bad

Can you elaborate? This doesn’t give me much to go on. I can’t fix issues if I don’t know what they are.

Indeed, sorry for the short review. I hadn’t the time to elaborate on the errors.
After installing the plugin I have :

Notice: Undefined variable: pluginloc in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 80

Warning: Cannot modify header information - headers already sent by (output started at /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php:80) in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/slidedeck2-personal/lib/flash.php on line 63

Warning: Cannot modify header information - headers already sent by (output started at /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php:80) in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/slidedeck2-personal/lib/flash.php on line 63

Notice: Undefined index: multi in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 496

Also, I do not see the instruction custom post type.
These warnings/notices are showing with wp_debug set to true.

Interesting. I have it installed (locally) with 3.4.2 using Twenty Eleven and no other plugins installed. Have you tried that setup? Because I’m getting no warnings/errors at all. (I don’t currently have my wp-config set to debugging true, though – but my error logs show absolutely nothing.)

What happens if you deactivate your Slidedeck plugin? (The “pluginloc” and “multi” variables are only notices, and will not affect how the plugin works – but it’s strange that these are coming up, since this notice only happens when the variables aren’t defined – and they are. Which version of the plugin are you using?)

I’ve had a few people tell me that they can’t see the Instructions menu option to edit it, and in every case (so far) it’s because another plugin is interfering. Unfortunately, no one’s telling me what other plugins are causing conflicts so I can attempt fix it. But in your case, it looks like it’s the Slidedeck plugin – it’s trying to send output to the headers.

My guess would be that the Slidedeck is trying to use pluggable.php, which is necessary for using stuff to check current user login statuses (which my plugin does). I already have it set to check and see if pluggable.php is already being called, and if it is, to NOT do so (therefore bypassing the “headers already sent” errors). But I’m guessing Slidedeck doesn’t check for that, and because my plugin is being called in first, Slidedeck is trying to activate it as well, which results in said error. Which means it’s a Slidedeck issue, not a BEI one. (WordPress activates plugin in alphabetical order – so if Slidedeck was installed first, and then you tried to activate mine, then you’d get this error. But I bet if you deactivate Slidedeck, it’ll work fine – and if you reactivate it, it’ll give you the same error, but possibly naming Slidedeck as the cause)

Can you give that a shot for me? Those are my initial thoughts, but until I can test it myself, I can’t be sure. (I think Slidedeck is a paid-for plugin, as I recall, but I’ll see if I can get it. if I can’t, and deactivating the plugin *does* fix this, let me know.)

I appreciate you getting back with me on this. And if it turns out I’m right, I do hope you edit your review to reflect this.

I’ve just tried deactivating slidedeck, to enable BEI first.
I think you were right since now I only get the ‘multi’ variable as undefined index. But, still can’t see the Custom post type though.
I sure it’ll work on a clean install with no plugins.. but that won’t help.

(Indeed Slidedeck is a paid plugin)

Would love to edit the review (first post) but apparently we can only edit last posted post here.

Nicolas,

No, I wouldn’t expect the plugin to only wok on a clean install with no other plugins ?? But others who have reported they can’t see the custom post type (I’m assuming you mean the menu item in the left-hand sidebar?) have said that’s been due to plugin conflicts. So maybe there’s another plugin that’s doing it? If you can deactivate the plugins and reactivate them to see which ones make it disappear, that would be helpful to me, so I can see why it’s doing this.

Hm I have a plugin for a custom post type I use (products). Will try to deactivate that one first and the others after when I’ll have some spare time to check this. ??
Will ge back to you as soon as I can.

Thank you, I really appreciate it ??

Hello again

Okay so I deactivated the other plugins one by one starting with mine which adds a custom post type.
Of course it was the last one on the list, I’m always lucky like that.

I see the Instructions custom post type while “WordPress SEO” is deactivated.

Hope this helps.

Edit:
When adding a new instruction I have these errors in the ‘instruction page information’ box:

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 217

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 218

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 218

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 218

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 219

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 219

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 219

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 220

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 220

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 220

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 221

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 221

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 221

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 222

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 222

Warning: Illegal string offset 'user_level' in /Users/Nico/Sites/Alys/zonetrial_wp/wp-content/plugins/back-end-instructions/instructions.php on line 222

After posting the instruction these are gone though.

Okay, thanks so much! You’re the second person to tell me they have WordPress SEO activated, and the menu disappears. I’ve also heard from several people that they have other plugins that create CPT’s and that seems to conflict for some reason. So I’ll be looking into WordPress SEO (which I do have, so I’ll test what’s going on there), and a few CPT creators I have.

This helps a lot, and I’ll be working to fix it.

As for your error messages, I *did* see those, and I already have them fixed – just not uploaded yet ?? So when the next release comes out, that will be taken care of. unfortunately, I won’t be able to deal with that until after Christmas…so maybe I can go ahead and just fix these little warning.notice errors *now* (well, sometime today, anyway – but they’re already fixed, so when I get a chance I will) and worry about the (more pressing) issue of the menu item not showing after the holidays.

Thanks again for letting me know what was going on!