lukum

Ok thanks for your reply. Hopefully that’ll be an additional feature soon ??

As to the sorting issue also: no “sortable handle” icon shows up in the backend.
Lk

Hi,
Excellent plugin, congrats. One thing doesn’t seem to work though: nothing happens when clicking the “Change Order” button.
Any fix? Thanks!

Luk

Same here, but I read in another post that it’s due to two plugins I use: “registered users only” and “members only”. The strange thing around this issue is that my blog client (Ecto) can bypass the authentication and publishes my posts flawlessly, whereas the WordPress app itself (downloaded today) cannot do it. I haven’t found any fix for that, anybody knows any howto??

No code in the sidebar files… Any idea about how to integrate a rotating banner into header.php?

Well, here’s another useful info. I’ve got another worpdress blog on another server where automatic plugins upgrade works just fine, and cURL is enabled. That server has php 5.2.4 installed (whereas the other server with the buggy WP installs has php 5.2.6 installed). Also, the server where automatic upgrade works shows the following with the core-control plugin:

PHP HTTP Extension Not Available
cURL Available Disable Transport | Test Transport Primary GET
Primary GET(non-blocking)
PHP Streams Not Available
PHP fopen() Not Available
PHP fsockopen() Available Disable Transport | Test Transport Primary POST
Primary POST(non-blocking)

Here the cURL test/disable settings don’t end with an Apache error.
I don’t know if that means something, but the server with the automatic upgrade that works has less available functions than the other with the buggy installs…

@dd32: it seems we’re on the right track for troubleshooting: I installed the core-control plugin as you said, activated the http module, and I have this:

PHP HTTP Extension Not Available
cURL Available Disable Transport | Test Transport Primary GET
Primary GET(non-blocking)
PHP Streams Available Disable Transport | Test Transport Primary POST
Primary POST(non-blocking)
PHP fopen() Available Disable Transport | Test Transport
PHP fsockopen() Available Disable Transport | Test Transport

When trying to Disable transport for cURL, I get a server error:

Not Acceptable
An appropriate representation of the requested resource /index/wp-admin/admin-post.php could not be found on this server.
Apache/2.0.46 (Red Hat) Server at https://www.myserver.org Port 80

Note that cURL support is enabled in my php settings.
What does “PHP HTTP Extension Not Available” mean?

Does that issue have to do with the server settings? Should I ask my provider to disable cURL, or is there another workaround? Thanks.

Answers to Gangleri and dd32:

– Yes, the issue affects all plugins
– No, the Plugin browser doesn’t work properly when I try to download/install a new extension. I have the same kind of message, “Download failed”, and operation timed out. So I guess the same issue affects updates and new installs.

Thanks!

Man, that’s something thanks, then it’s not a real bug! My theme is Wuhan. What could be the relevant .php file, and where to edit it to use the_content()? By the way, I’ll take some time to read (and why not install) your excerpt plugin.

I can’t get this promising plugin work on WP 2.0 with Wuhan: all categories vanish in the sidebar. The author says in the readme file that this could be due to the category list HTML that “is somewhat different than what the plugin expects. In this case, please email the HTML snippet to the me and I’ll try to fix it.”
I’m new to WP and I have no idea where to find this information and even how to start troubleshooting the problem. Thanks for helping.

I would like not to list some specific pages in Fuzzy recent posts. Is it possible to insert the ‘exclude’ tag in ‘<?php the_recent_posts(); ?>’ (is in the sidebar), or alternatively, what would be the script for excluding pages in the list of recent posts if the pages option is set to true?
Thanks!

Well, that was not my interpretation of the issue: I know a bit of open source developers, who also use their time to freely write code for different apps. All I notice is that sometimes, giving a more precise frame for development, whithout being too much restrictive, prevents confusion and long forum discussions… ??

Thanks, this worked. But I also understand another thing: the plugins location is not stable between developers. In fact, some plugin developers ask that you place their plugin folder in \plugins, and that’s it, whereas others ask that their plugin files be put directly in \plugins. Others even ask that some of their plugin files be put directly in \admin\. In most cases, you can activate the plugins from the Admin panel properly, but then some functions may work or not. Therefore I think that less freedom should be given to developers to plugin files location, since it tends to produce confusion by end users.