Hi cpaboost,
do you host the plugin on localhost (and/or have database cache enabled)?
Please send me the logs from:
http://yourwordpress.com/wp-admin/tools.php?page=permalink-manager.php&debug_editor_sql=1
no i do not have any caching plugins active.
there are no errors listed in my error log file
this is what shows under that debug editor
SELECT * FROM wp_posts WHERE post_status IN (‘publish’) AND post_type IN (‘post’, ‘page’) ORDER BY ID desc LIMIT 10 OFFSET 0
Offset: 0
Page: 1
Per page: 10
Total: 164
Please go to this page:
…/wp-admin/plugin-editor.php?file=permalink-manager%2Finc%2Fpermalink-manager-editor.php&plugin=permalink-manager%2Fpermalink-manager.php
or edit /wp-content/plugins/permalink-manager/inc/permalink-manager-editor.php file directly via FTP:
find this code (Lines #149-#151):
// Grab posts from database
$sql_query = "SELECT * FROM {$wpdb->posts} WHERE post_status IN ($post_statuses) AND post_type IN ($post_types) ORDER BY $orderby $order LIMIT $per_page OFFSET $offset";
$data = $wpdb->get_results($sql_query, ARRAY_A);
and replace it with:
// Grab posts from database
$sql_query = "SELECT * FROM {$wpdb->posts} WHERE post_status IN ($post_statuses) AND post_type IN ($post_types) ORDER BY $orderby $order LIMIT $per_page OFFSET $offset";
$wpdb->flush();
$data = $wpdb->get_results($sql_query, ARRAY_A);
hello,
i replaced the code, deactivated the plugin and reactivated it
it did not work. i cannot get past page 1 still.
any idea what the problem could be?
actually nevermind, i just noticed under ‘screen option’s i could set the # of posts per page, and i said that show all my posts on the same page. not sure what the issue as to why it can’t go beyond the first place. i pretty much disabled almost every plugin on my site and it still doesnt work. but i guess this is the workaround to make it work.
Hi again cpaboost,
could you provide me with temp. admin account to your WP installation?
no, everything works fine as long as you change the screen options and set to show everything on one page
Hi cpaboost,
could you check if the issue still occurs in 0.4.8 version of the plugin?
Best Regards,
Maciej
