Forum Replies Created

Viewing 15 replies - 1 through 15 (of 18 total)
  • Thread Starter aimutch

    (@aimutch)

    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.

    Thread Starter aimutch

    (@aimutch)

    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.

    Thread Starter aimutch

    (@aimutch)

    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

    Thread Starter aimutch

    (@aimutch)

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

    angular.min.js?ver=1.0:101

        POST http://myserver/wp-admin/admin-ajax.php 500 (Internal Server Error)
    Thread Starter aimutch

    (@aimutch)

    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?

    Thread Starter aimutch

    (@aimutch)

    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’m seeing the same problem. I keep changing the “Display Name Publicly As” name and it keeps reverting.

    I ran into the same problem on Dreamhost. I had to set up this:

    Reply-To: [your-name] <[your-email]>

    and set that to a valid e-mail on my domain. Otherwise, DH treats it like spam.

    It must have been a combination of things because I’ve been keeping my plugins current. It did break after I upgraded to 3.5 but I upgraded the plugin at the same time.

    I didn’t vote for “broken” but when a plugin breaks an installation because of a change the author made, it’s broken. I can’t recall the last time I had to manually edit WP or a plugin to make it work.

    Thanks. This might not be the most direct way to do this but for anyone who got stuck like me, here’s the detailed explanation. I had set this up so long ago that I had forgotten how all the parts worked together so the summary help comments above didn’t provide enough detail for me to immediately figure out how to fix this. This should be enough for anyone who is still trying to work this out.

    ==============

    1. Go into the wp-content\plugins directory and rename “theme-my-login” directory to a different name. This effectively disables the plugin.

    2. Go to your regular login page. At this point, with “Theme My Login” disabled, you should see the default WP login form.

    3. Once logged in as admin, from your list of pages, find your custom login page and open it. Change the shortcode showing from [theme-my-login-page] into [theme-my-login]. Save the change.

    4. Go back into wp-content\plugins and rename the “theme-my-login” directory back to its original name.

    5. Go to “Plugins” in the Admin section and re-enable the “Theme My Login” plugin.

    6. Log out of the Admin section and go back to your login page. You should now see your “Theme My Login” based login form.

    I don’t have access to the DB to fix this. Is there any way to undo this without getting into the database?

    Same problem with 3.3.

    Thread Starter aimutch

    (@aimutch)

    I discovered some code in my root index.php file. I’m sure this is connected to it.

    http://pastebin.com/a3BAMHDx

    Thread Starter aimutch

    (@aimutch)

    Thanks! I’ll be reviewing my files today to see if I can find the offending code. I also appreciate the link to Sucuri. I hadn’t seen that site before and sure enough, it was reporting a couple of problems.

Viewing 15 replies - 1 through 15 (of 18 total)