Something in Role Scoper 1.2.7 is rewriting my .htaccess file in the root of my site with errant code that is causing my site to go down with a 500 Server Error. I (and tech support) have been able to locate and rewrite the errant code to get my site back up; however, we were able to trace the code back to the Role Scoper Plugin.

I use WP 3.0.1

thanks! Appreciate your work on this!

Scott

It is a single site installation (not WPMU, just WP).

Here is the code:

the first time, Role Scoper inserted the following into my .htaccess file

WordPress

This should have been #WordPress Begin

the second time, it inserted this: T_FILENAME} !-d

instead of this: RewriteCond %{REQUEST_FILENAME} !-d

hope this helps!

Scott

Can you try updating wp-content/plugins/role-scoper/rewrite-rules_rs.php as follows and let me know if it clears your error?

change:

add_action( 'shutdown', create_function( '', 'global $wp_rewrite; if ( ! empty($wp_rewrite) ) { $wp_rewrite->flush_rules(true); }' ) );

to:

add_action( 'shutdown', create_function( '', 'global $wp_rewrite; if ( ! did_action("delete_option_rewrite_rules") && ! empty($wp_rewrite) ) { $wp_rewrite->flush_rules(true); }' ), 999 );

I will apply the code to my site.

To answer the above question… only 1 line in the code was appended incorrectly by RoleScoper in the above examples. The other lines of code were correct. The one line of incorrect code broke the whole site though.

thanks so much!

in Jesus,

Scott

I just wanted to make sure you have the code revision that includes the ", 999″ argument.

Operations that may have triggered .htaccess file rewrite (and corruption) include updating a page, updating permalink settings, updating options and activating plugins.