Version 2.2.2 Class WPCAMeta Not Found Error

Thank you for reporting this. I am unable to reproduce this problem, can you provide a more detailed stack trace + PHP version?

Thank you very much for a quick answer, Joachim. It seems this appears in a combination with another plugin and I reported this too hastily. Sorry about that!

I will do some more testing and report back later.

It is possible that this change is incompatible with other plugins, if they call wp_set_current_user() earlier than expected: https://plugins.trac.www.ads-software.com/browser/restrict-user-access/trunk/app.php#L145

If you keep seeing the fatal error, could you please also provide a list of other plugins you use? Then I will see if I can reproduce it on my end and provide a fix.

Got the same problem. Any fix?

03.03.2022 09:33:16 xyz.tld [client xx.xx.xx.xx] Stack trace:
03.03.2022 09:33:16 xyz.tld [client xx.xx.xx.xx] #0 /wp-content/plugins/restrict-user-access/level.php(246): RUA_Level_Manager->_init_metadata()
03.03.2022 09:33:16 xyz.tld [client xx.xx.xx.xx] #1 /wp-content/plugins/restrict-user-access/app.php(596): RUA_Level_Manager->metadata()
03.03.2022 09:33:16 xyz.tld [client xx.xx.xx.xx] #2 /wp-includes/class-wp-hook.php(307): RUA_App->process_level_automators()
03.03.2022 09:33:16 xyz.tld [client xx.xx.xx.xx] #3 /wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
03.03.2022 09:33:16 xyz.tld [client xx.xx.xx.xx] #4 /wp-includes/plugin.php(474): WP_Hook->do_action()
03.03.2022 09:33:16 xyz.tld [client xx.xx.xx.xx] #5 /wp-includes/pluggable.php(48): do_action()
03.03.2022 09:33:16 xyz.tld [client xx.xx.xx.xx] #6 /wp-includes/user.php(3375): wp_set_current_user()
03.03.2022 09:33:16 xyz.tld [client xx.xx.xx.xx] #7 /wp-includes/pluggable.php(70): _wp_get_current_user()
03.03.2022 09:33:16 xyz.tld [client xx.xx.xx.xx] #8 /mnt/web3 in /wp-content/plugins/restrict-user-access/level.php on line 260
03.03.2022 09:33:18 xyz.tld [client xx.xx.xx.xx] PHP Fatal error:  Uncaught Error: Class 'WPCATypeManager' not found in /wp-content/plugins/restrict-user-access/lib/wp-content-aware-engine/core.php:178
03.03.2022 09:33:18 xyz.tld [client xx.xx.xx.xx] Stack trace:
03.03.2022 09:33:18 xyz.tld [client xx.xx.xx.xx] #0 /wp-content/plugins/restrict-user-access/level.php(458): WPCACore::types()
03.03.2022 09:33:18 xyz.tld [client xx.xx.xx.xx] #1 /wp-includes/class-wp-hook.php(307): RUA_Level_Manager->create_restrict_type()
03.03.2022 09:33:18 xyz.tld [client xx.xx.xx.xx] #2 /wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
03.03.2022 09:33:18 xyz.tld [client xx.xx.xx.xx] #3 /wp-includes/plugin.php(474): WP_Hook->do_action()
03.03.2022 09:33:18 xyz.tld [client xx.xx.xx.xx] #4 /wp-settings.php(587): do_action()
03.03.2022 09:33:18 xyz.tld [client xx.xx.xx.xx] #5 /wp-config.php(93): require_once('/mnt/web301/e1/...')
03.03.2022 09:33:18 xyz.tld [client xx.xx.xx.xx] #6 /wp-load.php(50): require_once('/mnt/web301/e1/...')
03.03.2022 09:33:18 xyz.tld [client xx.xx.xx.xx] #7 /wp-blog-header.php(13): require_once('/mnt/web301/e1/...')
03.03.2022 09:33:18 xyz.tld [client xx.xx.xx.xx] #8 / in /wp-content/plugins/restrict-user-access/lib/wp-content-aware-engine/core.php on line 178

Joachim, here is the stack trace:

Fatal error: Uncaught Error: Class 'WPCAMeta' not found in /srv/htdocs/wp-content/plugins/restrict-user-access/level.php:260
Stack trace:
#0 /srv/htdocs/wp-content/plugins/restrict-user-access/level.php(246): RUA_Level_Manager->_init_metadata()
#1 /srv/htdocs/wp-content/plugins/restrict-user-access/app.php(596): RUA_Level_Manager->metadata()
#2 /wordpress/core/5.9.1/wp-includes/class-wp-hook.php(307): RUA_App->process_level_automators('')
#3 /wordpress/core/5.9.1/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)
#4 /wordpress/core/5.9.1/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
#5 /wordpress/core/5.9.1/wp-includes/pluggable.php(48): do_action('set_current_use...')
#6 /wordpress/core/5.9.1/wp-includes/user.php(3375): wp_set_current_user(0)
#7 /wordpress/core/5.9.1/wp-includes/pluggable.php(70): _wp_get_current_user()
#8 /wordpress/core/5.9.1/wp-includes/user.php(628): wp_get_current_user()
#9 /wordpress/plugins/jetpack/10.8-a.1/jetpack_vendor/automattic/jetpack-connection/src/class-manager.php(687): get_current_user_id()
#10 /wordpress/plugins/jetpack/10.8-a.1/jetpack_vendor/automattic/jetpack-tracking/src/class-tracking.php(240): Automattic\Jetpack\Connection\Manager->is_user_connected()
#11 /wordpress/plugins/jetpack/10.8-a.1/class.jetpack.php(944): Automattic\Jetpack\Tracking->should_enable_tracking(Object(Automattic\Jetpack\Terms_Of_Service), Object(Automattic\Jetpack\Status))
#12 /wordpress/core/5.9.1/wp-includes/class-wp-hook.php(307): Jetpack->configure('')
#13 /wordpress/core/5.9.1/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)
#14 /wordpress/core/5.9.1/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
#15 /wordpress/core/5.9.1/wp-settings.php(450): do_action('plugins_loaded')
#16 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1317): require('/wordpress/core...')
#17 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1235): WP_CLI\Runner->load_wordpress()
#18 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()
#19 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(78): WP_CLI\Bootstrap\LaunchRunner->process(Object(WP_CLI\Bootstrap\BootstrapState))
#20 phar:///usr/local/bin/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap()
#21 phar:///usr/local/bin/wp-cli/php/boot-phar.php(11): include('phar:///usr/loc...')
#22 /usr/local/bin/wp-cli(4): include('phar:///usr/loc...')
#23 {main}
  thrown in /srv/htdocs/wp-content/plugins/restrict-user-access/level.php on line 260

