gplasky

Ok so I was able to grab some log data after replicating the issue (actual paths and usernames redacted):

2013-06-24 23:10:07 auth_cookie_expired: some_user
2013-06-24 23:10:07 auth_cookie_expired: some_user
2013-06-24 23:10:07 auth_cookie_expired: some_user
2013-06-24 23:10:07 authenticate: empty user_name
2013-06-24 23:10:07 wp_login_failed: authenticate filter not called
2013-06-24 23:10:07 wp_login_failed: authenticate filters
2013-06-24 23:10:07 wp_login_failed: backtrace: [{"function":"wp_login_failed","class":"login_security_solution","object":{"dir_dictionaries":"\/home\/vhosts\/webroot\/wp-content\/plugins\/login-security-solution\/pw_dictionaries\/"},"type":"->","args":[""]},{"file":"\/home\/vhosts\/webroot\/wp-includes\/plugin.php","line":406,"function":"call_user_func_array","args":[[{"dir_dictionaries":"\/home\/vhosts\/webroot\/wp-content\/plugins\/login-security-solution\/pw_dictionaries\/"},"wp_login_failed"],[""]]},{"file":"\/home\/vhosts\/webroot\/wp-includes\/pluggable.php","line":485,"function":"do_action","args":["wp_login_failed",""]},{"file":"\/home\/vhosts\/webroot\/wp-includes\/user.php","line":53,"function":"wp_authenticate","args":[null,null]},{"file":"\/home\/vhosts\/webroot\/wp-login.php","line":608,"function":"wp_signon","args":["",""]}]

The exact error as shown on the page:

Login Security Solution: authenticate filter not called

So clearly the plugin is expiring the auth cookie as it should, and then WordPress seems to be trying to reauth with an empty username field?

Daniel,

Thanks for helping us look into this. I’ve now had multiple users report this on two separate WPMU instances, neither of which are running any other plugins which call the authenticate() function. I’ve updated your plugin to the latest version and uncommented out all of the logging calls. I’ll wait for this error to reproduce itself and then share the sanitized log data so we can figure out what’s going on.

FWIW I also ran into this issue on a very bare-bones WPMU site with no wp_authenticate overrides as described above. Clearing my site cookies fixed the issue for the time being but doesn’t explain the root cause.

To extend this, I would like to see an option where you can store a copy of the originals somewhere, and then have resized samples be the ones displayed for website viewers. That way you don’t have to re-upload originals should you want to say go from 800×600 to 1024×768. Of course it should be disable-able for those who are concerned about the disk space implications. ??

You’re not the only one. I’ve disabled both options you’ve mentioned for the time being until the issue is addressed (there’s a thread around here somewhere where alex acknowledges the issue).

I did a little hack for my gallery where I have album pages with galleries listed therein, and when clicking a gallery link, it takes you to a piclens slideshow on top of the parent album page instead of linking elsewhere.

The exceeded memory limit error does not pertain to your allocation of storage space. This is the amount of memory a PHP script is allow to consume before it is stopped, to prevent it from running away from the server. It does appear however the error you’re getting is from WordPress’ own internal memory limit controls.

Create a php file with the following contents:

<?php phpinfo(); ?>

Open the file in your browser and look for a memory_limit setting. Take this value and place it in the wp-config.php in:

define(‘WP_MEMORY_LIMIT’, ’32M’);

(In place of the 32M part.