Hello in Christ!

We have a site running WP 3.0 RC1 and Role Scoper 1.2.2 along with several other plugins.

We are using a child theme of Twenty Ten, which (so far) is CSS only. No 'functions.php' file in the child theme.

As soon as we activated the plugin and set a page permission for a user (role: author), we started randomly getting error messages (see below) displayed right within the main menu bar (a Twenty Ten theme feature) at the top, which show up (seemingly at random) while browsing the frontend of the site:

Warning: preg_split() expects parameter 2 to be string, array given in ~PATH~/wp-content/plugins/role-scoper/hardway/hardway-taxonomy_rs.php on line 235

Warning: Invalid argument supplied for foreach() in ~PATH~/wp-content/plugins/role-scoper/hardway/hardway-taxonomy_rs.php on line 237

We can refresh a page that shows the error, and it disappears after the refresh. The errors occasionally show, and it seems to be regardless of what user is logged in, and even if no user is logged in.

Any ideas what we could tweak to stop the errors from being thrown?

Same here, it's random too. If you reload the page sometime you get it sometimes not. I think it's related to the new wordpress menu. I only get the error when I have a menu item which is a post category. When there is just pages no error.

Warning: preg_split() expects parameter 2 to be string, array given in C:\xampplite\htdocs\bsa\wp-content\plugins\role-scoper\hardway\hardway-taxonomy_rs.php on line 235 Warning: Invalid argument supplied for foreach() in C:\xampplite\htdocs\bsa\wp-content\plugins\role-scoper\hardway\hardway-taxonomy_rs.php on line 237

While I am logged out, I am being served static HTML pages that were generated by Quick Cache.

I am in the process of testing multiple log-outs (with "purge and refresh" of the cache in between) to see what happens.

On my first pass through (within that scenario) currently there are two certain places in the menu that always show the error. The error messages always display on those two pages, because all is "frozen" and locked into HTML by the Quick Cache program when I am logged out.

One of the items that always shows the error is the main blog page that displays all posts in all categories.

The other one that always shows the error is a category page that is set to show only posts in a certain sub-category. I have other such category pages that don't display the error (and they are displaying both parent-childless categories, parent-with-child categories, and child categories, aka sub-categories).

More soon.

I tried several times to clear the cache (both manually and via the automatic clearing that occurs when editing a post) and found that the Quick Cache plugin could not clear the cache as long as Role Scoper was active.

I then tried after deactivating Role Scoper, and Quick Cache immediately began to work again. At this point I have gathered that Quick Cache and Role Scoper don't yet play nice with each other.

I will probably temporarily deactivate caching while I do some testing on Role Scoper. However, since the Role Scoper errors are occuring even when caching is not an issue, eventually I will either need to get Role Scoper fixed for WP3 menus, or deactivate it until it's upgraded.

After more testing, I have refined my hypothesis:

While caching is turned off:

Error seems to always show on the very first viewing of the frontend after logging in, and nowhere else, and it only shows the first time a different user logs in.

To explain further:

If I log in as a certain for the first time after logging out as another user, and view the frontend, I get the error. If I log out, and log in again as the same user, and visit the frontend again, I do not get the error.

If I log out, and log in again as a different user, and visit the frontend, I see the error. If I log out and back in again as that same user and visit the frontend, I will not see the error.

John, can you do a little test and see if that is so on your end?

Thanks!