I have a Plone 4.3.3 site. My logged in URL is different than the non-logged in URL. For example, the anonymous URL would be http://mysite.somewhere.com. When logged in, the URL is https://loggedin.mysite.somewhere.com.
When I create a link on a page and click save, if I view the page anonymously, the link is incorrect, displaying as the https version. However, if I go back and just open the page and click save, the link will be fixed and when view anonymously, it is fine.
These are internal links within the site and the site is not set to use UID's.
Any thoughts?
there is a bug report for this issue and it should have been fixed recently according to the comments there
https://dev.plone.org/ticket/13721
afaics 1.3.7 already contains this changes, so try to pin that version in your buildout
https://github.com/plone/Products.TinyMCE/commits/1.3.x
Related
I've been using the Facebook Plugin for years, on dozens of websites, but all of a sudden, I can only see the page's facebook header, the actual feed appears only as a spinning icon. This is on my desktop and mobile device, feed is at the bottom of the page. https://saltydogfestival.com
screenshot_mobile
However, my co-worker in the desk across from me tried it on his desktop and laptop and the feed loads just fine.
I'm not a page admin for this particular feed.
I have this plugin for other facebook pages, for which I AM an Admin, and those don't show up for me, either. I've tried using Chrome and Edge.
I'm knocking my head against the wall with this.... or maybe it's something so simple that I'm not seeing it... Suggestions??? Please save what's left of my sanity!
I think this issue has affected many sites including mine. I used a third party plugin recently that's said to no affect page speed. It's called "Buttonizer - Smart Floating Action Button" you can add a FB messenger button also and add call to action and any they button as well. I have disabled the Facebook chat one for now. If you can update me if it's now work for you that would be great as I'm in the same boat. Email mtgusto#outlook.com
Edited - bug seems resolved
This is what worked for me:
Go to Facebook Developers - Page Plugin and configure the 'widget' with desired params.
As you change the parameters the preview should update & show. If it doesn't, try signing out.
Click "Get Code" beneath the preview. I used the JavaScript SDK method.
Copy & paste the first piece of code after the < body > tag.
Copy & paste the second piece of code where the box should appear.
Previous answer - leaving here for posterity / reference
It seems to be an issue with Facebook that occurs when the visitor is signed in to Facebook. Try viewing the page in a private window or reload after you have signed out of Facebook to see if it loads when you are not signed in.
There's more information on a Facebook Developers bug report, which was just marked as closed 8/26, although it still appears to be happening: https://developers.facebook.com/support/bugs/584988619248795/
This other community thread has a work-around - look for Dave's comment: https://developers.facebook.com/community/threads/1018223139108570/
I have a single page which I built from the same blocks as other pages in the same category, which do work. This page redirects to the 404 page.
I checked to make sure the page was published- it is.
I am able to preview the page in the Experience area and it looks good.
From what I can tell, no other 301s have been set up to override this.
What else can I check?
Try Checking your log files. There are additional information about what is happening.
There were dependencies that were on the page that no longer existed. Apparently, whoever cloned the page used an older (previously working) page, which no longer worked.
The specific element in question was an object reference to an image in a gallery.
We removed the element in the editor, published the page, and it worked great.
I have the same problem like asked here: Facebook messenger checkbox plugin is hidden
I tried the implementation of the Facebook Checkbox Plugin according to Facebooks documentation but it won't show on my VM in my Company.
The Facebook SDK Implementation works fine, I tried the "Share" and "Like"-Button, which show up correct.
I have a Facbook Page which has public access and a Messenger APP in DEV-mode. The "Send-API" from Facebook works correct too: I am able to send message to myself as administrator from my Webpage on my development VM.
Following Steps are done: use a random user_ref on every request, set my page on the whitelist, use "https", visit my page FB-loggedIN and FB-loggedOut
But the result ends in Markup and Log-Infos like this screen:
See FF DeveloperTools Markup Screenshot for current state
According to this I visited a page given as origin where the Plugin should work (see first link in my question) - but there the plugins' HTML is the same like mine.
So is there a general problem on Facebooks' site or is there quite more necessary, to get this plugin running? Could it be a problem with self-signed certificate on my VM?
At the moment I don't want to notify or login any user. All I want is that the checkbox is shown.
Pherhaps anyone has an idea or the same experiences :)
Additional Info: the console shows following message
fb:messenger_checkbox failed to resize in 45s
after some fiddling we found out that a registered webhook is required (even if you dont consume the events) to make the messenger checkbox plugin render properly.
I inserted the facebook code where required and absolutely nothing happens or shows up. Using dreamweaver cs6 and in live view or when testing in ANY browser, nothing shows up. It's a blank box. ANy thoughts? I read somewhere that the website must be made into an application of facebook? Is this something?
Specifically, after activating the plugin and properly connecting the plugin to the facebook app,which does work and has been used extensively before hand, comments simply fail to load. There is no comment box, no past comments pull in either (note the app has historical comments already).
In the plugin settings area on the right side of the screen where the comments check box exists, there is a read more link that takes you to the facebook developers page where it discusses adding the facebook comments iframe.
If there is some other location where comment settings might also exist (past the three fields that require the 2 keys and the app name) I could not find them and this was not referenced in the plugin setup.
Like button (iframe / like.php plugin) of our Facebook app is broken for some days.
We have choose to use "http://www.facebook.com/apps/application.php?id=APP_ID" url instead of "http://apps.facebook.com/APP_NAME/" format (maybe not a good idea).
A click on it leads to a failure (popup telling "There was an error liking the page. If you are the page owner, please try running your page through the linter on the Facebook devsite (https://developers.facebook.com/tools/lint/) and fixing any errors.")
Linter is able to find that http://www.facebook.com/apps/application.php?id=APP_ID must be converted to "Final URL : http://apps.facebook.com/APP_NAME/"
Redirect Path section says "Final URL is in bold (this is the URL we tried to extract metadata from)" and final URL is correct (http://apps.facebook.com/APP_NAME)
But in this case, linter is not able to scrap Open Tags included into "http://apps.facebook.com/APP_NAME" despite the fact that open tags are well recognized if final URL "http://apps.facebook.com/APP_NAME" is directly submitted to linter.
It seems that open graph tags of final url are no more used.
Can someone confirm me that this a new behaviour/bug and tell how to solve it ?
Could I migrate our likes from one url (.../apps/application.php?id=APP_ID) to a new one that works (.../APP_NAME/) ?
Many thanks
Those /apps/application.php URLs were deprecated in December 2011 and removed in February 2012 - you shouldn't still be using them, they automatically redirect to the app's canvas or website URL. Like buttons may have given some semblance of still working on those URLs for a few months afterwards, but effectively anyone clicking them was becoming a fan of nothing
Your like button or Like Box should be pointing to the Page for your app if you have one. That blog post has instructions for creating one if you didn't migrate between December 2011 and February 2011
If you don't have a page for your app, there's no purpose to accumulating fans via the Like button as you can't target ads to them or send them updates.
There's instructions for creating a Page in the blog post i linked above, or in the Communicating with your users doc.