Lastest Release Crashed website

This resulted from a change to how the core plugin handles the membership functions if memberships are not enabled. Unfortunately, the Advanced Options has a single line of code that looks for one of the functions in the membership object of the core plugin, so when that’s not loaded, it causes a fatal error.

I will need to update Advanced Options to use an API function rather than calling the method in the object class directly, but due to the nature of the error, instead of pushing an update to Advanced Options (for now) what I did was roll back the change in the core plugin so that I can look at other possibilities that will be backwards compatible. That has been pushed out as version 3.4.4.1 of the main plugin. If you update to that, you should be OK.

(When you’ve got a support site subscription, make sure you open a ticket there – I’ll see it sooner.)

• This reply was modified 2 years, 4 months ago by Chad Butler.

I am running WordPress 6.0, 2016 theme, and everything is up to date. The plug in caused this error, which cleared when I deactivated the plug in “PHP Warning: call_user_func_array() expects parameter 1 to be a valid callback, function ‘wpmem_admin_options’ not found or invalid function name in C:\visionroot\wwwroot\wp_inspiration\wp-includes\class-wp-hook.php on line 307

This causes the admin panel not to display, as well as being unable to create a new post.

I am running version 3.4.4.1 of the plugin

Same problem here on two sites after updating 3.4.4 –> 3.4.4.1. Unable to get access to the backend with “critical error” message. After disabling wp-members via ftp I got access back.

3.4.4.2 resolves this issue.

tl;dr
The rollback of code in the 3.4.4.1 release which was to fix the backward compatibility issue in 3.4.4 for WP-Members Advanced Options actually slipped back in one line of code that was intended to remain changed. This was hooking wpmem_admin_options() to WP’s admin_menu action. wpmem_admin_options() no longer exists in the plugin and the process was moved to the admin object. This hook is removed in 3.4.4.2 and all should function as normal at this point.

If anyone has any problems rolling forward or backward, let me know and I’ll walk you through getting it resolved.

Problem solved. Thanks for the super fast fix!

No problem! Glad to hear that resolved it!