Biranit

To fix this, open the file /plugins/theme-my-login/includes/class-theme-my-login.php

Find the function

public static function check_password_reset_key( $key, $login ) {

And comment out (add // at the start of the line) this line:

$key = preg_replace( '/[^a-z0-9]/i', '', $key );

That’s it. The end result should be:

public static function check_password_reset_key( $key, $login ) {
		global $wpdb;

		// $key = preg_replace( '/[^a-z0-9]/i', '', $key );

		if ( empty( $key ) || ! is_string( $key ) )
			return new WP_Error( 'invalid_key', __( 'Invalid key' ) );

		if ( empty( $login ) || ! is_string( $login ) )
			return new WP_Error( 'invalid_key', __( 'Invalid key' ) );

		$user = $wpdb->get_row( $wpdb->prepare( "SELECT * FROM $wpdb->users WHERE user_activation_key = %s AND user_login = %s", $key, $login ) );

		if ( empty( $user ) )
			return new WP_Error( 'invalid_key', __( 'Invalid key' ) );

		return $user;
	}

I have no idea why that line is there, it’s redundant and just strips off all letters and numbers from the key, so obviously it then won’t match the key in the db…

I did this on our site and it all works fine now.

I am experiencing the same problem. Very frustrating. Can anyone help?

the wp_options renaming works for me.

@arbe-vanbeek: not a very useful solution, but like you I wanted the styelsheet off. So I edited the plugin (you can do that via Plugin -> Editor) and commented out line 17:

// add_action( 'wp_enqueue_scripts', 'category_posts_widget_styles' );

(added // at the start of the line)

I also added, on line 3, on the plugin’s description, a note to myself — so that if I see an upgrade for the plugin, I’ll remember to comment out the stylesheet again:

Description: (MODIFIED: REMOVED STYLESHEET) Adds a widget that shows the most recent posts from a single category.

I hope in future versions, though, the inclusion of the stylesheet will be an OPTION.

Good luck! I’m sorry we’re all angry at you ??

By the way, it’s extremely rare that I criticize a developer who is giving something for free to the community. It’s ungrateful.

But this is such a huge failure, with implications for thousands of websites, that I find the negligence shocking.

@mrinal Kanti Roy: it would have been better if you launched a new plugin called “Category Posts Widget Redux” or something, because you just cannot make such a fundamental change without taking care of backward compatibility. If your upgrade erases the widget, then this is not an upgrade — it’s a clean install!

It’s not too late. Add a backward compatibility with a $wpdb query to update the wp_options table (see my above post) and at least those who have not upgraded yet won’t get so badly affected.

@arbe-vanbeek:

I am not sure, because I only realized what he did after discovering the widgets have disappeared and rebuilding them…

But try it out! I got a feeling it will fix it, and if you don’t have the widgets then you really have nothing to lose by trying this, at this point…

UPDATE wp_options SET option_name='widget_category-posts' WHERE option_name='widget_categoryposts'

(Obviously don’t do this if you don’t know your way around MySQL etc…)

The new version stores in the database with option_name widget_category-posts while previously it was widget_categoryposts

So obviously ANYONE who upgrades the plugin will lose their widgets.

What a bad, bad, bad move. Seriously. You should have at least made sure there’s backward compatibility, checking if option exists and renaming it accordingly.

I run WPSC as well as WPTP without a problem, and I DON’T follow the WPTP instructions.

This is all I have done, and it works:

1) Check the box in WP Super Cache advanced settings for “Mobile device support”

2) Replaced the WPSC part in the .htaccess file with the following:

# BEGIN WPSuperCache
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
AddDefaultCharset UTF-8

RewriteCond %{REQUEST_URI} !^.*[^/]$
RewriteCond %{REQUEST_URI} !^.*//.*$
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:X-Wap-Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP:Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP_USER_AGENT} !^.*(2.0\ MMP|240x320|400X240|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|Googlebot-Mobile|hiptop|IEMobile|KYOCERA/WX310K|LG/U990|MIDP-2.|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|PlayStation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|SHG-i900|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|webOS|Windows\ CE|Windows\ Phone|WinWAP|YahooSeeker/M1A1-R2D2|iPhone|iPod|Android|BlackBerry9530|LG-TU915\ Obigo|LGE\ VX|webOS|Nokia5800).* [NC]
RewriteCond %{HTTP_user_agent} !^(w3c\ |w3c-|acs-|alav|alca|amoi|audi|avan|benq|bird|blac|blaz|brew|cell|cldc|cmd-|dang|doco|eric|hipt|htc_|inno|ipaq|ipod|jigs|kddi|keji|leno|lg-c|lg-d|lg-g|lge-|lg/u|maui|maxo|midp|mits|mmef|mobi|mot-|moto|mwbp|nec-|newt|noki|palm|pana|pant|phil|play|port|prox|qwap|sage|sams|sany|sch-|sec-|send|seri|sgh-|shar|sie-|siem|smal|smar|sony|sph-|symb|t-mo|teli|tim-|tosh|tsm-|upg1|upsi|vk-v|voda|wap-|wapa|wapi|wapp|wapr|webc|winw|winw|xda\ |xda-).* [NC]
RewriteCond %{HTTP:Accept-Encoding} gzip
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{SERVER_NAME}/$1/index.html.gz -f
RewriteRule ^(.*) "/wp-content/cache/supercache/%{SERVER_NAME}/$1/index.html.gz" [L]

