Mad Max

You are right. I usually use permalinks so this problem has never come to my mind! I think it worths a rewrite of the function to take in account your use case.
Taking out cat names/values from the function and grouping them in a “pagination settings” section of the function.php files (clearly a plugin with an admin page should be the best solution), we can rewrite the code like this:

Permalinks enabled

//POSTS PER PAGE (permalinks on)
$my_ppp =array(
	'category' => array(
		'cat1_name' => X,
		'cat2_name' => Y,
		'cat3_name' => Z,
	),
	'search' => K,
);

Permalinks disabled

//POSTS PER PAGE (permalinks OFF)
$my_ppp =array(
	'category' => array(
		'cat1_ID' => X,
		'cat2_ID' => Y,
		'cat3_ID' => Z,
	),
	'search' => K,
);

And then the function:

if ( isset( $my_ppp ) && is_array( $my_ppp ) && count( $my_ppp ) ) add_filter('request', 'cure_wp_amnesia_on_query_string');
function cure_wp_amnesia_on_query_string($query_string){
	global $my_ppp;
	if ( !is_admin() ){
		if ( isset( $my_ppp['category'] ) && is_array( $my_ppp['category'] ) )  {
			if ( isset( $query_string['category_name'] ) ) {
				foreach ( $my_ppp['category'] as $category_name => $ppp ) {
					if ( $query_string['category_name'] == $category_name ) {
						$query_string['posts_per_page'] = $ppp;
						break;
					}
				}
			}elseif ( isset( $query_string['cat'] ) ){
				foreach ( $my_ppp['category'] as $cat_id => $ppp ) {
					if ( $query_string['cat'] == $cat_id ) {
						$query_string['posts_per_page'] = $ppp;
						break;
					}
				}
			}
		}
		if ( isset( $my_ppp['search'] ) && isset( $query_string['s'] ) )  {
			$query_string['posts_per_page'] = $my_ppp['search'];
		}
	}
	return $query_string;
}

Hi Kevin,
ok, found it. That was an oversight on my part: I’ve copy&pasted the code on your site here, without a check in the downloadable file.

Cheers

Your argument is logically flawless, but in practice I think is more a matter of preferences.
The “Descriptions” can be some paragraphs long while “Titles” are usually some words long so I think is more suitable to show a single phrase in case images cannot be loaded.

So I’ve made a try finally!

I think your plugin is great but it lacks one setting: the database prefix!

My goal is to clone a wp site to another fresh wp installation not to just change domain name, but to create a clone site and then change only relevant contents and images, but mantaining all plugins and settings.
So, at 99% of times, I use a different database prefix.

I’ve tried a migration toward a new fresh 3.3 WP installation with different db prefix and your plugin correctly unserializes, changes and serializes again all data containing the old domain name, create backups and upload them to the new wp, but it uses the old db prefix and there’s no way to instruct the plugin to use the new one.

Another thing I came across (but I made only one test) is that, even if I setted the correct path to the new wp site backup folder for your plugin, the backfiles was uploaded in the root folder, ie:

new-site.com/DBBackup-13250069441.sql
new-site.com/Backup-13250069451.zip

So I moved manually those files to the right folder and then I completed the migration process.

Let me know if you need more infos.
Regards, Daniele.

@lonchbox: have you tried the solution in the first post at the top?

1) line 50 in scissors.php:

load_plugin_texdomain('scissors', $scissors_locale_dir);

change to

load_plugin_texdomain('scissors',false, $scissors_locale_dir);