100% agree! This is the worst and I’ll be searching for an alternative straight away!
Hello @mikeyinglis ,
I’m very sorry to hear about the inconvenience you’re experiencing. It’s certainly not right for an onboarding process to block the use of the menu or Complianz itself, so something is definitely wrong.
We can’t reproduce the issue on our end, unfortunately, so we would appreciate if you could provide an example. This will help us understand the problem better and work on a solution.
Thank you for your patience and cooperation.
Hello @mikeyinglis ,
We got some updates for the current issue, and want to assure you that we are actively working on resolving it in the next patch. In the meantime, we have identified the cause of the problem and provide a temporary workaround to restore your WordPress backend using a mu-plugin or script inside functions.php. Please follow these steps:
- If you don’t already have a mu-plugins folder in wp-content, open your FTP client and create a new folder named mu-plugins in the wp-content directory. The resulting path should look like: */wp-content/mu-plugins/
- Upload a .php file to wp-content/mu-plugins/ via FTP with the following code:
<?php
if ($timestamp = get_option('cmplz_wsc_onboarding_start')) {
if (is_numeric($timestamp) && $timestamp < time()) {
delete_option('cmplz_wsc_onboarding_start');
}
}
- Logout from your WordPress website and log in again. This will initialize the script via the admin_init hook, restoring your backend.
- Remove the mu-plugin or the script after the backend has been restored.
I hope this helps, please let us know.
Best regards,
Antonio
Thank you we will give this a go.
This is happening to me as well, Complianz keeps popping up wanting me to use it’s website scanner. I hit “No thanks” three times in a row and then “Close” then every time I try to access anything else on the admin menu it starts again.
