friend asked me to help him out with his Joomla website. Here is the problem. He turned off Plugin System Cache and in Global Config he turned off cache in Cache settings and when he posts links on his articles on Facebook everything is fine. He needed to turn on those caches due to website crashes but now when he links article on Facebook Article name is something random from site and not actual article name. He tried Facebook Debug option and this was error
More Than One OG URL Specified:
Object at URL 'http://www.madbarz.com/news/614-not-your-average-mamas-workout' of type
'website' is invalid because it specifies multiple 'og:url' values:
http://www.madbarz.com/news/614-not-your-average-mamas-workout,
http://www.madbarz.com/news/565-hannibal-for-king-compilation,
http://www.madbarz.com/add-team.
Obviously the "post to facebook" code is being cached once instead of once per page.
This most likely depends on it being added as a module (as opposed to a plugin, which would cause no trouble), and the module doesn't take into account proper caching techniques.
Since having page caching and global cache on is desirable, you may be able to get around this just setting the module's cache to "Do not cache": it will still be cached by the system page cache, but that cache is built once per each page so you'll be fine.
The multiple headers could be an issue generated by the same cause.
If this still doesn't solve the issue, look into the module's code; here you can find some info on setting up a module to cache correctly: http://www.fasterjoomla.com/joomla-dev/programmare-un-modulo-joomla-per-utilizzare-la-cache
The reason the site crashes with cache turned off should be studied: it's not normal and you don't want to run a site under those conditions, it's not safe. There could be something really really wrong and you might end up wasting months to build linkbacks only to find they all become invalid at some point.
Related
I need to use the member profile plugin from LinkedIn for a project. So I generated my personal "code" at https://developer.linkedin.com/plugins/member-profile . Which gives me the following standard code sample
<script src="//platform.linkedin.com/in.js" type="text/javascript"></script>
<script type="IN/MemberProfile" data-id="https://www.linkedin.com/in/myname" data-format="inline"></script>
Where "myname" is obviously replaced with the name at which my public LinkedIn profile is found.
My problem is that there is nothing showing, after inspecting the resulting html at a couple of frames deep there is only a hidden div with the following content:
<h2>
Your Request Could not be Completed.
</h2>
I have checked all my privacy settings on LinkedIn and they are configured to make sure all information is publicly available and there should be no reason to let this plugin fail. I even checked with a colleague and we compared settings, the settings were the same but his plugin worked and mine did not.
Does anyone know what is causing this problem? Is there a setting we are missing, which is detrimental to this plugin?
(fyi, the plugin is running from a server so there is no problem to actually get the script)
The question was asked several times here (as the LinkedIn support is unwilling to help and redirect here where developers seldom answer questions)
See this question
Linkedin Member Profile Plugin not working for some profiles
One month after it was asked (yes one month!!!), a LinkedIn dev answered:
"The problem is under investigation. Several profiles still work fine, so there isn't a systemic issue with the plugin itself, but rather with certain profiles in particular."
Note that the number of particular profiles seem to be huge, because 9 out of 10 profiles I try fail.
Nothing has changed since then...
This is not the only bug in LinkedIn which is litteraly ruining my experience with it.
I used to love LinkedIn, but the way their support is treating customers (yes I am not only a user but also a customer because I pay for ads...) + the fact that they just can't seem to detect/fix their bug is making me become very bitter about them.
So all you can do is to cross fingers and hope that somewhere, someone will finally care about this and fix the bug...
The problem i have is that i own a website where other people can post stuff ,creating new pages on my domain, but the problem that occured today is that all the new post pages created today are malfunctioning , sharing is not loading thumbnail picture and title and so on, but the weird this is that all the posts(new pages) created before today are all working fine
What caused an error to occur out of nowhere?
I also cannot debug any of the URL's of my website as the same error: Error parsing input URL, no data was scraped
The website im having problems with 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 says no error on page but facebook still cant reach it. http://www.vabameedia.ee/vm/178/craig-parks-%C3%BChek%C3%A4eline-krossisoitja.html
For people experiencing the same problem but for different causes, I discovered a few interesting things about how Facebook "scrapes" pages, checking the logs of the server while doing some trials.
First of all: if you never tried to share a page with FB, FB never tried to scrape it, and it will not try to do so if you only put the url in the Debug tool.
That's the first reason because you get the error: it just states that FB has no information on the page, you must "force" it to scrape the page.
The first time you try to share a page, FB scrapes it (asks your server the first 40k of the page and analyse the opengraph tags).
What can happen is that you do not see the image: Facebook Share Dialog does not display thumbnails one first load
The reason is that FB behind the scenes is still scraping your page and caching the image. The next time, in fact, you have also the image.
How to solve it? Pre caching: https://developers.facebook.com/docs/sharing/best-practices#precaching
or simply add
<meta property="og:image:width" content="450"/>
<meta property="og:image:height" content="298"/>
I was pulling my hair out trying to fix this issue. Hours and hours of troubleshooting to no avail. After speaking with one of our programmers about a topic unrelated I thought of something to try as a long shot.
Much to my surprise, it worked!!!
This is the reason behind the problem and my solution for it:
When you draft a post in WordPress it generates a link based on your article's title (unless you manually change it). The title of my article included special characters, however the auto-generated link didn't display these special characters, only hyphens to replace the spaces. Should be fine right? Wrong! Somewhere embedded in metadata and code in the WordPress platform are those special characters and they mess up the way Facebook pulls info from the article being linked to. This is a problem because certain special characters invalidate hyperlinks.
For example:
Article Title: R[eloaded]
Auto-generated hyperlink DISPLAYED in WordPress "Permalink" field: http://www.example.com/reloaded
Actual WordPress Auto-generated hyperlink: http://www.example.com/r[eloaded]
Those brackets will invalidate the link and Facebook will be unable to pull any information (ie pictures) from it.
Solution:
(1) Simply, manually change the WordPress hyperlink address to something that doesn't include any special characters (this will not change the title of your article).
(2) Click "Update" to change the post to include the new hyperlink.
(3) Click "Purge from Cache" in the WordPress window
(4) Refresh your Facebook browser window
(5) Paste the new hyperlink for your article
(6) Enjoy your Facebook post with a preview image and information
Sidenote: Don't pull your hair out over Facebook, it's not worth it. =)
If you're using Wordpress, edit the post in question to change the permalink (just alter it slightly), then update the post. Using the new permalink in the Facebook OG debugger should now work.
It's a weird fix, but I think it takes care of a problem caused by special characters being used in the title of a post, which is then used to make the permalink.
Its all about DNS issue, was having same issue and resolved it by updating domain name servers to actual name servers.
In my case my domain was pointed to ns1.websterz.net and ns2.websterz.net and on this server i had DNS redirect to my other server (where web site is hosted). I Just updated name servers of the domain to actual name servers where my web site is hosted on. This was account migration case i forgot to update name servers as of new server.
Everything works fine now.
I'm setting up a temporary coming soon one-pager for my employer and after running the Object Debugger on it, as I usually do when setting up a new site it brings up an error I've not seen before.
Cannot change og_type The object at 'http://www.example.com/' previously had type 'article' and cannot be changed to an object of type 'website' to avoid data corruption of existing actions.
So, the graph API still returns the old OGP data for the URL (https://graph.facebook.com/10150291357906791) even though I've changed the meta tags on the website.
The url has 15 likes already, and honestly, I don't really care that much about them and if the solution involves losing them, I'm all for it.
I found a solution for changing the og:type for subpages (http://facebook.stackoverflow.com/a/14405329/859999), but the page in this case is the root of the website. So… the solution posted there is not usable in this case.
Since you don’t care about existing likes, I’d suggest to just use a new URL for this.
You said it is the root URL of your page – but if it’s only temporary, you could redirect from there to another address (which has the correct meta info).
(If you are worried about your SEO-Ranking or something, you could do this redirect only for the Facebook scraper, recognizing it by its User Agent.)
I recently purchased the domain www.iacro.dk from UnoEuro and installed WordPress planning to integrate blogging with Facebook. However, I cannot even get to share a link to the domain.
When I try to share any link on my timeline, it gives the error "The content you're trying to share includes a link that's been blocked for being spammy or unsafe: iacro.dk". Searching, I came across Sucuri SiteCheck which showed that McAfee TrustedSource had marked the site as having malicious content. Strange considering that I just bought it, it contains nothing but WordPress and I can't find any previous history of ownership. But I got McAfee to reclassify it and it now shows up green at SiteCheck. However, now a few days later, Facebook still blocks it. Clicking the "let us know" link in the FB block dialog got me to a "Blocked from Adding Content" form that I submitted, but this just triggered a confirmation mail stating that individual issues are not processed.
I then noticed the same behavior as here and here: When I type in any iacro.dk link on my Timeline it generates a blank preview with "(No Title)". It doesn't matter if it's the front page, a htm document or even an image - nothing is returned. So I tried the debugger which returns the very generic "Error Parsing URL: Error parsing input URL, no data was scraped.". Searching on this site, a lot of people suggest that missing "og:" tags might cause no scraping. I installed a WP plugin for that and verified tag generation, but nothing changed. And since FB can't even scrape plain htm / jpg from the domain, I assume tags can be ruled out.
Here someone suggests 301 Redirects being a problem, but I haven't set up redirection - I don't even have a .htaccess file.
So, my questions are: Is this all because of the domain being marked as "spammy"? If so, how can I get the FB ban lifted? However, I have seen examples of other "spammy" sites where the preview is being generated just fine, e.g. http://dagbok.nu described in this question. So if the blacklist is not the only problem, what else is wrong?
This is driving me nuts so thanks a lot in advance!
I don't know the details, but it is a problem that facebook has with web sites hosted on shared servers, i.e. the server hosting your web site also hosts a number of other web sites.
I've been at this for almost 3 days straight and now I can't even think clearly anymore.
All I'm trying to do is to get my featured image thumbnail to appear when I paste the link in Facebook.
I'm using the Wordpress Facebook Open Graph protocol plugin which generates all the correct og meta properties.
My thumbnail images are 240x200px which respects the minimum requirements and also respects the 3:1 ratio
I've made sure there's no trailing slash at the end of my post URLs
When I use the Facebook Object Debugger, the only warning is in regards to my locale, but that shouldn't affect it.
Facebook appears to be pulling the right image, at least the URL is correct, but the image appears as a blank square
I've gone through pretty much every thread I could find in forums, but all the information available is about using the correct og tags, which I believe I'm already doing.
Thank you very very much for any help, I'm desperate!! :)
You can troubleshoot the OpenGraph meta tags with the Debugger https://developers.facebook.com/tools/debug - this can at least show if you're using the meta tags properly and if Facebook can 'read' the image.
I finally figured out that the root of my issue was the fact that I was using an addon domain (which is really a subdomain being redirected to the top level domain) and I read on eHow (of all places :) ) that Facebook has trouble pulling data from redirected domains.
Not sure if there was another way around it, but I simply ended up creating a seperate hosting account and everything is loading properly now.
one problem youre going to run into testing is that often the first time your page or post gets liked, fb keeps whatever img it finds in your meta tags or by searching your page. so, you'll keep changing your img meta tag and still it wont show the right pic. it's very anoying. One way to get around it is to change the slug of your post. now, it has a different url and to fb, it's a different page. The downside is you lose all the likes that go with your orig url. Not a problem with a new site.
I ended here googling another problem. Maybe this might help someone:
Please bear in mind that the facebook scraper works asynchronously and will need some time (during my tests around 10 minutes) to be able to display an image after seeing it for the first time.
For more information, here's a more thorough answer on a similar problem.
Indeed, as Andy Wibbels points out the FB debugger is a really handy tool.
I faced a similar issue with a server's og:image tag pointing to a secure subdomain which actually mirrors a CDN server,
<meta property="og:image" content="https://subdomain.pathToImage.jpg" />
<meta property="og:image_secure" content="https://subdomain.pathToImage.jpg" />
The FB debugging tool allows you to see the errors that FB encounters when trying to pull the image.
In my case the subdomain was not registered under the SSL certificate used by the HTTPS protocol. Hence FB was getting the following error,
Curl Error : SSL_CACERT SSL certificate problem: unable to get local issuer certificate