Error parsing input url, data was not cleared. only with new pages on my site

Question

The problem is that I have a website where other people can post material by creating new pages in my domain, but the problem that arose today is that all the new mail pages created today are not working properly, joint use does not load the thumbnail image and title, etc., but it is strange that all messages (new pages) created until today, everything works fine. What caused the error from nowhere?

I also can not debug any URL of my website as the same error: Input parsing error, no data was cleared

A website that has problems is here http://www.vabameedia.ee/vm/184/h%C3%A4da-ei-anna-h%C3%A4beneda.html

This is one of the sites where it does not report an error on the page, but facebook still cannot reach it. http://www.vabameedia.ee/vm/178/craig-parks-%C3%BChek%C3%A4eline-krossisoitja.html

Answer 1

For people who are experiencing the same problem, but for different reasons, I found some interesting things about how Facebook “scratches” pages by checking server logs when performing some tests.

First of all: if you never tried to share the page with FB, FB never tried to clear it, and it will not try to do it if you only put the URL in the Debug tool , This is the first reason you get the error: it just states that the FB has no information on the page, you have to “force” it to clear the page.

The first time you try to share a page, FB resets it (requests the first 40k pages from your server and parses opengraph tags). What can happen is that you do not see the image: Facebook Share Dialog does not display thumbnails with the first download

The reason is that the FB behind the scenes still clears your page and caches the image. Next time, in fact, you have an image. How to solve it? Pre-caching: https://developers.facebook.com/docs/sharing/best-practices#precaching

or just add

<meta property="og:image:width" content="450"/> <meta property="og:image:height" content="298"/> 

Answer 2

I pulled out my hair trying to solve this problem. The hours and hours of troubleshooting are inconclusive. After talking with one of our programmers about an unrelated topic, I thought about something to try and take a long shot.

To my surprise, it worked !!!

This is the cause of the problem and my solution for it is:

When you create a post in WordPress, it creates a link based on the title of your article (unless you manually modify it). The heading of my article included special characters, however the automatically generated link did not display these special characters, but only hyphens to replace spaces. Should it be good? Wrong! Somewhere, embedded in the metadata and code on the WordPress platform are these special characters, and they messed up the way Facebook retrieves information from a related article. This is a problem because some special characters invalidate hyperlinks.

For instance:

Article Title: R [eloaded]

Auto-generated DISPLAYED hyperlink in the "Permalink" WordPress field: http://www.example.com/reloaded

Actual WordPress Auto-Generated Hyperlink: http://www.example.com/r [eloaded]

These brackets invalidate the link, and Facebook will not be able to extract any information from it (i.e. images).

Decision:

(1) Just manually change the WordPress hyperlink address to something that does not contain any special characters (this will not change the name of your article).

(2) Click Refresh to edit the message to include the new hyperlink.

(3) Click "Clear Cache" in WordPress Window

(4) Refresh your Facebook browser window.

(5) Insert a new hyperlink for your article

(6) Enjoy your Facebook post with preview and information.

Sidenote: Don’t pull your hair over Facebook, it’s not worth it. =)

Answer 3

If you use Wordpress, edit this post to change the permalink (just change it a little), and then refresh the message. Using the new permalink in the Facebook OG debugger should now work.

This is a strange fix, but I think it takes care of the problem caused by the use of special characters in the message header, which is then used to create a permalink.

Answer 4

All about the DNS problem, had the same problem and solved it by updating the domain name servers to the actual name servers.

In my case, my domain was listed on ns1.websterz.net and ns2.websterz.net, and on this server I had a DNS redirect to another server (where the website is located). I just upgraded the domain name servers to the actual name servers that host my website. This was a case of account migration, I forgot to update the name servers from the new server.

Now everything works fine.