Facebook
TwitterI will explain the title a bit better now.
One of my clients has a Wordpress site that chokes the Wordpress toolkit.
It gives:
I found the culprit and I can resurrect it by changing the wp-config.php.
There I just comment this line:
Now, the WordPress site is able to get configured by the Wordpress toolkit.
I can do a "Scan" now.
Alas, that's not enough to bring it back.
One may think the underlying issue is not fixed, but that's not the case.
It just needs an additional step to really resurrect it....
If I issue a "Check for updates" which is available in the Wordpress Toolkit's root it does bring it back.
This issue is not a problem for me, but it would improve the product a lot IMHO if the "Scan" would do a complete refresh so it brings back this "broken instance" to a managed site.
I know now I have to take an additional step, but others that are still troubleshooting the website may have already fixed the website and still think it's broken.
One of my clients has a Wordpress site that chokes the Wordpress toolkit.
It gives:
Code:
Broken instance onI found the culprit and I can resurrect it by changing the wp-config.php.
There I just comment this line:
Code:
require_once(ABSPATH.'wp-content/plugins/estore/estore.php');Now, the WordPress site is able to get configured by the Wordpress toolkit.
I can do a "Scan" now.
Alas, that's not enough to bring it back.
One may think the underlying issue is not fixed, but that's not the case.
It just needs an additional step to really resurrect it....
If I issue a "Check for updates" which is available in the Wordpress Toolkit's root it does bring it back.
This issue is not a problem for me, but it would improve the product a lot IMHO if the "Scan" would do a complete refresh so it brings back this "broken instance" to a managed site.
I know now I have to take an additional step, but others that are still troubleshooting the website may have already fixed the website and still think it's broken.
