Roadmap
MainWP Community
Return to MainWP.com

Shape the Future of MainWP – Your Voice Matters!

Share your ideas, vote and comment on others, and collaborate to make MainWP even better for everyone! Not sure how to get started?

For Developers: Want to fast-track your feature? Submit a well-crafted pull request in GitHub. Quality submissions that align with MainWP's core purpose will be included in upcoming releases.

ℹ️ Having trouble logging in? Try clearing your browser cache and cookies or use a different browser.

Please make some proper activate/deactivate switches.

I'm sure if you enable or disable addons every day, this is not an issue. But when only using this every six months, I'm always confused and find it hard to see whether an addon is enabled or disabled. The current on/off switch makes no sense. Please make it more clear if an addon is active or not active. Thank you. Kind regards, Chilles.

Image

Chrilles 10 days ago

🎨

UI & Usability Suggestions

Feature Request: Umami Analytics Extension

Hi MainWP Team, I am a happy user and I’ve been using MainWP for more than 10 years to manage my sites, and I really appreciate the platform—it saves me a ton of time. I would love to see an extension developed for Umami Analytics. With the increasing complexity of GA4 and the growing focus on privacy (GDPR), many of us in the WordPress community are moving away from Google Analytics. I believe Umami Analytics is a perfect fit for the MainWP ecosystem for several reasons: Self-Hosted Philosophy: Like MainWP, Umami is open-source and can be self-hosted. This aligns perfectly with users who prefer to own their own data. Privacy-Focused: It is GDPR compliant and often doesn't require cookie banners, which is a huge plus for client sites. Cost-Effective: It is completely free when self-hosted. Lightweight: It collects the essential data without bloating the websites. It would be incredibly valuable to have a MainWP extension that connects to a self-hosted Umami instance (or their cloud version) and pulls basic stats (Visitors, Pageviews, Bounce Rate) into the MainWP Dashboard for each child site—similar to how the Google Analytics extension works today. I really believe this would be a popular addition for agencies and developers focused on privacy and data ownership. Keep up the great work! Best regards, Chrilles

Image

Chrilles 21 days ago

💡

New Extension Ideas

Add Official Support for Uptime Kuma in Advanced Uptime Monitor

Please add native support for Uptime Kuma as an uptime-monitoring source in the MainWP Advanced Uptime Monitor extension. Uptime Kuma has gathered over 77,000 stars on GitHub and is consistently recognized in “best open-source uptime monitoring tools” lists. This speaks to its wide adoption and credibility in the self-hosted monitoring space.” This idea has been raised by MainWP users several times in the past but wasn’t pursued because Uptime Kuma did not originally provide an external API or authentication system. That has now changed. Uptime Kuma includes a documented HTTP API and API key authentication, allowing secure read-only access to monitor status and uptime data: 🔗 Uptime Kuma API Documentation To comply with MainWP’s third-party integration policy, I reached out to the Uptime Kuma maintainers to confirm their interest and willingness to collaborate before submitting this request. Developer Response (Uptime Kuma #6270) In GitHub Issue #6270, Uptime Kuma collaborator @CommanderStorm responded: “If the existing HTTP APIs (metrics-endpoint, status pages) are sufficient for your use case, great. Those are stable.” “If that just means ‘open to issues’, fine.” “I don't think external integration requires lots of work on our side.” This indicates that the maintainers are open to third-party integrations using the existing, stable HTTP endpoints (metrics and status pages) for read-only use, and that such use does not require additional work or official partnership on their part. This should ideally fulfill MainWP’s policy requirement to confirm a developer’s interest and willingness to collaborate. Proposed Implementation Add Uptime Kuma as an additional monitoring provider within the Advanced Uptime Monitor extension, alongside Uptime Robot and NodePing. Users would supply: The API URL (e.g., https://status.example.com/api/metrics or /status-page endpoint) Their API key/token (for instances where authentication is required) MainWP would then: Fetch uptime and incident data from Kuma’s metrics or status endpoints Display site status and uptime percentages within the MainWP dashboard Benefits ✅ 100% open-source, self-hosted alternative to commercial uptime services ✅ Data remains private and under user control ✅ No monthly fees or external dependencies ✅ Perfect philosophical fit with MainWP’s self-hosted model

Image

Samuel About 2 months ago

⚒️

Core Requests (Dashboard/Child)

Ability to download point in time backup sets without WordPress running

I really need a way to access backups from various points in time and be able to download them as a zip file (files + database .sql file) where the backup service prepares the download file from the incremental backup files up to the chosen restore point/date. Most of the backups that have MainWP add-ons and support incremental backup at all seem to rely on having a working Wordpress site, preferably the actual source site, that is healthy enough to do the restore. They have various work-arounds for recovering a site that is down / broken but they are a lot of work. Sometimes I just need to make a localhost copy of a site to do some development or testing and having to restore to an external site just so that I can get at the DB and files to copy them to localhost is an extra step and a lot of expensive time. I’m not suggesting you revive your own backup solution that you’ve deprecated but you may want to a) look for additional backup partners that have more efficient and flexible restore/download options and/or b) lobby the existing partners to improve in this area so that, together, you can better compete with other management console / backup solutions like ManageWP’s. If you need a use case, I manage about 50 clients’ sites. Not too long ago some malware managed to get into two of my VPS servers and taint every single account. I needed to get at the backup files from about a week earlier and replace the existing files. I had no way to know if it would be safe to do that from within WordPress and a backup plugin as the malware might attach itself to the restore process and instantly re-infect the sites. It was better to get all the files staged in zip files then use SSH and FTP to remove the existing files, upload the zip file and extract the contents for each site. That would’ve taken days if even possible with the backup solutions that have MainWP add-ons. It took an afternoon with ManageWP.

