Hi,
same here, my debug log said:
PHP Fatal error: Class ‘WPCAObjectManager’ not found ../wp-content/plugins/restrict-user-access/level.php on line 228
And breaks admin access for user in my multisite install.
Please, help.
Best regards,
Thank you for reporting this. Would it be possible to get more details from the stacktrace? I have an idea of what can be the cause, but unfortunately I cannot reproduce the error.
Hi,
thanks for the quick reply. What do you exactly need? I just copied my debug log above.
Best regards,
Ah! BTW: i got the error after the last plugin update.
Usually the log file should contain a stack trace so that it’s possible to see exactly where the error is triggered, in this case when the function that uses WPCAObjectManager is called.
To everyone in this thread: Do you run a WP multisite/network, and if yes, is the plugin activated on network level?
My case is a single install.
I don’t have a stacktrace but this is what the server log file is reporting (same at the opening thread item):
[22-Sep-2016 16:25:24 UTC] PHP Fatal error: Class ‘WPCAObjectManager’ not found in ../wp-content/plugins/restrict-user-access/level.php on line 228
Hi,
I don’t know what do you mean, the only log I can get is the one I wrote above.
WP multisite install and plugin and plugin activated on netwrok level: yes
Regards,
Hey Joachim,
Thank you for looking into this so quickly. In the meantime, do you see any issue with reverting back to v0.12.1?
The problem is that something (maybe another plugin) prematurely is triggering the call to the function that uses WPCAObjectManager (ie. before it exists). That is what the error message is indicating. However, without a stacktrace, it is hard for me to debug exactly what is going on.
Does the error only show up when the user is trying to log in? Or when he tries to access restricted content? Is there something particular about the user, eg. does he belong to 1 or more Levels?
@srumery
There is no issue or security concerns by reverting back to 0.12.1
Downgrading would need to be done by cloning the git repo (including submodules).
Instead, open up restrict-user-access.php and change line 42 to:
require($rua_plugin_path.'/lib/wp-content-aware-engine/core.php');
Cool. I updated that line and will watch the error report closely. I’ll report back with results.
I confirmed that your update fixed the problem. Multiple users that reported a problem are no longer having any issues. Well done, Joachim! 🙂
Thank you for supporting your plugin.
