Absolute Paths prevent facebook scraper to access the pages

Hi ,

I'm using zen cart 1.5.1 and everything seems to work but the facebook debugger which is not great as the like/share buttons do not work.
Facebook debugger says Could not Parse URL.

the website is www regatuljocurilor. ro
The webserver admin says that zen cart has absolute paths and when a request comes it tries to redirect the pages and it ends up sending them to the router again thus timing out the requests.
He has a few sites working but zen cart is the only one with this issue.
He also says the site is not accessible from the webserver side due to these redirects.

Is there a way to make the pages with relative paths? as he says that should do the trick.

Regards,
Alex

Zen Cart by default uses relative paths in all links, with a <base href> set to the cart installation location. (This allows SSL to work correctly.) So either you have some modified links, or there is confusion about terminology.

I will double check with the administrator and let you know.
I haven't modified any on the links, I have actually backed up to the first day of installation and it behaves the same.

Your facebook link appears to be working??

The facebook fanbox works , the like box does not work as I've added it for every product.
Although it says that you liked the page , it does not update the information on FB and you cannot post it on facebook , the post window goes away but the update is never seen on fb.

Administrator says he sees the links as absolute paths trying to access www.regatuljocurilor. ro instead of trying to access only /regatuljocurilor which causes the redirect to the routers administration page....

the like box does not work as I've added it for every product.
When I click "like" I am asked to log into facebook

Yes , you log in to facebook like button will say you like this ...will ask you to post it but when you do nothing happens on fb , the facebook debugger says Error Parsing URL: Error parsing input URL, no data was scraped.

https://developers.facebook.com/tools/debug/og/object?q=www.regatuljocurilor.ro

flernebunu:

Yes , you log in to facebook like button will say you like this ...will ask you to post it but when you do nothing happens on fb , the facebook debugger says Error Parsing URL: Error parsing input URL, no data was scraped.

https://developers.facebook.com/tools/debug/og/object?q=www.regatuljocurilor.ro

You don't appear to have set any "open graph" parameters.
Facebook works better when these are set.

They are set if you look at the page source. I have the open graph module installed :
<meta property="og:url" content="http://www.regatuljocurilor.ro/" />
<meta property="fb:admins" content="100005258739582" />
<meta property="fb:app_id" content="152629171565736" />
<meta property="og:image" content="heh" />
<meta property="og:type" content="website" />

flernebunu:

<meta property="og:image" content="heh" />

This doesn't look like a valid image address???

Also try moving these above all that javascript

I've done what you suggested , still no improvement

This error message from Facebook's Object Debugger indicates Facebook is unable to scrape your website (no data returned when requesting a response from "www.regatuljocurilor.ro").

After copying the "text/html; charset=utf8" version of the page to a different hosting server (not doing charset negotiation) and modifying the og:url to point to the new URL... The Facebook Object Debugger works against the other hosting provider without an issue (and also points out some problems with your opengraph tags).

My initial thought is possibly something occurring with content (including charset) negotiation at the web server level... Or it could be something as simple as Facebook blacklisting your hosting provider (or your hosting provider blocking Facebook) for whatever reason.

You may want to look at your web server logs to do further debugging (or contact your hosting provider) and take a more in-depth look at the HTTP requests / responses between your server and Facebook.

I'll look into it and update the status of my issue...if you have other theories please post them

it was the router in the webserver's network...changed the webserver to test and everything works,
thanks for your answers

flernebunu:

it was the router in the webserver's network...changed the webserver to test and everything works,
thanks for your answers
Thank You for reporting back it was something on the hosting providers network :) Always good to hear the resolution (and hopefully helpful to others down the road)!