Features request

Currently, visual regression testing focuses only on the homepage, which may not reflect issues occurring on other critical pages. It would be valuable to allow users to select specific pages or URLs to include in visual regression tests. This could include landing pages, checkout pages, contact forms, or other key templates where visual integrity is important.

Automated updates can be one of the biggest time-savers in WP Umbrella — but without control over which versions are installed, automation can quickly become a problem instead of a benefit. For agencies, developers and administrators managing production sites, blindly installing every new version (including minor and major releases) introduces unnecessary risk and reduces trust in automated updates. This feature request proposes version-aware automated updates, allowing users to automate safely without giving up control. --- The problem Today, automated updates apply to all new versions of a plugin (core or theme if added) — regardless of whether the release is a patch, minor, or major update. This is especially problematic for complex and business-critical plugins such as WooCommerce, where: Minor and major releases frequently introduce breaking or behavioural changes These updates often require testing, staging, or client approval Patch and security releases, on the other hand, should usually be installed automatically As a result, many users either: Disable automated updates entirely, or Manually babysit updates — defeating the purpose of automation This makes automated updates less usable for agencies and professionals managing real production environments. --- Proposed solution Add version-level filtering to automated updates, based on semantic versioning (SemVer). Global update rules Allow users to define a default rule for all plugins/themes: Patch releases only (e.g. 1.2.3 → 1.2.4) Patch + minor releases (e.g. 1.2.3 → 1.3.0) All releases (including major) Per-plugin overrides Allow individual plugins/themes to override the global rule, for example: WooCommerce → patch only Yoast SEO → patch + minor Small utility plugin → all releases Simple SemVer-based logic Detect version type based on version string structure Optionally allow a short delay (e.g. only auto-install patch releases after X days) This does not need to be perfect SemVer enforcement — even basic version segmentation would cover the vast majority of real-world cases. --- Why this matters (broader impact) ✅ Safer automated updates for production sites ✅ Higher adoption of automation among agencies and developers ✅ Fewer incidents caused by unintended upgrades ✅ Aligns WP Umbrella with professional update workflows already used in staging-first environments Many plugins already follow semantic versioning in practice. Even when they do not do so perfectly, having version-aware automation is still vastly safer than treating all updates as equal. --- Summary This feature does not remove automation — it makes automation trustworthy. Giving users control over which types of updates are installed automatically allows WP Umbrella to remain fast and efficient, while also being safe enough for serious production use. If this is important for your workflow as well, please upvote and share your thoughts. �

My site's names are all funky when they have & and ' in the name. For example, here are three site names: Darrah's All-Star Academy, Monroe & Company CPAs, Weible & Associates, Co.

As a WordPress maintenance provider, I want to inform my clients directly from WP Umbrella about important updates and developments, without having to use an external program. Current Situation WP Umbrella currently has a template function for automated monthly reports. This works excellently for periodic communication, but there's no option for one-time, urgent messages to selected clients. Concrete Use Cases Major WordPress releases require proactive client communication. I want to inform clients about upcoming changes, manage expectations, and communicate potential downtime. Currently, I need to switch to another program for this, even though all relevant data is already in WP Umbrella. Other Scenarios: Major core updates or breaking changes Expected downtime for maintenance Critical security updates requiring extra attention Proactive communication about PHP version upgrades Changes in hosting or infrastructure Proposed Functionality Ability to send one-time emails to selected sites/clients Selection based on existing filters (WordPress version, PHP version, labels, groups) Simple editor for email content (doesn't need to be fancy, just functional) Preview function before sending Nice to Have: Merge tags for personalization (site name, WordPress version, etc.) Save drafts for later sending Sending history/log Why This is Valuable for WP Umbrella For users like me: One platform for all website management communication Time savings (no switching between tools) Data already present (which sites, which versions, which clients) Better workflow, less frustration For WP Umbrella as a product: Higher customer retention (one less tool needed) Competitive advantage over ManageWP and MainWP Natural complement to existing client communication features Higher perceived value of the platform Additional Context Currently, sites can only be linked to one template (for monthly reports). A one-time email function solves this without complicating the existing template structure. These are two different use cases that can coexist perfectly.

It would be good to be able to see useful information on the site overview page rather than just buttons/links to move you to uptime, updates or security pages for a specific site. For example, displaying the WordPress version, PHP version and number of plugins with updates available in each row in the list. Being able to sort/filter by these values would be useful.

It would be incredibly helpful to have the ability to set additional predefined fields in client settings that can be automatically included in client reports. For instance, we provide clients with a unique dashboard link, which is the only personalised element in each report. This dashboard URL is separate from their website domain, and currently, we need to manually update the custom works date each month just to reference this field. By introducing a predefined list of custom fields in client settings, we could streamline the process, reduce manual updates, and further automate the reporting workflow. This feature would greatly enhance efficiency and accuracy in report generation.

Hi it would be nice to be able to add an alert on some site health issues, most important are if site is not indexable (and should be) and if DEBUG is set to true on production, as these need to be fixed as soon as possible.

Some plugins are related to master plugins [eg Woocommerce B2B is related to Woocommerce]. When we launch Bulk Management for plugins, it would be nice that the master-plugins are updated first and avoiding that the slave-plugins are driving the website into a severe failure. Occured once in the last seven days.

The ability to open/view notes per website directly on the dashboard. This can be infopanel that opens on hover or click

Integrate with Wordfence to be able to run scans, see vunabilities from the panel