Although the plugin version is 10.8-a.1 above, this happens with stable release of Jetpack 10.7 as well: https://www.ads-software.com/plugins/jetpack/

PHP version: 7.4

Yes but, Jetpack isn’t installed my WP instance.

• This reply was modified 2 years, 8 months ago by rocuments.

Same error here:

Stack trace:
#0 /www/xyz.com/wp-content/plugins/restrict-user-access/level.php(246): RUA_Level_Manager->_init_metadata()
#1 /www/xyz.com/wp-content/plugins/restrict-user-access/app.php(596): RUA_Level_Manager->metadata()
#2 /www/xyz.com/wp-includes/class-wp-hook.php(307): RUA_App->process_level_automators('')
#3 /www/xyz.com/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)
#4 /www/xyz.com/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
#5 /www/xyz.com/wp-includes/pluggable.php(48): do_action('set_current_use...')
#6 /www/xyz.com/wp-includes/user.php(3379): wp_set_current_user(1)
#7 /www/xyz.com/wp-includes/pluggable.php(70): _wp_get_current_user()
#8 /www/xyz.com/wp-includes/l10n.php(97): wp_get_current_user()
#9 /www/xyz.com/wp-includes/l10n.php(140): get_user_locale()
#10 /www/xyz.com/wp-includes/l10n.php(885): determine_locale()
#11 /www/xyz.com/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php(3284): load_plugin_textdomain('sitepress', false, 'sitepress-multi...')
#12 /www/xyz.com/wp-includes/class-wp-hook.php(307): SitePress->plugin_localization('')
#13 /www/xyz.com/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array)
#14 /www/xyz.com/wp-includes/plugin.php(474): WP_Hook->do_action(Array)
#15 /www/xyz.com/wp-settings.php(450): do_action('plugins_loaded')
#16 /www/xyz.com/wp-config.php(87): require_once('/www/htdocs/w00...')
#17 /www/xyz.com/wp-load.php(50): require_once('/www/htdocs/w00...')
#18 /www/xyz.com/wp-admin/admin.php(34): require_once('/www/htdocs/w00...')
#19 /www/xyz.com/wp-admin/plugins.php(10): require_once('/www/htdocs/w00...')
#20 {main}
 thrown

• This reply was modified 2 years, 8 months ago by Ronen.
• This reply was modified 2 years, 8 months ago by Ronen.

Hello, I am also reproducing the same issue on 2.2.2 but not on 2.2.1 (same plugins installed).

+--------------------------------------------+--------+-----------+---------+
| name                                       | status | update    | version |
+--------------------------------------------+--------+-----------+---------+
| ayesha_core                                | active | none      | 4.0     |
| bookly-responsive-appointment-booking-tool | active | none      | 20.6    |
| bookly-addon-pro                           | active | none      | 4.6     |
| bookly-addon-staff-cabinet                 | active | none      | 4.1     |
| classic-editor                             | active | none      | 1.6.2   |
| cmb2                                       | active | none      | 2.10.1  |
| contact-form-7                             | active | none      | 5.5.6   |
| jetpack                                    | active | available | 9.9.1   |
| loco-translate                             | active | none      | 2.5.8   |
| revslider                                  | active | none      | 6.5.14  |
| under-construction-page                    | active | none      | 3.92    |
| widget-importer-exporter                   | active | none      | 1.6     |
| wordpress-importer                         | active | none      | 0.7     |
| js_composer                                | active | none      | 6.8.0   |
| wp-crontrol                                | active | none      | 1.12.0  |
| wp-mail-smtp                               | active | available | 2.9.0   |
+--------------------------------------------+--------+-----------+---------+

@throu maybe try installing an older version.
2.2.1 works for me but 2.2.2 doesn’t.

You can download version 2.2.1 from
https://www.ads-software.com/plugins/restrict-user-access/advanced/

Thanks! Already done this morning.

Thank you all for stacktraces and lists of plugins, it will be very helpful to debug the issue.

For now, I have released version 2.2.3 which reverts the line of code I referenced in my previous comment. For transparency, the change was made to make Member Automators more compatible with other plugins, but obviously it had the exact opposite effect, and I apologise for the inconvenience.

TLDR: Version 2.2.3 fixes the fatal error introduced in 2.2.2. Since version 2.2.1 contains a vulnerability, please update as soon as possible.

Lieber Joachim Jensen,

in between: Keep simple and stupid.
We webmasters run lots of websites. Plugins that need complex documentations are a failure, e.g. WTF is “Automation (Beta)”? Who needs this kind of endeavour?

Sorry. No go. The sooner I can replace your plugin, the better.
As of now, and as long I need to study complex documentations.

Keep it simple and stupid.

Thank you very much for the quick fix, Joachim.