Reply To: bbPress 2.5.4
When a plugin is updated via WordPress’s Admin Interface
- It is deactivated
- New files are pulled down
- It is reactivated
Problem is, the bbPress Notify Spam plugin isn’t coded in such a way to fail gracefully when bbPress is not active. Thus when WordPress tries to reactivate bbPress, a fatal error occurs. Not because of bbPress, but because bbPress is temporarily not there, and bbPress Notify Spam tries to call bbPress functions.
The fix is for that plugin author to use bbPress’s sub-actions and filters to include its files and execute code, and not call bbPress core functions without confirming bbPress is active previously in its call stack.
Sorry y’all for the inconvenience, but there’s little we can do in bbPress core to prevent this type of thing.
