I have a personal website at http://deanattali.com/
A few days ago I shared my site on my feed and everything was ok. Now whenever I try to share any other page, Facebook does not parse it and simply ignores it.
I tried the Open Graph Object Debugger tool and it always returns "Error Linting URL An internal error occurred while linting the URL."
For example, try any of the following URLs:
http://deanattali.com/aboutme
http://deanattali.com/2015/03/12/beautiful-jekyll-how-to-build-a-site-in-minutes/
I even tried taking an HTML page from a similar site and copying the exact same HTML onto my site, and the parser worked for the other site but not for mine
Page on other site that works: http://keshinid.github.io/2015-02-26-flake-it-till-you-make-it/
Page on my site with identical HTML that doesn't work: http://deanattali.com/test
This is very frustrating, the error is very vague.
When I try to click on the link to see what the scraper sees on FB's debugger tool (https://developers.facebook.com/tools/debug/og/object/) it says "Document returned no data"
Another point worth mentioning is that this is a GitHub Pages website, with URL daattali.github.io and I have a CNAME to deanattali.com (I'm not sure if that matters at all)
I'm very lost, thank you
For anyone who will ever run into this problem in the future: a bandage fix seems to be to append ?fbrefresh=anystring to the URL. It looks like when there is a fbrefresh param in the query string, it works fine (doesn't matter what the value of the parameter is). Not sure what the underlying cause is, whether this is a bug or not.
Related
I am having an issue regarding App Indexing. I have attached a graph and i want to know why there is a decline after 5th Nov as you can see from the graph. Applinks are working completely fine (which is while we search on google it redirects to the app when we click on the link in the search page). Any help would be much appreciated
I went through "https://firebase.google.com/docs/app-indexing/android/test#testing-your-completed-app" to validate my links. For some app urls it works proper but for some app urls it gives me following "ERROR:An unknown error happened when we processed your request. Try again later." But for those app urls linking is working proper. Please refer following crawl status graph image to understand problem.
As the title suggests, http://localhost/mywebapp is being automatically added to urls within my application.
User clicks an https hyperlink, but instead of browsing to
https://correcturl.something.com
it goes to http://localhost/mywebapp/https://correcturl.something.com
ie the localhost part is being automatically added. I'm sure there is an IIS setting that we are missing here.
It might not be IIS. If you're forming your URLs improperly, I'm pretty sure the browser will handle redirect to "current url" + "redirecting url".
example:
if you execute the following in a javascript console, you will not get redirected.
window.location.href = "/http://google.com";
Running that off stackoverflow page sends me to https://stackoverflow.com/http://google.com
which is incorrect.
I'm assuming that if you're testing urls in some dev environment locally, you'll produce a similar result against localhost. I can't give you a better answer without more information, however I would begin by looking for something in your app similar to what I described.
I'm in the middle of testing a customized Dojo theme based on the popular claro theme. The new theme is named 'jelam'. I've gone through all the suggested steps for making a new theme based on an existing theme like claro and all seems to be working fine - except Firebug is reporting an error immediately upon opening my page. It reports that it can't find the claro_rtl.css file. The thing is, I've searched many times my source code and files for any reference to that claro_rtl.css file, but I can't find it. I suspected initially that my browser was cacheing it somehow, so I cleared the Firefox browser, closed Firefox and ropened it, and also restarted the WebSphere portal which is serving my JSP page. Despite those attempts to clear out any reference to claro_rtl.css, I'm still getting the error reported in Firebug.
"NetworkError: 404 Not Found - https://localhost:10149/CompassThemesURS/themes/html/commonurs/dojo/1.9.1/dijit/themes/jelam/claro_rtl.css"
How can I get Firebug to show me what the source of that request is? I had initially suspected that I had missed it in one of my many JSP files or CSS files that was possibly importing it, but it's not showing up.
Is there a way to get Firebug to show me who is trying to pull that file in?
Thanks for any insight you can give.
Finally figured it out. In Firebug I put "claro_rtl.css" in the search box, then performed the search in each tab until the search found it from the CSS tab, and it found it referenced in the new jelam.css file.
I had forgotten to redeploy the webapp. I had correctly updated the source files, including jelam.css, but I hadn't redeployed with those updates like I thought I had.
Cheers.
I have written my first asp.net website and I'm ready to deploy. I've followed this tutorial to the letter in order to test first and all seems to proceed without any hitches or errors. However, the webpage gives a blank page with nothing rendered, only
<html><head><style type="text/css"></style></head><body></body></html>
All the files seem to have deployed correctly and I can see them in C:\inetpub\wwwroot\Test Webpage and if I attempt to run using inetmgr I get the same.
Can anyone advise what the problem(s) might be? Below are some screenshots of IIS if it helps but will post up more info if needed.
Our website keeps logging a "page not found" error under the Drupal Recent Log Entries, but we do not know where it is coming from. When clicking into the detail of the error, the location is marked as "http:///*", user is "Guest", and severity is "warning". Does anybody have ideas on where we can find out what's causing these errors to log?
Page not found warnings like this can be caused every kind of code that triggers an http request, like loading a .js or .css file or an image. A way to debug this is the quick-and-dirty method described by Lullabot which means that you add a debug_backtrace() at the point where the warning is registered (in your case probably the watchdog() function, see the comment by Randy Fay).
PS. #Arvind: If you're using the Drupal API correctly, there shouldn't be too many drupal_goto calls in your code.
do you have atypo error in your code? check if you have mistakenly commented coz i see /* in the link.
This has to be a local error. I would check for my drupal_goto calls in my code.
this is my guess and i'm no drupal expert. let us know if it helps.
atb!
You might have an issue with your favicon like I did, although I don't recalling it generating errors in my watchdog.
It's what triggered a lot of page not founds on my setup.
Basically, you normally put your favicon in your root. However, some browsers ( I believe IE6 ) , don't check the root for your favicon, but your theme folder.
I just duplicated my favicon in my theme folder, and my problem was solved.
Worth a try.