Error in admin page after update.

conflicts with multiple WordPress files are reported in debug mode.

Could you indicate what the errors are?

Debug and Query Monitor error messages.
————–
Parse error: syntax error, unexpected ‘)’ in /html/wp/wp-content/plugins/wp-members/includes/admin/tabs/class-wp-members-admin-tab-options.php on line 184
————–
Fatal error: Uncaught Error: syntax error, unexpected ‘)’
in /html/wp/wp-content/plugins/wp-members/includes/admin/tabs/class-wp-members-admin-tab-options.php on line 184

Call stack:

WP_Members_Admin_API::load_dependencies()
wp-content/plugins/wp-members/includes/admin/class-wp-members-admin-api.php:52

WP_Members_Admin_API::__construct()
wp-content/plugins/wp-members/includes/class-wp-members.php:657

WP_Members::load_admin()
wp-includes/class-wp-hook.php:287

WP_Hook::apply_filters()
wp-includes/class-wp-hook.php:311

WP_Hook::do_action()
wp-includes/plugin.php:478

do_action()
wp-admin/admin.php:175

require_once()
wp-admin/options-general.php:10

Got error too!

i just updated to 3.3.7 & have no problems

I have the same problem but the errors are different then I post my thanks

I have the same problem but the errors are different then I post my…..thanks

Now solved as follows.

class-wp-members-admin-tab-options.php
on line 184

‘wp-members’, ),
-> ‘wp-members’ ),

, Was deleted

I want the official patch.

Here’s the run down…

There’s an extra comma in a translation function call that shouldn’t be there. This will be ignored in some environments (i.e. if you don’t get an error on the plugin’s main options page, then your environment ignores the syntax error) and in others, it will throw a critical error.

The bigger part of this is that it is in a section meant for a future release (likely 3.3.8) and was not supposed to be in this release. It was not included in the beta release and somehow got slipped in between the beta and the production release last night.

For anyone reading later, this ONLY affects the loading of the plugin’s main settings page. It does not create an error with the front end functioning of the plugin, nor with any of the other admin elements.

I have pushed out version 3.3.7.1 which corrects the problem by removing the feature setting that shouldn’t be there in the first place. You can update to 3.3.7.1 to resolve the issue (if it affects you) or to just make sure you’re on the most recent production code base.

For anyone else who got a sneak peek of the setting before I removed it (i.e. your environment did not throw an error on syntax), you’ll see that I’m adding the ability to turn on/off WP-Members fields in the WooCommerce registration when WC is installed and active. There will be more information on that when the time comes ??

Thanks for those that reported the problem, and for helping me track it down.