2.2.0 update shutdown wordpress site with critical error

Yes, it works ??

I’m sorry ??

PHP Fatal error: Uncaught TypeError: substr() expects parameter 1 to be string, null given in /var/www/eufort-sokolniki/wordpress/current/wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php:559
Stack trace:
#0 /var/www/eufort-sokolniki/wordpress/current/wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php(559): substr()
#1 /var/www/eufort-sokolniki/wordpress/current/wp-content/plugins/user-access-manager/src/Config/WordpressConfig.php(66): UserAccessManager\Wrapper\Wordpress->isAdmin()
#2 /var/www/eufort-sokolniki/wordpress/current/wp-content/plugins/user-access-manager/src/UserGroup/UserGroupHandler.php(272): UserAccessManager\Config\WordpressConfig->atAdminPanel()
#3 /var/www/eufort-sokolniki/wordpress/current/wp-content/plugins/user-access-manager/src/UserGroup/UserGroupHandler.php(324): UserAccessManager\UserGroup\UserGroupHandler->checkUserGroupAccess()
#4 /var/www/eufort-sokolniki/wordpress/current/wp-content/plugins/user-access-manager/src/Access/AccessHandler.php(210): UserAccessManager\UserGr in /var/www/eufort-sokolniki/wordpress/current/wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php on line 559

you will need to fix a few other issues if you switch your php version to 8.0

2.2.7 fix your latest issue.

@nunosarmento Which one? Made a quick test and also run an inspection of PhpStorm and seems to work fine with PHP 8.0.

@gm_alex I’m very sorry, my bad, you’re absolutely right there are no issues at all.

@gm_alex I havn’t tested the latest version yet, but I want to thank you for updating the plugin. It’s been very helpfull.

@gm_alex
I tested the update today on my development site.
After doing the update, file restriction doesn’t work anymore.

The .htaccess file showed that the UAM code is commented out

# END WordPress
# BEGIN UAM Custom
# <IfModule mod_rewrite.c>
# <FilesMatch '\.(zip|rar|tar|gz|pdf)'>
# RewriteEngine On
# RewriteBase /
# RewriteRule ^index\.php$ - [L]
# RewriteRule ^([^?]*)$ /index.php?uamfiletype=attachment&uamgetfile=$1 [QSA,L]
# RewriteRule ^(.*)\?(((?!uamfiletype).)*)$ /index.php?uamfiletype=attachment&uamgetfile=$1&$2 [QSA,L]
# RewriteRule ^(.*)\?(.*)$ /index.php?uamgetfile=$1&$2 [QSA,L]
# </FilesMatch>
# </IfModule>
# END UAM Custom

But even after removing the #, file restriction still does not work. Protected files can be opened by anyone. Before running the update, it worked.

EDIT: The version that currently works for me is: Version 2.1.12

• This reply was modified 3 years, 9 months ago by coholm.
• This reply was modified 3 years, 9 months ago by coholm.
• This reply was modified 3 years, 9 months ago by coholm.

@coholm It works for me as expected. Please deactivate the file locking and enable it again maybe that will fix the issue.

@gm_alex still doesn’t work.

Maybe it’s worth mentioning:
I have set up a user group called “Luftfahrtkunden” in UAM and WordPress and linked those two:
https://i.postimg.cc/Hx4z0wpf/uam1.png

In the Media section I wordpress I have checked the box for files that should be protected:
https://i.postimg.cc/nztTQRt4/uam2.png

Have you tried it with a custom user group?

@gm_alex Hi Alex, first of all: thankx for your great plugin!
in V2.2.7 there is also an Issue with the Type Hinting in the ShortCodeController.
I’m calling an uam_public Shortcode without Attributes (except content of course) and get the Error:

Fatal error: Uncaught TypeError: Argument 1 passed to UserAccessManager\Controller\Frontend\ShortCodeController::publicShortCode() must be of the type array, string given, called in 
/homepages/.../wp-includes/shortcodes.php on line 343 and defined in /homepages/.../wp-content/plugins/user-access-manager/src/Controller/Frontend/ShortCodeController.php:95 
Stack trace: 
#0 /homepages/.../wp-includes/shortcodes.php(343): UserAccessManager\Controller\Frontend\ShortCodeController->publicShortCode('', 'Bitte geben Sie...', 'uam_public') 
#1 [internal function]: do_shortcode_tag(Array) 
#2 /homepages/.../wp-includes/shortcodes.php(218): preg_replace_callback('/\\[(\\[?)(LOGIN_...', 'do_shortcode_ta...', '<h2>Ihr Zugang ...') 
#3 /homepages/.../wp-content/plugins/js_composer/include/helpers/helpers.php(240): do_shortcode(' in /homepages/.../wp-content/plugins/user-access-manager/src/Controller/Frontend/ShortCodeController.php on line 102

My quick-and-dirty-bring-it-back-to-work solution was to skip the type hinting and remove the “array” from the function declaration in Line 95:

public function publicShortCode($attributes, $content = ''): string

…but I think you might have a better Solution. ??

@ingonieur 2.2.8 should fix your issue.

@gm_alex
Is there any chance you can figure out why file protection isn’t working for me anymore since updating to 2.2

With file protection I mean not only hiding the link, but also restricting file access when the file link is opened directly

I can also give you access if needed.

• This reply was modified 3 years, 9 months ago by coholm.

Also when I go on the setup link, it says:
Deine UAM-Datenbank scheint defekt zu sein. Du solltest versuchen, sie zu reparieren.

After running the repair, the message is still there.
When deleting the backup of the database I get the following error:

Fatal error: Uncaught TypeError: Argument 1 passed to UserAccessManager\Setup\Database\DatabaseHandler::deleteBackup() must be of the type string, null given, called in /home/www/testenv2/wp-content/plugins/user-access-manager/src/Controller/Backend/SetupController.php on line 200 and defined in /home/www/testenv2/wp-content/plugins/user-access-manager/src/Setup/Database/DatabaseHandler.php:454 Stack trace: #0 /home/www/testenv2/wp-content/plugins/user-access-manager/src/Controller/Backend/SetupController.php(200): UserAccessManager\Setup\Database\DatabaseHandler->deleteBackup(NULL) #1 /home/www/testenv2/wp-content/plugins/user-access-manager/src/Controller/Controller.php(173): UserAccessManager\Controller\Backend\SetupController->deleteDatabaseBackupAction() #2 /home/www/testenv2/wp-content/plugins/user-access-manager/src/Controller/Controller.php(182): UserAccessManager\Controller\Controller->processAction() #3 /home/www/testenv2/wp-includes/class-wp-hook.php(287): UserAccessManager\Controller\Controller->render('') #4 in /home/www/testenv2/wp-content/plugins/user-access-manager/src/Setup/Database/DatabaseHandler.php on line 454

@coholm I’m not able to reproduce your issue. Did you update other plugins? Currently I have no idea what could causes the issue.