Image

Scott 2 months ago

⚒️

Core Requests (Dashboard/Child)

Tags as filters globally

Please consider to use tags as filters and it should be managed globally. It also needs to use the AND logic for tags and for the filters, because if we want to filter down the websites to manage only websites, we want to see in our current workflow, the AND logic is the only way to do it. So if I have tags for “Elementor” and for “WooCommerce” and for “VIP” for example, and I want to manage only my VIP websites, that have WooCommerce installed, the AND logic is the only way to do it. These filters should be used globally, so when I select “WooCommerce” AND “VIP”, the MainWP dashboard should only show these websites everywhere, on the Sites, on the Updates page, everywhere! Because I want to manage only those websites at the moment. If I want to manage all sites or other filtered groups of websites, I clear the filters and set it again to my preferences. ManageWP has this option, but they also do not have the “AND” logic, only “OR”, which doesn’t make sense. The “OR” logic is not practical to filter down hundreds of websites. Please consider to make tags as filters and add the “AND” logic to filters!

Image

Peter 4 months ago

⚒️

Core Requests (Dashboard/Child)

Matomo addon limited number of properties in pulldown

Matomo add-on seems to run into limits in the MainWP installation. I just connected a lot (around 120) of Matomo properties, but the ones with the higest piwiks_id numbers (205 and higher) do not appear in the dropdown selector and are not searchable. I can manually connect by entering the right piwiks_id for the wpid in wp_mainwp_wp_piwiks table, which will give me analytics as expected. This is not a structural solution though, because that table will be overruled bij the settings, which will revert to ‘no properties‘ when I save. Can you unlimit the number of webistes that get fetched from Matomo? My limit in Matomo is set to 500 and API tests show that I can get the higher piwik_id websites without a problem, so Matomo is not the restricting factor. I am running latest versions for everything. Thanks for looking at this.

Image

Remco 4 months ago

🔄

Extension Improvements

IP / Server added to Sites

We have numerous hosting servers and lots of websites. It would be incredibly helpful to be able to list the IP of the server in the Sites list. I see this is already stored in the database table so adding it should be trivial. For bonus points: I’ve now written and deleted what I wanted to write here 4 times. I have something bigger in mind now. Short term, have the ability to define name & IPs for server instances and then display the server name in the Sites list.

Image

Ken 4 months ago

⚒️

Core Requests (Dashboard/Child)

Better filtering for plugin updates

Posting this here as per Bojan’s suggestion in support ticket #28473307 We’ve found ourselves needing to filter child sites, and updates in a way that isn’t currently possible without a workaround that requires hundreds or thousands of mouse clicks. Basically we want to be on this page: /wp-admin/admin.php?page=UpdatesManage&tab=plugins-updates but we need the filtering sidebar that’s seen on the right side of: /wp-admin/admin.php?page=PluginsManage I’ve attached a Photoshop mockup of what this would look like:

Image

Skunkworks 4 months ago

⚒️

Core Requests (Dashboard/Child)

Waring before "Save Setting" in Updraftplus addon

Just a small thing: When you click on “save settings” in Updraftplus addon, would have been useful to see a popup warning saying: “You are about to overwrite the settings of all child sites (unless you have specifically specified otherwise in the settings of each child site)” In other add-ons, and when updating plugins, etc., you first select the child sites you want the changes to affect. But in this case, it is done differently by expressly indicating it within the configuration of each child site, which is why when you click “Save Settings” it is not clear enough that you are going to save (and overwrite) the UpdraftPlus settings on all child sites (even if you have not expressly selected any).

Image

Antonio 5 months ago

⚒️

Core Requests (Dashboard/Child)

Programmatic Methods for WP Staging Addon

The following developer methods would be highly beneficial for automating staging site management. Synchronous Staging Site Creation: A method to programmatically create a staging site and wait for the process to complete, returning the new site's URL and ID. Proposed Method: $mainwp_staging->create_staging_site_sync($site_id, $options); Expected Return: array('success' => true, 'staging_url' => '...', 'staging_id' => 123) Staging Process Status Check: A method to check the status of an ongoing staging process, including its current state and progress. Proposed Method: $mainwp_staging->get_staging_process_status($staging_id); Expected Return: array('status' => 'running|completed|failed', 'progress' => ...) Staging Site Cleanup: A method to delete a staging site without affecting the production site’s MainWP connection. Proposed Method: $mainwp_staging->cleanup_staging_site($staging_id); Expected Return: array('success' => true) Thanks for your consideration.

Image

Andrew 5 months ago

🔄

Extension Improvements