• Resolved vgstudios

    (@vgstudios)


    The error when trying to reconnect them given is:
    https://site-name.here/ – Undefined error!

    Downgrading back to 4.5.1.3 gives a different error:
    Public key already set. Please deactivate & reactivate the MainWP Child plugin and try again.

    Is this behavior to be expected?

    —- —- —- —-
    Edit1: After restoring a backup of database and files of the Dashboard I can access them on 4.5.1.3 again, but I am afraid upgrading to 4.5.2 will break that again.

    —- —- —- —-
    Edit2: Yes that’s exactly what happens.

    • This topic was modified 7 months, 3 weeks ago by vgstudios.
    • This topic was modified 7 months, 3 weeks ago by vgstudios.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Bojan Katusic

    (@bojankatusic)

    Hi @vgstudios

    “After updating Dashboard to 4.5.2 sites on Child <=4.1.x got disconnected”
    Can you please update the MainWP Child plugin on those sites to the latest version v4.5.2, and see if that helps?

    If you get “Public key already set. Please deactivate & reactivate the MainWP Child plugin and try again.” error message again after updating the Child plugin, try deactivating and re-activating it and then try reconnecting again.

    Thread Starter vgstudios

    (@vgstudios)

    Can you please update the MainWP Child plugin on those sites to the latest version v4.5.2, and see if that helps?

    I wouldn’t be surprised if it would work after updating the MainWP Child Plugin to the latest version.
    However the WordPress core versions on those sites are older (4.x) than the what the latest MainWP child plugin demands (5.4 or higher) and I am not allowed to update those sites.

    Maybe updating the system requirements ( https://kb.mainwp.com/docs/system-requirements/ ) where it still says WordPress 3.6+ could be helpful for some.

    Thank you for your reply.

    Plugin Support Bojan Katusic

    (@bojankatusic)

    “Maybe updating the system requirements ( https://kb.mainwp.com/docs/system-requirements/ ) where it still says WordPress 3.6+ could be helpful for some.”
    Thanks for pointing that out to us. We’ve updated the article.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘After updating Dashboard to 4.5.2 sites on Child <=4.1.x got disconnected’ is closed to new replies.