RewriteCond %{REQUEST_URI} !^.*[^/]$
RewriteCond %{REQUEST_URI} !^.*//.*$
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:X-Wap-Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP:Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP_USER_AGENT} !^.*(2.0\ MMP|240x320|400X240|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|Googlebot-Mobile|hiptop|IEMobile|KYOCERA/WX310K|LG/U990|MIDP-2.|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|PlayStation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|SHG-i900|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|webOS|Windows\ CE|Windows\ Phone|WinWAP|YahooSeeker/M1A1-R2D2|iPhone|iPod|Android|BlackBerry9530|LG-TU915\ Obigo|LGE\ VX|webOS|Nokia5800).* [NC]
RewriteCond %{HTTP_user_agent} !^(w3c\ |w3c-|acs-|alav|alca|amoi|audi|avan|benq|bird|blac|blaz|brew|cell|cldc|cmd-|dang|doco|eric|hipt|htc_|inno|ipaq|ipod|jigs|kddi|keji|leno|lg-c|lg-d|lg-g|lge-|lg/u|maui|maxo|midp|mits|mmef|mobi|mot-|moto|mwbp|nec-|newt|noki|palm|pana|pant|phil|play|port|prox|qwap|sage|sams|sany|sch-|sec-|send|seri|sgh-|shar|sie-|siem|smal|smar|sony|sph-|symb|t-mo|teli|tim-|tosh|tsm-|upg1|upsi|vk-v|voda|wap-|wapa|wapi|wapp|wapr|webc|winw|winw|xda\ |xda-).* [NC]
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{SERVER_NAME}/$1/index.html -f
RewriteRule ^(.*) "/wp-content/cache/supercache/%{SERVER_NAME}/$1/index.html" [L]

RewriteCond %{REQUEST_URI} !^.*[^/]$
RewriteCond %{REQUEST_URI} !^.*//.*$
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP_USER_AGENT} ^.*(2.0\ MMP|240x320|400X240|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|Googlebot-Mobile|hiptop|IEMobile|KYOCERA/WX310K|LG/U990|MIDP-2.|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|PlayStation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|SHG-i900|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|webOS|Windows\ CE|Windows\ Phone|WinWAP|YahooSeeker/M1A1-R2D2|iPhone|iPod|Android|BlackBerry9530|LG-TU915\ Obigo|LGE\ VX|webOS|Nokia5800).* [NC]
RewriteCond %{HTTP:Accept-Encoding} gzip
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{SERVER_NAME}/$1/index-mobile.html.gz -f
RewriteRule ^(.*) "/wp-content/cache/supercache/%{SERVER_NAME}/$1/index-mobile.html.gz" [L]

RewriteCond %{REQUEST_URI} !^.*[^/]$
RewriteCond %{REQUEST_URI} !^.*//.*$
RewriteCond %{REQUEST_METHOD} !POST
RewriteCond %{QUERY_STRING} !.*=.*
RewriteCond %{HTTP:Profile} !^[a-z0-9\"]+ [NC]
RewriteCond %{HTTP_USER_AGENT} ^.*(2.0\ MMP|240x320|400X240|AvantGo|BlackBerry|Blazer|Cellphone|Danger|DoCoMo|Elaine/3.0|EudoraWeb|Googlebot-Mobile|hiptop|IEMobile|KYOCERA/WX310K|LG/U990|MIDP-2.|MMEF20|MOT-V|NetFront|Newt|Nintendo\ Wii|Nitro|Nokia|Opera\ Mini|Palm|PlayStation\ Portable|portalmmm|Proxinet|ProxiNet|SHARP-TQ-GX10|SHG-i900|Small|SonyEricsson|Symbian\ OS|SymbianOS|TS21i-10|UP.Browser|UP.Link|webOS|Windows\ CE|Windows\ Phone|WinWAP|YahooSeeker/M1A1-R2D2|iPhone|iPod|Android|BlackBerry9530|LG-TU915\ Obigo|LGE\ VX|webOS|Nokia5800).* [NC]
RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/supercache/%{SERVER_NAME}/$1/index-mobile.html -f
RewriteRule ^(.*) "/wp-content/cache/supercache/%{SERVER_NAME}/$1/index-mobile.html" [L]
</IfModule>

# END WPSuperCache

I have this running on four sites for the past 18+ months, and I think maybe once or twice in that period I had to delete a cached file that was wrongly served.

Hope this helps.

you have the ability to exclude. Under the WP Super Cache settings -> Advanced, you have the following section:

Accepted Filenames & Rejected URIs

Do not cache the following page types. See the Conditional Tags documentation for a complete discussion on each type.
Single Posts (is_single)
Pages (is_page)
Front Page (is_front_page)
Home (is_home)
Archives (is_archive)
Tags (is_tag)
Category (is_category)
Feeds (is_feed)
Search Pages (is_search)
Author Pages (is_author)

So just check the boxes of the pages you don’t want to cache.

Oh, brilliant. Thanks a lot Donncha ??

Thanks a lot, Donncha!!!

Thanks, Steve ??

Steveb123: Could I get a link to Autopmise please? I can’t find this plugin anywhere. In fact, the only results on Google are you mentioning it – and I’m very curios about it. Thanks ??

Gary, I’m sorry but what you say just does not make sense, because you’re ignoring the pullzone. The processing and delivery speed of the origin has a major effect on overall delivery speed. WordPress is a dynamic web application, using some of the most resource-thirsty (not to mention slow) processing there is. Without something like wpsc it makes the origin very slow and will therefore affect the delivery. Of course, if all you got is a single installation of vanilla Twenty-Twelve / no plugins / no nothing / one post a day, then the benefits are somewhat diminished. But with 4 million visitors a month and some 50,000 articles, wordpress alone – even with PSS – is not good enough and certainly not as fast as it is with wpsc.

But PSS is not the origin. It pulls its content from the origin server – why would you not want to run wpsc there? The speed difference is huge. And the end user feels it.

We don’t use PSS but we do serve our entire site via CDN, and there is no doubt the combination – wpsc on the origin with CDN for front end – is the perfect solution.