Annotum Theme conflict?

Hi.

Last night I began experimenting with the Annotum themes. There are currently two, the main theme and one child theme that are available.

Annotum is designed for scholarly reviews, and adds an additional type of custom post that they call an article to wp functionality. So there is the normal default post, and then there is an article that allows for peer editing and peer reviews.

After creating a test article, I got the following error message when I selected the SAVE button:

http://domain.com/wp-admin/post.php and then get the following error message:
Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /path-to/wp-includes/post.php on line 2996

Warning: stripos() [function.stripos]: needle is not a string or an integer in /path-to/wp-includes/functions.php on line 658

Warning: stripos() [function.stripos]: needle is not a string or an integer in /path-to/wp-includes/functions.php on line 661

Warning: Cannot modify header information - headers already sent by (output started at /path-to/wp-includes/post.php:2996) in /path-to/wp-includes/pluggable.php on line 876

I did a google search and contacted their support, and the trouble may be caused by a PayPal plugin… so I’m concerned that s2member might be involved.

I’m concerned that s2member might be involved because I seem to recall reading that there’s no support for custom posts (such as the Article feature that Annotum creates)?

Have you tested deactivating s2Member and other plugins to see if the errors go away to confirm what the theme conflicts with?

Okay, I installed a clean copy of WPMU, installed s2Member Pro, installed the Annotum Themes, tested both, they worked, then installed the Capability Manager Enhanced plugin, and it still worked.

s2Member is not the problem, it’s another plugin.

Thanks

Okay, I installed a clean copy of WPMU, installed s2Member Pro, installed the Annotum Themes, tested both, they worked, then installed the Capability Manager Enhanced plugin, and it still worked.

It’s possible something got mixed up in your database and something weird got send to a call to something in one of your plugins. I’d recommend resetting everything to defaults and seeing if that helps.