Facebook Like button breaks SSL because of the image-sprite loaded - facebook

We use the Facebook like button on the bottom of each page. We used to have the iFrame version but now changed to the FB version. On both solutions, we get an SSL error on our page because the image file is not loaded over a secure page.
When looking into the resources loaded, we see that two files are loaded securely:
https://www.facebook.com/plugins/like.php?app_id=110658975693059&href=http%3A%2F%2Fwww.stackoverflow.com&send=false&layout=button_count&width=280&show_faces=false&action=like&colorscheme=dark&font&height=21
https://s-static.ak.facebook.com/rsrc.php/v1/yK/r/PpEvPTmpg44.js
and the image sprite is loaded in plain http:
http://static.ak.fbcdn.net/rsrc.php/v1/z7/r/ql9vukDCc4R.png
I guess it is a temporary bug from facebook because the ssl-loaded css file references to a non-ssl image file. I created a bug report some time ago - with no response yet. Does any one have the same problem or even a solution on how to deal with that?
Thanks

There really is no fix for this that you can do on your end. Facebook must fix this, and they are extremely slow at fixing bugs. I noticed this on my site as well. Facebook's https css file is referencing non https images and causing this. I think this is a newer issue though because it used to work fine on my site.

We ended up grabbing the button resources and storing them locally. This improves page load time and solves any possible HTTPS issues.

Related

Wrong Link on Facebook and wrong open graph but good meta property

