Doodlebee

Did you get this sorted yet? I’m willing to help, but I can’t if I don’t have more information.

Hugh, if you have the same warning, just setting the line:

define('WP_DEBUG', false);

in your wp-config.php file should solve the problem.

Well, this is only a warning, so it doesn’t affect how the plugin works. However, if you want to fix it, you can open up instructions.php, and change line 601 from this:

$path = plugin_dir_url();

to this:

$path = plugin_dir_url(__FILE__);

Alternatively, you can just shut off error messages in your WordPress install.

I can’t replicate this issue, though – so I’m not 100% sure that will work.

Thanks Rebecca – I just uploaded the fix. Might take a few minutes to come through. It was my bad – a function was missing a (quite an important) variable! Thanks for letting me know!

(ha – just finished reading the rest of your post – I just saw “Fatal error” and went right to work! – but yes – that was the important missing variable! Thanks for the catch 🙂 )

Okay – thanks for bringing this to my attention. You’ll have to contact the YAPB plugin author, because really, only HE can fix the issue, since it’s with his plugin. I have *no idea* why my plugin makes some of these errors show. All I know is that the warning you described you were seeing in the original post made me look at his class. Apparently he’s recently popped in a fix for another issue – the fix was this exact line. So in that file (wp-content/plugins/yet-another-photoblog/lib/Yapb.class.php on line 821) the line he has is this:

if ($post && property_exists($post, 'image')) {

The problem is, he’s just checking for a post of ANY type. Could be a post, a page, an attachment – or a Custom Post Type. Back End Instructions runs on Custom Post Types. So it looks like YAPB doesn’t make any sort of differentiation between a regular post, and a CPT – so it’s tossing out this error.

I fixed it locally by changing that line to:

if ($post['post_type'] == 'post' && property_exists($post, 'image')) {

And BAM. Message goes away. Of course, this will only work until his next release – and if he doesn’t do something about checking for CPT’s, and you upgrade, your edit will be overwritten. But that’s the best I can offer.

Otherwise, I figured out a couple of the issues BEI was having, and I’m going to put out an update here in the morning to fix those bugs. between the two, your problem should be solved. But I would HIGHLY recommend you make the author of YAPB know about the issue with CPT’s. otherwise, the issue will remain.