Locked Configuration Screen

Hey there,

1. Do you have enabled “Set local password on first successful login” and/or “Fallback to local password” on the configuration page https://docs.active-directory-wp.com/Configuration/Password.html?
2. What does your Windows Server event log shows when your users are not able to log in with their new password?
3. Do you have NADI installed in a WordPress Multisite environment?
4. Can you check with your browser’s Web Developer Console if there any JavaScript errors on the configuration page?

Sorry for the delay on my response. I’m going to spin up a clean install of WP 6.5.5 and the latest version of the plugin and see if I can replicate the problem there first. That will simplify the troubleshooting.

I think I found what needs to be changed in the settings in the test WordPress install. But when I try to access the settings on my production WordPress blog, I’m unable to access any of the settings for the plugin. They are “grayed out”. I tried the following:
– Deactivated, deleted and reinstalled the plugin.
– Log into the WordPress installation from a browser that had never been used to access the site.

Neither of those worked. Is there a database setting(s) I can alter via PHPMyAdmin that would enable the settings?

In JS console, I’m getting this error on only on the Plug-in configuration page:

angular.min.js?ver=1.0:101

    POST https://myserver/wp-admin/admin-ajax.php 500 (Internal Server Error)

I enabled debugging. I had to disable the “BackWPup” plugin for the configuration page to become accessible. This was the error message I was seeing that referenced the NADI plugin:

[03-Jul-2024 20:06:16 UTC] PHP Fatal error: Uncaught TypeError: Dreitier\Nadi\Vendor\Monolog\Logger::pushHandler(): Argument #1 ($handler) must be of type Dreitier\Nadi\Vendor\Monolog\Handler\HandlerInterface, Monolog\Handler\StreamHandler given, called in C:\inetpub\wwwroot\library\wp-content\plugins\backwpup\src\Infrastructure\Restore\commons.php on line 90 and defined in C:\inetpub\wwwroot\library\wp-content\plugins\next-active-directory-integration\vendor-repackaged\monolog\monolog\src\Monolog\Logger.php:231
Stack trace: 0 C:\inetpub\wwwroot\library\wp-content\plugins\backwpup\src\Infrastructure\Restore\commons.php(90): Dreitier\Nadi\Vendor\Monolog\Logger->pushHandler() 1 C:\inetpub\wwwroot\library\wp-content\plugins\backwpup\vendor\pimple\pimple\src\Pimple\Container.php(122): Inpsyde\BackWPup\Infrastructure\Restore{closure}() 2 C:\inetpub\wwwroot\library\wp-content\plugins\backwpup\src\Infrastructure\Restore\commons.php(111): Pimple\Container->offsetGet() 3 C:\inetpub\wwwroot\library\wp-content\plugins\backwpup\vendor\pimple\pimple\src\Pimple\Container.php(122): Inpsyde\BackWPup\Infrastructure\Restore{closure}() 4 C:\inetpub\wwwroot\library\wp-content\plugins\backwpup\src\Infrastructure\Restore\commons.php(180): Pimple\Container->offsetGet() 5 C:\inetpub\wwwroot\library\wp-content\plugins\backwpup\vendor\pimple\pimple\src\Pimple\Container.php(122): Inpsyde\BackWPup\Infrastructure\Restore{closure}() 6 C:\inetpub\wwwroot\library\wp-content\plugins\backwpup\src\Infrastructure\Restore\commons.php(268): Pimple\Container->offsetGet() 7 C:\inetpub\wwwroot\library\wp-content\plugins\backwpup\vendor\pimple\pimple\src\Pimple\Container.php(122): Inpsyde\BackWPup\Infrastructure\Restore{closure}() 8 C:\inetpub\wwwroot\library\wp-content\plugins\backwpup\src\Infrastructure\Restore\commons.php(311): Pimple\Container->offsetGet() 9 C:\inetpub\wwwroot\library\wp-content\plugins\backwpup\src\Infrastructure\Restore\Restore.php(114): Inpsyde\BackWPup\Infrastructure\Restore\restore_container() 10 C:\inetpub\wwwroot\library\wp-includes\class-wp-hook.php(324): Inpsyde\BackWPup\Infrastructure\Restore\Restore->ajax_handler() 11 C:\inetpub\wwwroot\library\wp-includes\class-wp-hook.php(348): WP_Hook->apply_filters() 12 C:\inetpub\wwwroot\library\wp-includes\plugin.php(517): WP_Hook->do_action() 13 C:\inetpub\wwwroot\library\wp-admin\admin-ajax.php(45): do_action() 14 {main}

thrown in C:\inetpub\wwwroot\library\wp-content\plugins\next-active-directory-integration\vendor-repackaged\monolog\monolog\src\Monolog\Logger.php on line 231

I can confirm on my test installation that once I activated the “BackWPup” plugin, the configuration screen for NADI is grayed out and “locked” so that those settings can’t be accessed.

We have just tested BackWPUp 4.1.2 with the latest available NADI version and it works on our side without any problems. Two remarks here:

• BackWPUp 4.1.2 is wrongly packaged. There is the file vendor\monolog\src\Monolog\Handler\ElasticsearchHandler.php and vendor\monolog\src\Monolog\Handler\ElasticSearchHandler.php (note the uppercase ‘S’) in the ZIP file. We had to manually delete the upper-case file from the ZIP files. Otherwise we would not be able to extract the archive manually.
• BackWPUp does not repackage Monolog in its own namespace. We are doing this since NADI version 3.0. To keep our plug-in compatible, there is a stub.
  You can remove our Monolog stub by commenting out the line 40 (require_once DIR . '/monolog_logger.php';) in next-active-directory-integration/src/compat-v2/stubs.php. For some reason in your environment the loading of BackWPUp’s dependency occurs to a later point in time.

Thanks for identifying the source of the conflict. Feel free to close the ticket as the source of the problem is the other plugin. I’ve reported it to them and hopefully, they’ll get that fixed soon.