Hello Algaraba, I am the author of Register Plus Redux. I can tell you that that problem with Back-End Instructions is that on line 44 of instructions.php, Back-End Instructions loads pluggable.php. Now, I am not entirely sure why, the preceding line checks for a function ‘wp_set_current_user’ but I don’t see that function actually utilized anywhere in Back-End Instructions. If you are interested in determining whether Back-End Instructions really needs to load pluggable.php you could comment out lines 43 through 45 with preceding // characters, if the plugin still works as expected, then bang, problem solved, otherwise you and/or this plugin’s developer will need to review their code to move code that requires pluggable functions further down the page life cycle.
The problem is that plugins are often loaded in alphabetical order. Back-End Instructions is loading pluggable.php which should be loaded after every other plugin. By loading pluggable.php prior to other plugins completing their initialization they cannot create their own pluggable functions, thus breaking the purpose of pluggable.php. This is all rather complicated if you aren’t a WordPress plugin developer. Regardless I ran into a similar problem with Maintenance Mode several years ago, the core concepts should still ring true.
http://radiok.info/blog/the-case-of-maintenance-mode/
Thanks “Radio K”. Your advice has worked well. I also had to remove the line of code number 46. like this:
//if( !function_exists('wp_set_current_user') ) {
// require(ABSPATH . WPINC . '/pluggable.php');
//}
Do I have to take special care when upgrading WP or the plugin “Back End Instructions” with these code changes? Can generate any other conflict with other features? I have no idea of PHP programming.
Thank you very much for your support.
Note: I think that helps custom messages no longer appear on the dashboard home page. The rest works perfectly, I must study more in depth the issue.
The problem is that plugins are often loaded in alphabetical order. Back-End Instructions is loading pluggable.php which should be loaded after every other plugin.
Exactly. I actually have a list of issues to fix, and this is one that I’m working on now. I have the fix in place, but I’m just testing to be sure it’s working. It’ll be fixed in the next release.
Thanks Doodlebee.
Arise any problem with this castration of functions in your practical and excellent plugin?
I am very grateful for your support.
Okay, I’m marking this as resolved. I’ve fixed the issue locally, but I can’t upload the update until tomorrow – but it will be done 🙂 If you have any other problems, let me know!
Excellent! You are a master.
Thank you very much for your work which I appreciate very much