My web site www.jeancharlesbarthelet.com has good meta . (I checked)
When I tried to share on Facebook, there is no image, no description.
I tried one hundred times the debug tool !! (for one month)
Nothing works.
I am very worried because lots of people are sharing my news at this time..
Thanks for help.
You should try and show some code examples....
However, with that said, it may be a caching issue with your images and their server.
I did see that the path to the image (http://www.jeancharlesbarthelet.com/autre/logo.jpg) does serve up the image correctly. Perhaps revisit thie tomorrow?
When did you upload it to your server? if your hosting company uses akamai to cache it could take up to 6 hours to be seen globally...

URL causing javascript to disable

I have a website built in Magento. Normally javascript runs fine, but someone pinned a product to pinterest and the URL they pinned appended a series of characters that for some reason causes the javascript to stop running on that page. Here's the normal URL:
http://trumpetandhorn.com/vintage-engagement-rings/tiara-i.html
Here's the one that was pinned:
http://www.trumpetandhorn.com/vintage-engagement-rings/tiara-i.html#.UWC7Hb8fpFI
I've tried redirecting using htaccess but have had no luck with that. It's important for us to fix this as the person who pinned the product has 2.7 million followers so we're seeing a ton of site traffic from this.
Any ideas?
Thanks!!
This seems slightly unorthodox, but you could reassign the location.hash. At the top of the page, you can try this - it seemed to work in my tests. Of course, you can also find any non alpha characters at the beginning and strip them. I am just showing a base example.
window.location.hash = window.location.hash.replace('.','');

SilverStripe CMS times-out when changing pages in the CMS

I have installed SilverStripe on several servers successfully in the past (but I'm not a SilverStripe expert). This time my SS install fails to work and I'm at a loss how to fix it.
The Problem
SilverStripe 2.4.6 installed correctly on the server (AFAIK).
The front-end works as expected. (Show default theme. Pages all load correctly.)
I am able to log into the CMS admin section succesfully. The CMS loads but when changing site pages in the CMS using the browser pane on the left, the CMS shows the circular loading symbol. The new page load never completes.
Using the console of Firebug in Firefox - When attempting to change pages in the CMS (by clicking on the page browser pane) the CMS tries to load two pages. The second page request 404s.
The first GET request is from the initial page loads.
The following POST+GET requests fire when clicking on the page tree to change pages.
Attempting to Find the Solution
I've tried deleting and re-installing silverstripe twice. (2.4.7 and 2.4.6) Both times the problem recurs.
A strange thing is that this server is already running two other silverstripe sites (both of which I installed without a hitch). All three websites are accessed via different domains. I tried accessing this install via another domain thinking there might be something wrong with how this third domain is configured but that didn't help either.
What should I try now? I'm stumped.
Thanks in advance.
Responses to Comments
Check your root .htaccess file. Make sure RewriteBase is set to /
Checked. Full .htaccess on PasteBin
Indeed the javascrip URL is strange. Check if there is anything unusual about what's being returned from the previous POST request. Is the site running in dev, test or live mode?
I can't see anything unusual in the POST request.
Clue Found: The site is running in DEV mode. Switching to LIVE mode and the problem disappears. Also the second GET request only shows up in DEV mode.
Example Post request with response.
Example Get request with respones.
This is a work around more than a fix but if you'd rather be coding than bug hunting it might be worth a go! (remember to log out of SS before doing this fix)
In your mysite/_config.php file change
Director::set_environment_type("dev");
to
if(!isset($_GET['isDev']))
Director::set_environment_type("dev");
else
Director::set_environment_type("live");
Then you can develop the website in dev mode normally and to use the admin in live mode and avoid the bug you just go to: http://{your_domain}/admin?isDev=0
N.B. might find a proper answer when pastebin.com isn't overloaded and I can see your responses!

Facebook struggles to scrape one domain

I have already checked out this question, and it sounds like he's describing the same exact problem as me except for a few things:
I'm not running on https
80% of the time I try to debug, I get this message " Error parsing input URL, no data was scraped."
The scraper works perfectly on a different domain, but same server, same theme with almost identical content. Every time I try a domain it scrapes it perfectly including the image
During the 20% that it actually scrapes my page, I am having the same issue in the above link. It is reading my thumbnail, yet showing a blank image. The link brings me to a working image but it doesn't want to show anything.
The weird part is it worked completely fine about 10 months ago when I updated this blog on a daily basis. The only difference is I've switched servers recently. While that would explain a possibility, the other domain switched as well and doesn't have this problem.
I am at a loss why my links either show no image at all in facebook or give me the:
Domain Link
Domain
(no image, no description)
Very frustrating situation. Does anyone have any suggestions?
Update:
I have 6 domains...
When I moved servers recently, I found the new server wasn't prepared to compress the pages, so my blog posts looked crazy. This forced me to turn compression 'off' on WP Super Cache on my main blog. I also did it to my 2nd highest traffic blog figuring I'd get to the other 4 later.
Well, now those first two blogs appear to work fine in the facebook debugger, but the remaining 4 have troubles. The tricky part is, I completely removed WP Super Cache from one site and still had trouble fetching the data.
So while it seems logically it should have been a WP Super Cache issue, continuing to have errors despite removing it leads me to believe now? I'm still so baffled.
Update:
Ok, I loaded Chrome and IE, and both were able to pull the data with ease. The google snippet tool also worked great. I am going to try posting a link to my facebook fan page via chrome and see if it works correctly.
I did clear my FF cache and it didn't change, but I am still confused why one domain works ok while the other does not. Either way, if adding in Chrome works, I'll stick with that for now.
Any other suggestions?
Cache should not make any problem. If a browser can see your page, so can facebook debugger.
See if some 500 error is there. Try from different browser, clearing the browser cache etc. Try google rich snippet and see if a custom search engine is scrapping it fine.
PS: It will be nicer if you post url.

Umbraco Richtext Editor not loading

I've been scratchign my head on this one, hopefully someone can provide some feedback.
Umbraco Version: 4.7.2
Problem
A solution I developed for a company is having problem loading the rich text editor. They have a virtual IP solution acting as a proxy for their servers. After debugging on the client we noticed that the editor (tiny mce) was not loading because for some reason it is requesting the script and icons via the IP and not the URL. Obviously the IP is not hardcoded anywhere...
Need Help...
The client's IT department insists the configuration is ok; I think they are right, everything else in Umbraco seems to be working correctly. So I need help...
Is there anyway I can force the editor to be loaded from a specific URL?
I have experimented with changing the JS on umbraco_client, but the changes do not show when I load the editor. they appear to be cached somewhere (processed by the compressor), I've re-started the app and cleared my cache with no luck. How can I make my JS Changes be picked up?
What I've Tried
Setting the document.domain="my-url". No luck.
Setting the document_base_url on tinyMceConfig.config. Of course this is for links within the editor, so.. no luck
All other changes I've tried are on the JS files on /umbraco_client/tinymce3/, but I can't get them to show.
Any pointers?
Thanks,
-Covo
Is the RTE not rendering within umbraco it self or is the content not rendering on the front end?
This is a very good question - have you tried removing the property and adding again?
Other than what you've tried so far I'm out of suggestions other than the above sorry.