Hi to you, and thanks for your question.
To be clear: Are you getting the message as an error warning or notice that doesn’t prevent activation or impair plug-in functionality? Is the warning/notice appearing on your plugins page, or somewhere else (like in some other debugging tool)? Is it persistent (shows up continuously)?
I can put out an update that initializes the variable as empty – which seems like the right thing to do anyway! – but, since the error doesn’t come up on activation or in debuggers for me, it would be helpful for me if you would confirm on your end.
If you’re comfortable editing your plugins, you could go to Plugins/Editor, select Category Featured Images – Extended and, in category-featured-images-extended.php go to line 749 – near the beginning of the last major function, get_image( $object_id ), MAIN FALLBACK FUNCTION – and insert the following line immediately after //get fallback category ID:
$fall_cat_id = '' ;
So, it should look like this, including line 748:
//get fallback category ID
$fall_cat_id = '' ;
if ( get_cat_ID( $fall_cat) ) {
etc.
That should be it, and I hope that clears the message! If I don’t hear from you first, I’ll push out the update anyway by tomorrow.
Thanks!
-
This reply was modified 9 years, 6 months ago by
CK MacLeod.
-
This reply was modified 9 years, 6 months ago by
CK MacLeod.
-
This reply was modified 9 years, 6 months ago by
CK MacLeod.
-
This reply was modified 9 years, 6 months ago by
CK MacLeod.
Since it’s been several days since the first support request, since I haven’t received necessary clarification on the reported problem and whether it’s anything more than a passing annoyance on peculiar installations, and since I think the simple solution described SHOULD solve it, I’m inclined to close this support thread and, as I said, push out the micro-update (though four or five days later not the day after, after re-checking it and seeing if there are other revisions worth making).
Any reason not to go ahead, @auludag?
Don’t know if you’re still out there, @auludag. I’ve updated the plug-in (to version 1.32) incorporating the change (and doing a little bit of additional housekeeping). I’m going to mark this topic resolved, pending further replies. Please feel free to let me know if the problem is persisting, or, alternatively, please confirm that it’s fixed, if you get a chance.
Thanks again for bringing this matter to my attention.