How does WordPress ToolKit keep track of debug settings?
I think I know the answer to this one but I just want to double-check...
When you tweak debugging settings via WordPress ToolKit it writes rules to the wp-config.php file. But, if you then manually change (or delete) rules by editing wp-config.php directly ToolKit doesn't notice the settings have changed.
In other words, a cPanel user might set WP_DEBUG to true via WordPress ToolKit. Next, a developer sees the setting in the wp-config.php file and changes it to false. At that point WordPress ToolKit is out of sync.
Similarly, if I change the site title via the WordPress dashboard I still see the old site title in the ToolKit interface. ToolKit is again out of sync.
Are issue like this simply the price to pay for using ToolKit, or is there a way to sync the settings in ToolKit with the actual settings? If not, is the general advice that you should never edit settings that ToolKit handles outside ToolKit (i.e. by editing files directly, changing settings in the option table or via WP-CLI)?
-
Looks like the syncing trick is to detach the Wordpress install and then scan for it. 0 -
I've done some testing. When you detach a site and scan for it ToolKit correctly picks up the search engine indexing, debugging and WP_CRON settings. It does not correctly pick up the password protection and hotlinking settings. 0 -
Hello! You shouldn't need to detach anything. You should simply need to re-scan the website by clicking the button shown in my screenshot. I confirmed this works via enabling debugging in the ToolKit, setting it to "false" within the wp-config.php manually, and then clicking that "scan" button. Does this work for you? 0 -
Hi Anthony, Ah, I found the "refresh" button. That works pretty well! The only tool that doesn't seem to sync is the hotlink protection. I've enabled that in cPanel, but it's still showing as disabled in Toolkit. Other than that it's all working quite nicely. 0 -
I'm glad to hear you got that resolved! When I am on shift tomorrow, I will double-check on this Hotlink Protection issue and get back to you as soon as possible. 0 -
I'm curious if anyone has been able to reproduce this? 0 -
I'm curious if anyone has been able to reproduce this?
My apologies for the delay in response, I can't seem to reproduce this. Would you be able to open a ticket using the link in my signature and provide me with the ID? Otherwise, could you ask your web hosting provider to open a ticket on your behalf? Thanks!0 -
That's curious. I can reliably reproduce this. The cPanel hotlink protection works fine, but both enabling and disabling hotlink protection via Toolkit does absolutely nothing (the .htaccess file is never updated when I change the setting via Toolkit). Unfortunately I would need to raise a ticket via my employer, which they are never very keen on. If there is a bug tracker then I'm more than happy to provide a report with all the steps needed to reproduce the issue, a before and after copy of the .htaccesss file and the domain's Apache config file and whatever other information would be useful. But as far I'm aware there is no issue tracker, and it sounds like this only an issue on my test server anyway. 0 -
That's curious. I can reliably reproduce this. The cPanel hotlink protection works fine, but both enabling and disabling hotlink protection via Toolkit does absolutely nothing (the .htaccess file is never updated when I change the setting via Toolkit). Unfortunately I would need to raise a ticket via my employer, which they are never very keen on. If there is a bug tracker then I'm more than happy to provide a report with all the steps needed to reproduce the issue, a before and after copy of the .htaccesss file and the domain's Apache config file and whatever other information would be useful. But as far I'm aware there is no issue tracker, and it sounds like this only an issue on my test server anyway.
Understood! I am going to do some further testing on my end and will be in touch with you tomorrow. Thank you for your patience.0
Please sign in to leave a comment.
Comments
10 comments