get_post_edit_link / redirect broken

I’ve been working on a site on my localhost and this morning installed the Role Scoper plugin to try and mess around with comment moderation. I deactivated Role Scoper and the admin panel “broke”, for lack of a better term. I could only access the login page and login was failing. Cleared all data, tried on different browsers and machines, no luck. Before I had cleared data, phpMyAdmin was also having issues with sessions.

Went to a clean install, then added my theme and media. Exported the db, cleaned out all Role Scoper tables and options in standard options table, then imported into a new db. Manually edited the top-level .htaccess to make sure mod_rewrite was properly configured. I can access the dashboard and successfully make edits, but redirects are not properly occurring on Admin actions.

When I edit or add posts, pages, options, or anything that does not use AJAX to make changes, I get redirected to wp-admin/[thing].php with no query vars appended, and the page is blank.

When I trash anything, I get to a blank page at wp-admin/?[thing]=[id]&action=trash&_wpnonce=[nonce].

Hoping someone has had a similar experience with Role Scoper in the past and can offer a quick fix, I’ve been fighting with this for 5-6 hours now.

Questions:
1) I’ve noticed that in the post publishing and editing form “_wp_http_referer” and “_wp_original_http_referer” are the only inputs with name attributes but no id attributes. Is this by design?

2) When publish and edit actions occur properly, in what order do functions for determining the redirect URL occur? If I can narrow down the potentially offending functions I may be able to edit them.

3) Could this be an issue of Role Scoper redefining core cap definitions that came over with the exported data? I’ve noticed there’s a lot of checking user capabilities in the process of generating the redirect, so if Role Scoper had altered, I could see that being a problem.

4) Could this be an issue with .htaccess? From what I can see, redirect_post should not be dependent upon .htaccess, but I’ve read a bunch of threads about Role Scoper issues being fixed by repairing corrupt .htaccess files.