Travis Smith

Changing line 48 of custom.php will fix this:
$the_eval = "return ".stripslashes($cond_tag).";";

While it didn’t through an error, if the $cond_tag contains a ;, you may want to remove it from $cond_tag anyways.

Yes there is…

Joe,

SP moderators and members are usually the developers of the various plugins and someone from StudioPress will also reach out to the various plugin developers to get a response for you.

Generally speaking, though, if not listed in the forum, add the comment to www.remarpro.com. Since WordPress announced and brought their Notifications system to light, I have subscribed to all my plugins as have many plugin authors, which will result in faster service and help.

On the other hand, @andrea_r is a superb help and if she asks you to post there, it’s always helpful to do so.

Thanks,

Travis

Ok, the plugin does work as advertised with a clean install. There could be a theme and/or plugin conflict (I suspect there may be a conflict with BuddyPress). However, I cannot test it for a couple months, if I remember.

I fixed this…

Is this still an issue?

The plugin should be working again. Please let me know if there is an issue.

Do you have any plugin conflicts??

I added this back.

`$args = array(‘nav-menu’);
$menus = wp_get_nav_menus($args);`

That doesn’t accomplish anything??

First, have you tried removing all of your plugins and re-activating them one by one to see if there is a plugin conflict?

Thanks! It works with your solution, so I will change it hoping that it may solve some other difficulties!

Have you tried it on a clean install without BuddyPress or the other plugins to determine if there is a plugin conflict?

This is compatible for the most recent version of Shopp, 1.2.x.

Sorry. Typo. Remove/Replace, same thing right!?

The plugin has been updated with a fix.