Conversation
supportOn WP version 6.8.3 / PHP 8.3 my site experienced problems with this plugin. type E_ERROR caused by line nr. 76 of the file wp-content/plugins/user-access-manager/src/Command/GroupCommand.php. Error: Uncaught Error: Cannot call constructor in wp-content/plugins/user-access-manager/src/Command/GroupCommand.php:76 Stack trace: #0 wp-content/plugins/user-access-manager/init.php(258): UserAccessManager\Command\GroupCommand->__construct() #1 wp-content/plugins/user-access-manager/user-access-manager.php(77): initUserAccessManger() #2 wp-includes/class-wp-hook.php(341): initUam() #3 wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() #4 wp-includes/plugin.php(522): WP_Hook->do_action() #5 wp-settings.php(742): do_action() #6 wp-config.php(115): require_once(‘/home/xxxxxxxxxxx’) Now I have WP 6.9, still the same error. It looks like the plugin does function but this is a bit weird. Are you @gm_alex still developing this (8 months ago latest update) or should I look for an alternative? Best regards, AMMO
Hi, could you have a look if the latest release fixes the issue? Greetings, Alex
Hi Alex, The latest release is 2.3.0, this version generates not the mentioned errors but it does crash my entire site with a critical error. I uploaded the site error log to Gemini and this the conclusion: 1. The Critical Issue: Conflict Between Plugins The most recent and serious errors are caused by a conflict between two plugins: User Access Manager and Asgaros Forum . The Error Message: PHP Fatal error: Uncaught TypeError: UserAccessManager\Object\ObjectHandler::registeredTaxonomy(): Argument #2 ($objectType) must be of type array|string, null given . What is happening: The plugin Asgaros Forum attempts to register a taxonomy (a grouping, like categories). The User Access Manager plugin monitors this process but receives an empty value ( null ) where it expects a string or list. Due to stricter rules in newer PHP versions (likely running PHP 8.0 or higher), this leads directly to a fatal crash. Consequence: Your backend (wp-admin) is likely inaccessible or barely responsive. Solution: You must disable one of these two plugins to regain access. Since you probably cannot enter the admin panel, this must be done via FTP or the File Manager of your hosting (DirectAdmin/cPanel). Summary Your site is crashing due to the User Access Manager plugin in combination with the forum. Disable User Access Manager manually via the files on the server to get the site working again. How to fix this? Best regards, AMMO
Hi, new release is on the way and will be available within the next minutes. Please give it a try. Greetings, Alex
Hi Alex, I upgraded to version 2.3.2 and still get an error (PHP 8.5, WP 6.0, WPML, many other possible culprits). A fix for me was modifying line 156 in /src/Controller/Frontend/TermController.php and add “string” as a possible type for $term and the return value: private function processTerm(bool|WP_Term| stdClass |string $ term , bool &$ isEmpty = null): WP_Term| stdClass |bool|string (sorry for hijacking the thread)
@ammo69 @helmuthb New release is on the way, please check it. Thanks.
Hi still critical error on my website with 2.3.3 release This reply was modified 6 months, 4 weeks ago by rubin-sev .
Bonjour j’ai toujours une erreur critique avec la version 2.3.3
@rubin-sev Could you provide me the error you are receiving?
Fatal error : Uncaught TypeError: UserAccessManager\Wrapper\Wordpress::switchToBlog(): Argument #1 ($blogId) must be of type int, string given, called in /wp-content/plugins/user-access-manager/src/Setup/Database/DatabaseHandler.php on line 210 and defined in /wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php:201 Stack trace: #0 wp-content/plugins/user-access-manager/src/Setup/Database/DatabaseHandler.php(210): UserAccessManager\Wrapper\Wordpress->switchToBlog() #1 /wp-content/plugins/user-access-manager/src/Setup/Database/DatabaseHandler.php(230): UserAccessManager\Setup\Database\DatabaseHandler->getActivePluginSites() #2 /wp-content/plugins/user-access-manager/src/Controller/Backend/BackendController.php(44): UserAccessManager\Setup\Database\DatabaseHandler->isDatabaseUpdateNecessary() #3 /wp-includes/class-wp-hook.php(341): UserAccessManager\Controller\Backend\BackendController->showAdminNotice() #4/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() #5 /wp-includes/plugin.php(522): WP_Hook->do_action() #6 /wp-admin/admin-header.php(313): do_action() #7 /wp-admin/index.php(137): require_once(‘…’) #8 {main} thrown in wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php on line 201 There has been a critical error on this website.
hi, It looks like the plugin is functioning as supposed to. Using version 2.3.3 @rubin-sev still has problems, but on my site it looks good now. Thanks so far for the quick respons! AMMO
hello, Since new version i was able to update a account on wordpress but the user creation is blocked. Any new update is on going ?
@laurent06 Could you provide me an error?
Fatal error: Uncaught TypeError: UserAccessManager\UserGroup\AbstractUserGroup::isObjectMember(): Argument #2 ($objectId) must be of type string|int, null given, called in /homepages/28/d847146969/htdocs/clickandbuilds//wp-content htdocs/clickandbuilds//wp-admin/user-new.php(664): do_action() #9 {main} thrown in /homepages/28/d847146969/htdocs/clickandbuilds//wp-contentr-access-manager/src/UserGroup/AbstractUserGroup.php:353 Stack trace: #0 /homepages/28/d847146969/htdocs/clickandbuilds//wp-content/plugins/user-access-manager/src/View/GroupSelectionForm.php(50): UserAccessManager\UserGroup\AbstractUserGroup->isObjectMember() #1 /homepages/28/d847146969/htdocs/clickandbuilds//wp-content/plugins/user-access-manager/src/View/UserProfileEditForm.php(35): include(‘/homepages/28/d…’) #2 /homepages/28/d847146969/htdocs/clickandbuilds//wp-content/plugins/user-access-manager/src/Wrapper/Php.php(80): include(‘/homepages/28/d…’) #3 /homepages/28/d847146969/htdocs/clickandbuilds//wp-content/plugins/user-access-manager/src/Controller/BaseControllerTrait.php(66): UserAccessManager\Wrapper\Php->includeFile() #4 /homepages/28/d847146969/htdocs/clickandbuilds//wp-content/plugins/user-access-manager/src/Controller/Backend/UserObjectController.php(39): UserAccessManager\Controller\Controller->getIncludeContents() #5 /homepages/28/d847146969/htdocs/clickandbuilds//wp-includes/class-wp-hook.php(341): UserAccessManager\Controller\Backend\UserObjectController->showUserProfile() #6 /homepages/28/d847146969/htdocs/clickandbuilds//wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() #7 /homepages/28/d847146969/htdocs/clickandbuilds//wp-includes/plugin.php(522): WP_Hook->do_action() #8 /homepages/28/d847146969/htdocs/clickandbuilds//wp-admin/user-new.php(664): do_action() #9 {main} thrown in /homepages/28/d847146969/htdocs/clickandbuilds//wp-content/plugins/user-access-manager/src/UserGroup/AbstractUserGroup.php on line 353 This reply was modified 6 months, 4 weeks ago by laurent06 .
@gm_alex did you find something ? the issue is only when i’m trying to create a new user account This reply was modified 6 months, 4 weeks ago by laurent06 .
@laurent06 Can you try 2.3.4 please?
Hello i’m on it but issue still exist
this is the stack with version 2.3.4: Fatal error: Uncaught TypeError: UserAccessManager\ObjectMembership\UserMembershipHandler::isMember(): Argument #3 ($objectId) must be of type string|int, null given, called in /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/UserGroup/AbstractUserGroup.php on line 360 and defined in /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/ObjectMembership/UserMembershipHandler.php:35 Stack trace: 0 /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/UserGroup/AbstractUserGroup.php(360): UserAccessManager\ObjectMembership\UserMembershipHandler->isMember() 1 /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/View/GroupSelectionForm.php(50): UserAccessManager\UserGroup\AbstractUserGroup->isObjectMember() 2 /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/View/UserProfileEditForm.php(35): include(‘/homepages/28/d…’) 3 /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/Wrapper/Php.php(80): include(‘/homepages/28/d…’) 4 /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/Controller/BaseControllerTrait.php(66): UserAccessManager\Wrapper\Php->includeFile() 5 /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/Controller/Backend/UserObjectController.php(39): UserAccessManager\Controller\Controller->getIncludeContents() 6 /homepages/28/d847146969/htdocs/clickandbuilds/wp-includes/class-wp-hook.php(341): UserAccessManager\Controller\Backend\UserObjectController->showUserProfile() 7 /homepages/28/d847146969/htdocs/clickandbuilds/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() 8 /homepages/28/d847146969/htdocs/clickandbuilds/wp-includes/plugin.php(522): WP_Hook->do_action() 9 /homepages/28/d847146969/htdocs/clickandbuilds/wp-admin/user-new.php(664): do_action() 10 {main} thrown in /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/ObjectMembership/UserMembershipHandler.php on line 35
. This reply was modified 6 months, 4 weeks ago by laurent06 .
Hello! With PHP 8.4/UAM 2.3.4, I get : [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Wrapper\Wordpress::getAllowedMimeTypes(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php on line 345 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Wrapper\Wordpress::getUploadDir(): Implicitly marking parameter $time as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php on line 353 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Wrapper\Wordpress::getHomeUrl(): Implicitly marking parameter $scheme as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php on line 361 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Wrapper\Wordpress::getSiteUrl(): Implicitly marking parameter $scheme as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php on line 369 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Database\Database::getColumn(): Implicitly marking parameter $query as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Database/Database.php on line 97 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Database\Database::getRow(): Implicitly marking parameter $query as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Database/Database.php on line 105 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Database\Database::getVariable(): Implicitly marking parameter $query as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Database/Database.php on line 113 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Database\Database::getBlogPrefix(): Implicitly marking parameter $blogId as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-cont...
Hi, could you have a look if the latest release fixes the issue? Greetings, Alex
Hi Alex, The latest release is 2.3.0, this version generates not the mentioned errors but it does crash my entire site with a critical error. I uploaded the site error log to Gemini and this the conclusion: 1. The Critical Issue: Conflict Between Plugins The most recent and serious errors are caused by a conflict between two plugins: User Access Manager and Asgaros Forum . The Error Message: PHP Fatal error: Uncaught TypeError: UserAccessManager\Object\ObjectHandler::registeredTaxonomy(): Argument #2 ($objectType) must be of type array|string, null given . What is happening: The plugin Asgaros Forum attempts to register a taxonomy (a grouping, like categories). The User Access Manager plugin monitors this process but receives an empty value ( null ) where it expects a string or list. Due to stricter rules in newer PHP versions (likely running PHP 8.0 or higher), this leads directly to a fatal crash. Consequence: Your backend (wp-admin) is likely inaccessible or barely responsive. Solution: You must disable one of these two plugins to regain access. Since you probably cannot enter the admin panel, this must be done via FTP or the File Manager of your hosting (DirectAdmin/cPanel). Summary Your site is crashing due to the User Access Manager plugin in combination with the forum. Disable User Access Manager manually via the files on the server to get the site working again. How to fix this? Best regards, AMMO
Hi, new release is on the way and will be available within the next minutes. Please give it a try. Greetings, Alex
Hi Alex, I upgraded to version 2.3.2 and still get an error (PHP 8.5, WP 6.0, WPML, many other possible culprits). A fix for me was modifying line 156 in /src/Controller/Frontend/TermController.php and add “string” as a possible type for $term and the return value: private function processTerm(bool|WP_Term| stdClass |string $ term , bool &$ isEmpty = null): WP_Term| stdClass |bool|string (sorry for hijacking the thread)
@ammo69 @helmuthb New release is on the way, please check it. Thanks.
Hi still critical error on my website with 2.3.3 release This reply was modified 6 months, 4 weeks ago by rubin-sev .
Bonjour j’ai toujours une erreur critique avec la version 2.3.3
@rubin-sev Could you provide me the error you are receiving?
Fatal error : Uncaught TypeError: UserAccessManager\Wrapper\Wordpress::switchToBlog(): Argument #1 ($blogId) must be of type int, string given, called in /wp-content/plugins/user-access-manager/src/Setup/Database/DatabaseHandler.php on line 210 and defined in /wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php:201 Stack trace: #0 wp-content/plugins/user-access-manager/src/Setup/Database/DatabaseHandler.php(210): UserAccessManager\Wrapper\Wordpress->switchToBlog() #1 /wp-content/plugins/user-access-manager/src/Setup/Database/DatabaseHandler.php(230): UserAccessManager\Setup\Database\DatabaseHandler->getActivePluginSites() #2 /wp-content/plugins/user-access-manager/src/Controller/Backend/BackendController.php(44): UserAccessManager\Setup\Database\DatabaseHandler->isDatabaseUpdateNecessary() #3 /wp-includes/class-wp-hook.php(341): UserAccessManager\Controller\Backend\BackendController->showAdminNotice() #4/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() #5 /wp-includes/plugin.php(522): WP_Hook->do_action() #6 /wp-admin/admin-header.php(313): do_action() #7 /wp-admin/index.php(137): require_once(‘…’) #8 {main} thrown in wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php on line 201 There has been a critical error on this website.
hi, It looks like the plugin is functioning as supposed to. Using version 2.3.3 @rubin-sev still has problems, but on my site it looks good now. Thanks so far for the quick respons! AMMO
hello, Since new version i was able to update a account on wordpress but the user creation is blocked. Any new update is on going ?
@laurent06 Could you provide me an error?
Fatal error: Uncaught TypeError: UserAccessManager\UserGroup\AbstractUserGroup::isObjectMember(): Argument #2 ($objectId) must be of type string|int, null given, called in /homepages/28/d847146969/htdocs/clickandbuilds//wp-content htdocs/clickandbuilds//wp-admin/user-new.php(664): do_action() #9 {main} thrown in /homepages/28/d847146969/htdocs/clickandbuilds//wp-contentr-access-manager/src/UserGroup/AbstractUserGroup.php:353 Stack trace: #0 /homepages/28/d847146969/htdocs/clickandbuilds//wp-content/plugins/user-access-manager/src/View/GroupSelectionForm.php(50): UserAccessManager\UserGroup\AbstractUserGroup->isObjectMember() #1 /homepages/28/d847146969/htdocs/clickandbuilds//wp-content/plugins/user-access-manager/src/View/UserProfileEditForm.php(35): include(‘/homepages/28/d…’) #2 /homepages/28/d847146969/htdocs/clickandbuilds//wp-content/plugins/user-access-manager/src/Wrapper/Php.php(80): include(‘/homepages/28/d…’) #3 /homepages/28/d847146969/htdocs/clickandbuilds//wp-content/plugins/user-access-manager/src/Controller/BaseControllerTrait.php(66): UserAccessManager\Wrapper\Php->includeFile() #4 /homepages/28/d847146969/htdocs/clickandbuilds//wp-content/plugins/user-access-manager/src/Controller/Backend/UserObjectController.php(39): UserAccessManager\Controller\Controller->getIncludeContents() #5 /homepages/28/d847146969/htdocs/clickandbuilds//wp-includes/class-wp-hook.php(341): UserAccessManager\Controller\Backend\UserObjectController->showUserProfile() #6 /homepages/28/d847146969/htdocs/clickandbuilds//wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() #7 /homepages/28/d847146969/htdocs/clickandbuilds//wp-includes/plugin.php(522): WP_Hook->do_action() #8 /homepages/28/d847146969/htdocs/clickandbuilds//wp-admin/user-new.php(664): do_action() #9 {main} thrown in /homepages/28/d847146969/htdocs/clickandbuilds//wp-content/plugins/user-access-manager/src/UserGroup/AbstractUserGroup.php on line 353 This reply was modified 6 months, 4 weeks ago by laurent06 .
@gm_alex did you find something ? the issue is only when i’m trying to create a new user account This reply was modified 6 months, 4 weeks ago by laurent06 .
@laurent06 Can you try 2.3.4 please?
Hello i’m on it but issue still exist
this is the stack with version 2.3.4: Fatal error: Uncaught TypeError: UserAccessManager\ObjectMembership\UserMembershipHandler::isMember(): Argument #3 ($objectId) must be of type string|int, null given, called in /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/UserGroup/AbstractUserGroup.php on line 360 and defined in /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/ObjectMembership/UserMembershipHandler.php:35 Stack trace: 0 /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/UserGroup/AbstractUserGroup.php(360): UserAccessManager\ObjectMembership\UserMembershipHandler->isMember() 1 /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/View/GroupSelectionForm.php(50): UserAccessManager\UserGroup\AbstractUserGroup->isObjectMember() 2 /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/View/UserProfileEditForm.php(35): include(‘/homepages/28/d…’) 3 /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/Wrapper/Php.php(80): include(‘/homepages/28/d…’) 4 /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/Controller/BaseControllerTrait.php(66): UserAccessManager\Wrapper\Php->includeFile() 5 /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/Controller/Backend/UserObjectController.php(39): UserAccessManager\Controller\Controller->getIncludeContents() 6 /homepages/28/d847146969/htdocs/clickandbuilds/wp-includes/class-wp-hook.php(341): UserAccessManager\Controller\Backend\UserObjectController->showUserProfile() 7 /homepages/28/d847146969/htdocs/clickandbuilds/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() 8 /homepages/28/d847146969/htdocs/clickandbuilds/wp-includes/plugin.php(522): WP_Hook->do_action() 9 /homepages/28/d847146969/htdocs/clickandbuilds/wp-admin/user-new.php(664): do_action() 10 {main} thrown in /homepages/28/d847146969/htdocs/clickandbuilds/wp-content/plugins/user-access-manager/src/ObjectMembership/UserMembershipHandler.php on line 35
. This reply was modified 6 months, 4 weeks ago by laurent06 .
Hello! With PHP 8.4/UAM 2.3.4, I get : [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Wrapper\Wordpress::getAllowedMimeTypes(): Implicitly marking parameter $user as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php on line 345 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Wrapper\Wordpress::getUploadDir(): Implicitly marking parameter $time as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php on line 353 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Wrapper\Wordpress::getHomeUrl(): Implicitly marking parameter $scheme as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php on line 361 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Wrapper\Wordpress::getSiteUrl(): Implicitly marking parameter $scheme as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Wrapper/Wordpress.php on line 369 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Database\Database::getColumn(): Implicitly marking parameter $query as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Database/Database.php on line 97 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Database\Database::getRow(): Implicitly marking parameter $query as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Database/Database.php on line 105 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Database\Database::getVariable(): Implicitly marking parameter $query as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Database/Database.php on line 113 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Database\Database::getBlogPrefix(): Implicitly marking parameter $blogId as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Database/Database.php on line 121 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Database\Database::getResults(): Implicitly marking parameter $query as nullable is deprecated, the explicit nullable type must be used instead in /home/[...]/public_html/wp-content/plugins/user-access-manager/src/Database/Database.php on line 145 [09-Dec-2025 23:15:35 UTC] PHP Deprecated: UserAccessManager\Object\ObjectMapHandler::processTreeMapElements(): Implicitly marking parameter $subMap as nullable is dep...
I should have added that all images and files protected with UAM are unavailable and I get a critical error when I try to access them. Fatal error : Uncaught TypeError: UserAccessManager\Wrapper\Php::iniGet(): Return value must be of type string|int, false returned in /home/bhuquebe/public_html/wp-content/plugins/user-access-manager/src/Wrapper/Php.php:52 Stack trace: #0 /home/bhuquebe/public_html/wp-content/plugins/user-access-manager/src/File/FileHandler.php(84): UserAccessManager\Wrapper\Php->iniGet() #1 /home/bhuquebe/public_html/wp-content/plugins/user-access-manager/src/File/FileHandler.php(109): UserAccessManager\File\FileHandler->deliverFileViaFopen() #2 /home/bhuquebe/public_html/wp-content/plugins/user-access-manager/src/File/FileHandler.php(272): UserAccessManager\File\FileHandler->deliverFile() #3 /home/bhuquebe/public_html/wp-content/plugins/user-access-manager/src/Controller/Frontend/RedirectController.php(141): UserAccessManager\File\FileHandler->getFile() #4 /home/bhuquebe/public_html/wp-content/plugins/user-access-manager/src/Controller/Frontend/RedirectController.php(248): UserAccessManager\Controller\Frontend\RedirectController->getFile() #5 /home/bhuquebe/public_html/wp-includes/class-wp-hook.php(341): UserAccessManager\Controller\Frontend\RedirectController->redirect() #6 /home/bhuquebe/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters() #7 /home/bhuquebe/public_html/wp-includes/class-wp.php(563): apply_filters() #8 /home/bhuquebe/public_html/wp-includes/class-wp.php(829): WP->send_headers() #9 /home/bhuquebe/public_html/wp-includes/functions.php(1343): WP->main() #10 /home/bhuquebe/public_html/wp-blog-header.php(16): wp() #11 /home/bhuquebe/public_html/index.php(17): require(‘/home/bhuquebe/…’) #12 {main} thrown in /home/bhuquebe/public_html/wp-content/plugins/user-access-manager/src/Wrapper/Php.php on line 52 This reply was modified 6 months, 4 weeks ago by christianmartel .
Sorry for the inconvenience, hopefully I found all with 2.3.5. Feedback if it works would be nice.
Still the same sadly – php 8.3 wordpress 6.9 F atal error : Uncaught TypeError: UserAccessManager\Database\Database::getBlogPrefix(): Argument #1 ($blogId) must be of type ?int, string given, called in wp-content/plugins/user-access-manager/src/Setup/Database/DatabaseHandler.php on line 231 and defined in /wp-content/plugins/user-access-manager/src/Database/Database.php:121 Stack trace: #0 wp-content/plugins/user-access-manager/src/Setup/Database/DatabaseHandler.php(231): UserAccessManager\Database\Database->getBlogPrefix() #1 /wp-content/plugins/user-access-manager/src/Controller/Backend/BackendController.php(44): UserAccessManager\Setup\Database\DatabaseHandler->isDatabaseUpdateNecessary() #2 /wp-includes/class-wp-hook.php(341): UserAccessManager\Controller\Backend\BackendController->showAdminNotice() #3 /wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() #4 /wp-includes/plugin.php(522): WP_Hook->do_action() #5 /wp-admin/admin-header.php(313): do_action() #6 /wp-admin/index.php(137): require_once(‘…’) #7 {main} thrown in /wp-content/plugins/user-access-manager/src/Database/Database.php on line 121 This reply was modified 6 months, 4 weeks ago by rubin-sev .
Hello it’s works with 2.3.5 thanks for your help
@laurent06 Good to know, thanks for the feedback.
@gm_alex it works with 2.3.7! Thank you very much!!!
Hi Alex, I just wanted to share some good news. The fatal error messages regarding User Access Manager and the Forum have completely disappeared. The site no longer crashes, so the update to version 3.3.7 is a success. Nothing in the error log that concerns your plugin. Thank you very much for your efforts and the quick fix! Best regards, Arnout
@christianmartel Glad to hear. Thanks for the feedback.
Fatal Error in v2.3.7: Cannot call constructor (PHP 8.3) Hi, Thank you for the quick update to fix the previous conflict. However, after updating to version 2.3.7, I am immediately encountering a new Fatal Error that crashes the site. The Error: Uncaught Error: Cannot call constructor in .../wp-content/plugins/user-access-manager/src/Command/GroupCommand.php:29 Stack Trace: #0 .../user-access-manager/init.php(261): UserAccessManager\Command\GroupCommand->__construct() Environment: WordPress 6.7 PHP 8.3.25 User Access Manager 2.3.7 It seems like GroupCommand is trying to call a parent constructor that is not accessible or does not exist. Could you please look into this? Best regards, AMMO
Hi Alex, Could you please take a look at the problem I posted yesterday. The fatal error is still occurring. Thanks, AMMO
Hi @ammo69 , could you try version 2.3.8? I improved the logic, but to be honest I wasn’t able to reproduce the issue. Greetings, Alex
The error message I am seeing now indicates (according to Gemini) that there is a coding error in the plugin’s GroupCommand.php file. The code attempts to call a “constructor” (a startup function) that either does not exist or cannot be called. This is a specific error that frequently occurs in newer PHP versions (my server is running PHP 8.3). I installed 2.3.8. So far no problems. I have to wait till tomorrow to find out. I’ll let you know. Thanks, AMMO
@ammo69 I don’t get it, to be honest. Is everything now fine with 2.3.8, or are you still getting errors?
@gm_alex I have checked the latest error logs for my domain. There have been no crashes or fatal errors since Friday’s update. My site is stable and so is the plugin. The issues are resolved for now. Thanks again.
@ammo69 @helmuthb @rubin-sev @laurent06 Have these issues been resolved? I want to make sure before updating my own site. EDIT: Ah, I see now that most of you have stated the issue has been resolved, my apologies this was a long thread. Best, This reply was modified 5 months, 2 weeks ago by annaam . Reason: I was confused, and am now not
@annaam As far as I can tell, it seems to be working fine again now.