syklop
Forum Replies Created
-
Forum: Plugins
In reply to: [Ray Enterprise Translation] Hooked up at update translationSame behavior for me : Most of the time (not always…), the result of my translation (title and content) is empty. ??
Forum: Alpha/Beta/RC
In reply to: No WYSIWYG editor on 2.7-RC1-10041Same problem for me with WordPress 2.7-RC1-10119.
I disabled – re-enabled all my extensions and… now everything is working fine….
Forum: Plugins
In reply to: [Plugin: Google Analytics for WordPress] Comments disappear2.5.3 works fine for me too.
Forum: Plugins
In reply to: [Plugin: Google Analytics for WordPress] Comments disappearSame problem….
I wasted a big time before I understand the plugin version is causing the problem (restore database, downgrade from 2.5.1-alpha to 2.5, …).But rollback to 2.5.1 solved the problem.
Forum: Requests and Feedback
In reply to: WordPress 2.5 Widget Interface – I don’t like itWhen you remove a text widget, you lost (am I right ?) the whole content of the widget forever… With 2.3 interface, the “offlive widget” was preserved.
And I didn’t find how to move a widget from a sidebar to another : With 2.3 interface, it was just a drag and drop…
I have a text widget without any “Edit button” : I can’t edit nor remove this widget !….. BUG ?Forum: Fixing WordPress
In reply to: Schedule a post to be published at a future date: Does not workI saw elsewere that there is same symptoms with different cause for this problem.
wp-cron.php *is called* by wp-includes/cron.php (function spawn_cron), at each visit or admin panel load.
For my case :
There is no WP bug : I checked the call made by cron.php to wp-cron.php : The arguments are OK.
There is no MySql problem, because the manual call of wp-cron.php (affter disabling first check in the script) is OK.
in my case, fsockopen works fine when calling an external URL. But it does not work with an internal URL : It’s a “feature” of my hosting solution…..Forum: Fixing WordPress
In reply to: Schedule a post to be published at a future date: Does not workHello,
I had the same problem, and your workaround works for me too.
wp-cron.php is called by wp-includes/cron.php (function spawn_cron).
The problem, in my case, il that the php function “fsockopen” is not allowed by my hosting provider, when the URL is “local”.
For my complete tests, you can read https://blog.quelbazar.net/2007/06/16/wordpress-22-et-les-problemes-rencontres-sur-quelbazar/ , (in french…)