Geek Answers Handbook

Linter gives error "URL parsing error"

TASK: I am trying to apply the Like button on my blog - this is my first attempt.

BEHAVIOR: A button appears, but when someone clicks “Like”, the word “error” appears in red next to a similar button. There is no interaction with Facebook.

FIX TRIED: I tried both the implementation of iframe and html5, the same behavior using both methods.

FIX TRIED # 2: The word “error” appears as a hyperlink suggesting the use of Facebook Linter, which is why I did. However, when I insert my URL, Linter gives this error:

Invalid parsing url: error in parsing url, no data was cleared.

I tried the main URL of my blogs (douganddaniele.tumblr.com) and the URL of a single post ( http://douganddaniele.tumblr.com/post/14308744801/settling-in ).

I use Linter here: https://developers.facebook.com/tools/debug

HELP HELP: Clearly, there is something here that I misunderstand. Can anyone help?

+8
debugging blogs facebook-like
source share
10 answers

You will get this if the FB has trouble parsing any of the og tags. You can usually find the problem by following these steps:

1) The first thing to check, go through and make sure that there is nothing obvious. Often, if you use something like WordPress, simple things can get complicated. Browse through the source code and make sure everything is as you think it should be.

2) Visit any URLs. Linking to invalid og: url or og: image URLs may cause this error.

3). Your og: image url should be https (as of October 1, 2011). You will get this error if it is not (at the time of writing, this may change).

If you follow these steps and still have problems, return to the basics. Remove all tags and add each separately, each time launching the debugger. At least you will know which tag is causing the headache.

+7
source share

It seems that there are many cases where developers come across a message:

Error Parsing URL Error parsing input URL, no data was scraped.

and they cannot solve this problem. I believe that the best way to solve this problem is to get Facebook to provide more detailed error messages. Go to their bug tracker and comment, subscribe or add to the playback counter.

+3
source share

I had the same problem, but it was constant.,. produces damaged jpg in the og: image tag, which caused an error. I re-saved the image as png and it started working again.

+1
source share

I get this error when my .htaccesses files do not have

 RewriteCond %{HTTP_REFERER} !^$

Sometimes I don’t add this line to prevent a direct link to images and stuff. if I remove it, the debugging tool will go fine.

+1
source share

Wait and try again. Worked for me in a couple of minutes.

0
source share

Also check if you have, for example. php redirect (www.site.com to .com site) which also gave me a lot of open schedule errors. So I decided to remove it.

0
source share

I found that Facebook gave me this error if any of my og: meta tags other than og: image: secure_url contained an https:// link.

The best debugging procedure, apparently, is to remove all the meta tags from your page, then add them back one by one and fix everything that causes the linter to break.

0
source share

I got this error when an IMG tag was included in the HTML of my page, pointing to a server that the Facebook linker could not reach (corporate firewall).

In other words...

THIS WORKS

 <html> <head></head> <body> Hello World </body> </html>

THIS DOES NOT WORK

 <html> <head></head> <body> Hello World <br><img src="http://server.facebook.cannot.reach.com/some/file.jpg"> </body> </html>

When I removed the IMG tag or changed it to point to a public server, the debugging tool worked.

I contacted a couple of friends who work on Facebook and asked them to rely on the people in charge of the Debugger tool to provide more detailed error messages.

0
source share

I had the same issue when my URL that I used in the debugger had the following:

 www.mysite.com?s=&blah=yes

Facebook did not like the query string s, which does not matter.

0
source share

You are not setting the wrong link?

 CASE 1: // OK <meta property="og:image" content="http://exsample.com/test.jpg" /> CASE 2: // Error parsing input URL, no data was scraped.(No Image Mime) <meta property="og:image" content="http://exsample.com/" />
0
source share

More articles:


All Articles