sorin.sfirlogea
Forum Replies Created
-
I am having the same problem here and the same message on a new WP site, when I try to setup Jetpack. Never installed W3 Total Cache, but the error message is:
The Jetpack server could not communicate with your site\’s XML-RPC URL. If you have the W3 Total Cache plugin installed, deactivate W3 Total Cache, try to Connect to WordPress.com again, reactivate W3 Total Cache, then clear W3 Total Cache\’s cache.
I am running WordPress on a virtual box in Upcloud and there is no blocking for my xmlrpc API. Strangely enough, other WP sites on the same box have Jetpack installed and are working fine. I disabled all plugins in the new WP site, but no success. Can’t figure out what could be the problem.
Any thoughts?
Thanks.Even if only the right menu is active, it does not work. No options are displayed and the colors are not applied to the right menu.
Forum: Plugins
In reply to: [Yoast SEO] wp_safe_redirect not working anymore after installing YoastYou’re right. Thanks a lot. I really liked Yoast SEO features and I was eager to use it.
Regards.Forum: Plugins
In reply to: [Flickr Justified Gallery] Using Responsive LightboxThe solution is simple: go to Responsive Lightbox plugin settings, in the General settings tab, look for the Selector option and replace the default value (which is lightbox) with flickrGal0. This way you will instruct Responsive Lightbox plugin to apply itself to flickr Justified Galleries.
Forum: Plugins
In reply to: [Facebook Comments] Your plugin made my Facebook comments disappearProblem solved. Now it works again with width=100%.
Forum: Plugins
In reply to: [Facebook Comments] Width 100% not working anymore after last updateIt doesn’t help to move back to previous version of the plugin, because is not a bug in the plugin, is a bug of Facebook.
Forum: Plugins
In reply to: [Facebook Comments] Your plugin made my Facebook comments disappearIs working without any width settings, but on desktop it doesn’t look that good. I need it to have 100% width of its parent element ??
Forum: Plugins
In reply to: [Facebook Comments] Your plugin made my Facebook comments disappearNow I’m pretty sure that this is FB problem. I took the code for comments from their site (https://developers.facebook.com/docs/plugins/comments/) and a created a blank page, on my website. I set the width to 100% and it doesn’t work as expected.
Here it is how it looks like: https://www.sfirlogea.com/test.html
Forum: Plugins
In reply to: [Facebook Comments] Your plugin made my Facebook comments disappearI made some debugging and discovered that comments are not gone, but they are not displayed. For some reason the comments are delivered by Facebook with 0px width. This happens only if you set the width of the plugin to percentage (like 100%).
If you set the plugin to pixels (eg 900) comments are displayed. But you loose responsiveness of the plugin.
Analyzing the FB documentation it seems more like a bug in FB not in the plugin.
Thanks for helping me out of the issue. Your responsiveness ?? brought you a new customer. I just bought the PRO version.
Take care,
SorinYes, you’re right, it did.
Just to make sure you got it right: after updating the plugin to 3.0.7, in the database RMVer setting was set to ‘3.0.7’ and it didn’t work. Now I kept the files of the 3.0.7 version, but I set the database option to ‘3.0.6’ and it works, although there is a discrepancy between the version of files and the database setting value.
Yup, it works. Thanks. Still, I don’t get it why the RMVer should be 3.0.6 when the version installed is 3.0.7…
This is a link to Dropbox folder where you may find screenshots and the output of admin.php?page=responsive-menu in both versions. Let me know if it works for you.
https://www.dropbox.com/sh/qzczcwz0icoghls/AADlDyCqlN12gn6g24j4YgJZa?dl=0
That’s what I thought initially. But looking into the 3.0.6 version I noticed that jquery-ui-sortable is also called and it works nice. The real issue here is that the admin.php?page=responsive-menu crashes after 1166 lines. The JS problem is an effect, because JQuery scripts are loaded into the page footer, so when HTML generation crashes these scripts never get to be loaded.