Recent content by custer

Hey @burnley, thanks for providing such a detailed report, this is much appreciated. Let me discuss this with the team and figure out how we can solve the issues you're reporting in the next major release. I'll be back here with more questions and details later.

At the moment it's only Vulnerability Protection and what we call "reactivity" (meaning if a change related to plugins or themes happens inside WordPress, WPT will know about it immediately w/o having to wait for maintenance task). If you have plugin installed, login to WordPress from WPT will...

@neijek Sure, you can submit your idea here: https://features.plesk.com/tabs/28-planned-roadmap When submitting the idea, please provide as much info as possible for the problem you're having (focus on the problem, not the solution). If you don't see your submission appear in the list after...

Hey everyone, WP Toolkit v6.11 with the fixes we've discussed is out. Please note that this release will be going through a gradual rollout procedure to make sure we can catch any breaking bugs before they do too much damage, so it might not be available on your servers immediately. PS. If you...

Hi everyone, WPT v6.11 is out, check out the changelog: 6.11.0 (10 Jun 2026) [+] Site administrators can now manage WP Toolkit security measures directly from the WordPress admin dashboard via the WP Toolkit plugin [+] REST API now supports triggering a WordPress installation scan for a...

You probably misunderstood -- we did not plan to bring back "ignore low-risk" option in v6.11. We wanted to make sure that (I'm quoting myself from this thread)

@apisystems This week

Hey @watou, we have identified two issues related to tokens and authorization, and we're working on fixing them. I'm expecting these fixes to be delivered in the upcoming WPT v6.11 release scheduled for next week. The ID of your particular issue is: EXTWPTOOLK-12962. Again, thank you both for...

@watou The changes are applied when the hourly WP Toolkit maintenance task is executed. You can either wait for an hour and try again, or run the maintenance task manually:

@watou Yes, you are right, it should be set to false (or 0). Sorry about this! I've edited my original post to avoid confusing others.

@watou Thank you for the explanation, this definitely helps understand your situation better. In this case I would recommend to hide the GUI instead of uninstalling the plugin. This can be done by adding the following line to panel.ini file: The plugin will continue to work (vulnerability...

Hi @watou, Can you please explain your situation in more detail? As in, who are these admin users, and which functionality they should have no access to? We'd like to make sure the plugin is useful for everyone, and to provide full granularity over which plugin functionality is shown to which...

This is going to be a part of WP Toolkit v6.11 major version, which is planned to be released very soon. We want to be sure we've covered all the edge cases that result in unexpected behavior.

This is correct, thanks @Kaspar

Hi @Tinpeas, This is an oversight on our part. We'll fix this in the next WP Toolkit update -- the red warning next to "Mitigate vulnerabilities" should be present only if there are high-risk or critical vulnerabilities on the website.