When going to either http://myhost.mydomain/admin/user/user (Administer: User) or http://myhost.mydomain/admin/content/node (Administer: Content), and select a filter in the "Show only items where" fieldset, clicking the "Filter" button performs a page reload but the results are not filtered.

Comments

blakehall’s picture

blakehall commented
Status: Active » Postponed (maintainer needs more info)

Works fine for me on multiple 5.2 sites. Can you upgrade to 5.2 and verify that you still have this issue?

ShutterFreak’s picture

ShutterFreak commented

I have upgraded this site to Drupal 5.2 and this problem still occurs. The Apache log file displays a POST request with a 302 response code, like in

"POST /admin/content/node HTTP/1.1" 302 -

or

"POST /admin/user/user HTTP/1.1" 302 -

Anybody a hint of what might be the problem?

nschindler’s picture

nschindler commented

Same issue in my 5.2 installation.

Steps to reproduce:
Click Admin->Content management->Content
Filter by (for example) status is published
Click the "Filter" button
Observe how nothing happens :)

Same issue in admin/user/user

This happens in IE7 and Firefox2.

nschindler’s picture

nschindler commented
Version: 5.1 » 5.2
Component: other » node.module
Status: Postponed (maintainer needs more info) » Active

Oh, also:

Database interface - mysqli
Database version - 5.0.26
Drupal version - 5.2
PHP version - 5.1.2
Web Server - apache2-prefork-2.2.3
OS - SLES 10 SP1 2.6.16.53

FOUND IT while I was writing this. It's "mysqli" vs. "mysql" that causes this. Everything I've read recommends mysqli when using mysql 5+ and php 4.something+.

ShutterFreak’s picture

ShutterFreak commented

I am not sure. The DB connect string in my settings.php file used "mysql:" as protocol when I reported the bug. I set it to "mysqli:" for testing, and restarted Apache (I did not restart MySQL), but to no avail. So on my installation the bug does not seem to depend on the MySQL communication protocol (mysql/mysqli).

nschindler’s picture

nschindler commented
Version: 5.2 » 5.3

It's consistent and immediate on my installation (mysql restart not required): The feature works with mysql, but not mysqli.
Still happens in 5.3. Also tried different themes and disabled all non-core modules. Same behavior in FF2 and IE7.

ricabrantes’s picture

ricabrantes commented
Version: 5.3 » 5.x-dev
Status: Active » Fixed

I can´t reproduce this in D5.x-dev.. moving to to fixed..

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.