Solid Security Extension - Undesired resetting of settings for notifications
The Solid Security extension has been discovered to be the source of an issue we’ve been experiencing that is so detrimental to our time that we will have to discontinue using the extension completely until some kind of fix for this issue is found. The issue Whenever the MainWP dashboard pushes Solid Security settings out to all of our child sites it reverts our defined notification email preferences from “Us” to “All Admin users”. This results in us losing the desired setting on 100+ child sites and means that We have to manually revert each site back to our desired setting. One at a time. We have to deal with child site owner’s email inquiries about the sudden emails that they’re receiving from their website about “Security issues” Both of which are very time consuming things. The extension should never alter Solid’s Notification settings for child sites.
Skunkworks 10 days ago
Extension Improvements
Solid Security Extension - Undesired resetting of settings for notifications
The Solid Security extension has been discovered to be the source of an issue we’ve been experiencing that is so detrimental to our time that we will have to discontinue using the extension completely until some kind of fix for this issue is found. The issue Whenever the MainWP dashboard pushes Solid Security settings out to all of our child sites it reverts our defined notification email preferences from “Us” to “All Admin users”. This results in us losing the desired setting on 100+ child sites and means that We have to manually revert each site back to our desired setting. One at a time. We have to deal with child site owner’s email inquiries about the sudden emails that they’re receiving from their website about “Security issues” Both of which are very time consuming things. The extension should never alter Solid’s Notification settings for child sites.
Skunkworks 10 days ago
Extension Improvements
Present Health-Check-Issues on MainWP
The healt-check sumary is already on the page MonitoringSites, but we miss the issues that wordpress itself detected. Such us: “Your site is very slow, install a cache plugin.” At the moment we have to visit most of our wordpress sides by hand to find out what exactly is the problem on the website.
Ingo 11 days ago
Core Requests (Dashboard/Child)
Present Health-Check-Issues on MainWP
The healt-check sumary is already on the page MonitoringSites, but we miss the issues that wordpress itself detected. Such us: “Your site is very slow, install a cache plugin.” At the moment we have to visit most of our wordpress sides by hand to find out what exactly is the problem on the website.
Ingo 11 days ago
Core Requests (Dashboard/Child)
I want a feature that, even if I have set a plugin to automatically update a week after its release, will not update the old plugin if a new version of that plugin is released, and will instead automatically update to the new version a week later.
Manabu 15 days ago
Core Requests (Dashboard/Child)
I want a feature that, even if I have set a plugin to automatically update a week after its release, will not update the old plugin if a new version of that plugin is released, and will instead automatically update to the new version a week later.
Manabu 15 days ago
Core Requests (Dashboard/Child)
Hi,
To add value to my customer reports, I would love to see more Google analytics data embedded into the clients report. We can see it in our dashboard, but not the report. Clients love to see they are getting value for money and to add this to the report would be a great improvement.
Julie 15 days ago
Extension Improvements
Hi,
To add value to my customer reports, I would love to see more Google analytics data embedded into the clients report. We can see it in our dashboard, but not the report. Clients love to see they are getting value for money and to add this to the report would be a great improvement.
Julie 15 days ago
Extension Improvements
Manage Plugins - Removal Progress Status
It might be nice to actually see the sites from which the plugins are bing removed as they are removed from each. ☺️
Basil 17 days ago
Core Requests (Dashboard/Child)
Manage Plugins - Removal Progress Status
It might be nice to actually see the sites from which the plugins are bing removed as they are removed from each. ☺️
Basil 17 days ago
Core Requests (Dashboard/Child)
Feature Request: Branch Lock for WordPress Core Updates
Hi MainWP Team and Community, with WordPress 7.0 approaching, many agency owners face a situation that MainWP currently cannot handle natively: staying on a minor branch deliberately while a new major version is available. The current limitation MainWP lets you ignore a core update or update to the latest version. There is no option to say: "Stay on the 6.9.x branch. Apply minor updates within that branch. Do not touch 7.0." The only workaround would be wp-config.php edits per site — which defeats the entire purpose of centralized management. The Feature Request: Branch Lock A simple, MWP-native control on the Updates or Site Settings level: A toggle: Enable Branch Lock — yes / no A branch input field: e.g. 6.9 Behavior: MWP recognizes any 6.9.x update as valid and applicable. Any version outside that branch (7.0, 7.1 etc.) is treated as "up to date — no action required." This is different from "Ignore Core Update" because it does not lock a specific version — it locks a branch, so minor and security updates within that branch still flow through normally. Why this matters WordPress 7.0 is announced as a significant architectural release. Many agencies managing dozens or hundreds of client sites need time to test compatibility before committing to a major version jump — but they still want to keep client sites patched within the current branch in the meantime. A Branch Lock feature would make MainWP the go-to solution for exactly this kind of professional, risk-aware update management. There was a standalone WordPress plugin once that allowed locking to a specific version number. It’s long outdated and had a critical flaw: it required manually entering the exact version per site, not a branch. The Branch Lock concept improves on this significantly by being branch-aware, centrally managed, and integrated into the MainWP workflow. Thanks for considering this.
Benjamin 18 days ago
Core Requests (Dashboard/Child)
Feature Request: Branch Lock for WordPress Core Updates
Hi MainWP Team and Community, with WordPress 7.0 approaching, many agency owners face a situation that MainWP currently cannot handle natively: staying on a minor branch deliberately while a new major version is available. The current limitation MainWP lets you ignore a core update or update to the latest version. There is no option to say: "Stay on the 6.9.x branch. Apply minor updates within that branch. Do not touch 7.0." The only workaround would be wp-config.php edits per site — which defeats the entire purpose of centralized management. The Feature Request: Branch Lock A simple, MWP-native control on the Updates or Site Settings level: A toggle: Enable Branch Lock — yes / no A branch input field: e.g. 6.9 Behavior: MWP recognizes any 6.9.x update as valid and applicable. Any version outside that branch (7.0, 7.1 etc.) is treated as "up to date — no action required." This is different from "Ignore Core Update" because it does not lock a specific version — it locks a branch, so minor and security updates within that branch still flow through normally. Why this matters WordPress 7.0 is announced as a significant architectural release. Many agencies managing dozens or hundreds of client sites need time to test compatibility before committing to a major version jump — but they still want to keep client sites patched within the current branch in the meantime. A Branch Lock feature would make MainWP the go-to solution for exactly this kind of professional, risk-aware update management. There was a standalone WordPress plugin once that allowed locking to a specific version number. It’s long outdated and had a critical flaw: it required manually entering the exact version per site, not a branch. The Branch Lock concept improves on this significantly by being branch-aware, centrally managed, and integrated into the MainWP workflow. Thanks for considering this.
Benjamin 18 days ago
Core Requests (Dashboard/Child)
White Label API Options
Hi guys, would it be possible to add the option to toggle on the ‘visually hide MainWP Child plugin’ with one of the API endpoints — we’re setting up some customisations as part of our onboarding process and one of the things we want to ensure is that the plugin is hidden from the plugin list within wp-admin. Would be great to have an option to automated this within the setup. Thanks!
Martin 23 days ago
Core Requests (Dashboard/Child)
White Label API Options
Hi guys, would it be possible to add the option to toggle on the ‘visually hide MainWP Child plugin’ with one of the API endpoints — we’re setting up some customisations as part of our onboarding process and one of the things we want to ensure is that the plugin is hidden from the plugin list within wp-admin. Would be great to have an option to automated this within the setup. Thanks!
Martin 23 days ago
Core Requests (Dashboard/Child)
Block plugin or theme translations
I have a plugin that's been marked as "Do Not Update," but its translations keep appearing in the list of items to update. I'd like it if translations for plugins or themes could also be marked as "Do Not Update," or even better, if they were automatically marked as such when the associated plugin or theme is marked as "Do Not Update."
Planea about 1 month ago
Core Requests (Dashboard/Child)
Block plugin or theme translations
I have a plugin that's been marked as "Do Not Update," but its translations keep appearing in the list of items to update. I'd like it if translations for plugins or themes could also be marked as "Do Not Update," or even better, if they were automatically marked as such when the associated plugin or theme is marked as "Do Not Update."
Planea about 1 month ago
Core Requests (Dashboard/Child)
Track plugin/theme/WP activity regardless of the CRON setting
It is understandable to turn CRON monitoring off since there is a lot of unneeded things happening via CRON. But I think a few things are still important enough to track regardless if they happen through CRON or not. Major things like WP updates, plugin updates (or delete, add, etc), and theme updates (new, deleted, activate). Even user activity as well (deleted user, change user role). One context for this is when using Solid Security. If a plugin has a critical security vulnerability, SS will update it automatically even if it’s not normally set to auto-update. However, this plugin update is not in the MainWP Child Reports log and thus not in the Advanced Reports either. I don’t want to turn on logging all CRON activity just to catch a stray plugin/theme/WP activity. I think those things are important enough to track no matter how they are done.
Zack about 1 month ago
Core Requests (Dashboard/Child)
Track plugin/theme/WP activity regardless of the CRON setting
It is understandable to turn CRON monitoring off since there is a lot of unneeded things happening via CRON. But I think a few things are still important enough to track regardless if they happen through CRON or not. Major things like WP updates, plugin updates (or delete, add, etc), and theme updates (new, deleted, activate). Even user activity as well (deleted user, change user role). One context for this is when using Solid Security. If a plugin has a critical security vulnerability, SS will update it automatically even if it’s not normally set to auto-update. However, this plugin update is not in the MainWP Child Reports log and thus not in the Advanced Reports either. I don’t want to turn on logging all CRON activity just to catch a stray plugin/theme/WP activity. I think those things are important enough to track no matter how they are done.
Zack about 1 month ago
Core Requests (Dashboard/Child)
Pause plugin updates for individual websites
It would be useful to be able to mark a site for exclusion from plugin updates so that they are separated for the regular sites. This would allow us to still connect and monitor a site but only update plugins after review and testing.
Mike about 1 month ago
Core Requests (Dashboard/Child)
Pause plugin updates for individual websites
It would be useful to be able to mark a site for exclusion from plugin updates so that they are separated for the regular sites. This would allow us to still connect and monitor a site but only update plugins after review and testing.
Mike about 1 month ago
Core Requests (Dashboard/Child)
Connected sites report
Would it be possible to include an exportable report that lists all the connected websites and their current status. Eg pending updates, wordpress core version, php version.
Mike about 1 month ago
Core Requests (Dashboard/Child)
Connected sites report
Would it be possible to include an exportable report that lists all the connected websites and their current status. Eg pending updates, wordpress core version, php version.
Mike about 1 month ago
Core Requests (Dashboard/Child)
Improve Snippets add-on with folders or tags
Hi, It would be great to have folders or tags in the Snippets add-on to better organize snippets. Managing many snippets is currently quite limited. Thanks!
Kevin about 2 months ago
Extension Improvements
Improve Snippets add-on with folders or tags
Hi, It would be great to have folders or tags in the Snippets add-on to better organize snippets. Managing many snippets is currently quite limited. Thanks!
Kevin about 2 months ago
Extension Improvements
Admin and Site Enhancements (ASE) COLLAB
What do you guys think about Admin and Site Enhancements (ASE) plugin addon? It’s a very useful tool that ALOT of people use on every site. Its mainly for us who are administrating the websites. I personally think it would add huge value to the community.
aleksander about 2 months ago
Core Requests (Dashboard/Child)
Admin and Site Enhancements (ASE) COLLAB
What do you guys think about Admin and Site Enhancements (ASE) plugin addon? It’s a very useful tool that ALOT of people use on every site. Its mainly for us who are administrating the websites. I personally think it would add huge value to the community.
aleksander about 2 months ago
Core Requests (Dashboard/Child)
WPML Secondary Language Support for Post Publishing
Hello MainWP Team, I would like to suggest a feature improvement regarding WPML compatibility. Currently, when publishing posts through MainWP on a website that uses WPML, the posts are always published in the default language. This creates a limitation for users managing multilingual websites, as there is no option to directly publish content in a secondary language. The issue: When I try to publish a post intended for a secondary language (e.g., Arabic, Spanish, etc.), MainWP publishes it under the default language instead of the selected WPML language. Suggested improvement: Please add support for WPML language selection when creating or publishing posts via MainWP. Ideally, this would include: A dropdown or option to choose the target language (as defined in WPML) Proper assignment of the post to the selected secondary language Compatibility with WPML translation structure Why this is important: Many users manage multilingual WordPress sites, and being able to publish directly to a specific language would significantly improve workflow efficiency and automation accuracy. Thank you for considering this feature. It would be a valuable addition for WPML users. Best regards
a about 2 months ago
Core Requests (Dashboard/Child)
WPML Secondary Language Support for Post Publishing
Hello MainWP Team, I would like to suggest a feature improvement regarding WPML compatibility. Currently, when publishing posts through MainWP on a website that uses WPML, the posts are always published in the default language. This creates a limitation for users managing multilingual websites, as there is no option to directly publish content in a secondary language. The issue: When I try to publish a post intended for a secondary language (e.g., Arabic, Spanish, etc.), MainWP publishes it under the default language instead of the selected WPML language. Suggested improvement: Please add support for WPML language selection when creating or publishing posts via MainWP. Ideally, this would include: A dropdown or option to choose the target language (as defined in WPML) Proper assignment of the post to the selected secondary language Compatibility with WPML translation structure Why this is important: Many users manage multilingual WordPress sites, and being able to publish directly to a specific language would significantly improve workflow efficiency and automation accuracy. Thank you for considering this feature. It would be a valuable addition for WPML users. Best regards
a about 2 months ago
Core Requests (Dashboard/Child)
Completed
Cost tracker duplication
A little improvement that would be really practicle in some cases, would be the option to duplicate a cost. This would prevent to redo all the cost parameters for a an identical category and just change the things that are different (client/price/…). That would be saving time !
Stéphane about 2 months ago
Extension Improvements
Completed
Cost tracker duplication
A little improvement that would be really practicle in some cases, would be the option to duplicate a cost. This would prevent to redo all the cost parameters for a an identical category and just change the things that are different (client/price/…). That would be saving time !
Stéphane about 2 months ago
Extension Improvements
Wordfence - Firewall - External Allowlist of IPs
It would be useful for us to be able to import/append from an externally maintained list of safe IPs. We imagine it would look something like this: That way several of our tools (including MainWP) could benefit from that central “Single Source of Truth” list. We’d have less “spots” to keep up to date.
Skunkworks about 2 months ago
Extension Improvements
Wordfence - Firewall - External Allowlist of IPs
It would be useful for us to be able to import/append from an externally maintained list of safe IPs. We imagine it would look something like this: That way several of our tools (including MainWP) could benefit from that central “Single Source of Truth” list. We’d have less “spots” to keep up to date.
Skunkworks about 2 months ago
Extension Improvements
Support for Multiple Cloudways API Connections
Some clients have their own Cloudways account. It is not possible to set them as the backup provider on a per-site basis, nor is it possible to have more than one API connection in the main settings. I tried creating a Team account in Cloudways to connect to multiple client accounts, but Team accounts are not permitted API access in a way that applies to multiple Cloudways accounts.
Georgene 2 months ago
Core Requests (Dashboard/Child)
Support for Multiple Cloudways API Connections
Some clients have their own Cloudways account. It is not possible to set them as the backup provider on a per-site basis, nor is it possible to have more than one API connection in the main settings. I tried creating a Team account in Cloudways to connect to multiple client accounts, but Team accounts are not permitted API access in a way that applies to multiple Cloudways accounts.
Georgene 2 months ago
Core Requests (Dashboard/Child)
File Monitor
It would be nice to have a File Monitor for a website that is scheduled to check WordPress Core checksum along with any WordPress Plugins and Themes hosted by WordPress itself. All other files could just be monitored for add/update/delete/permissions. Any changes and there would be reports on the dashboard and emails sent. If WP Core or plugins etc get updated through MainWP or by someone with appropriate credentials then these changes can be recorded but notifications don’t need to go out as they were done on purpose by the admins.
Tom 3 months ago
Core Requests (Dashboard/Child)
File Monitor
It would be nice to have a File Monitor for a website that is scheduled to check WordPress Core checksum along with any WordPress Plugins and Themes hosted by WordPress itself. All other files could just be monitored for add/update/delete/permissions. Any changes and there would be reports on the dashboard and emails sent. If WP Core or plugins etc get updated through MainWP or by someone with appropriate credentials then these changes can be recorded but notifications don’t need to go out as they were done on purpose by the admins.
Tom 3 months ago
Core Requests (Dashboard/Child)
Completed
Add internal link from "Install plugins" to the Favorites add-on (if installed)
On this page: /wp-admin/admin.php?page=PluginsInstall under the tab “Install from Favorites” There should be a link similar to: "You can manage your favorite plugins [here](/wp-admin/admin.php?page=Extensions-Mainwp-Favorites-Extension)" I can't tell you how many times I've struggled to remember or find where that list of favorites is maintained while I’m at that first URL. Aside: Also please add a translation to change “🇺🇸 Favorites” to “🇨🇦 Favourites”
Skunkworks 3 months ago
Core Requests (Dashboard/Child)
Completed
Add internal link from "Install plugins" to the Favorites add-on (if installed)
On this page: /wp-admin/admin.php?page=PluginsInstall under the tab “Install from Favorites” There should be a link similar to: "You can manage your favorite plugins [here](/wp-admin/admin.php?page=Extensions-Mainwp-Favorites-Extension)" I can't tell you how many times I've struggled to remember or find where that list of favorites is maintained while I’m at that first URL. Aside: Also please add a translation to change “🇺🇸 Favorites” to “🇨🇦 Favourites”
Skunkworks 3 months ago
Core Requests (Dashboard/Child)