Sandbox Sites

WP Engine's Advanced Restore functionality provides excellent flexibility by allowing customers to restore either files, databases, or both independently. However, there is currently no option to restore individual database tables from a backup. For agencies and developers managing complex WordPress environments, a table-level restore feature would be extremely valuable. Many issues impact only a specific portion of the database, such as: • Corrupted plugin tables • Accidental deletion of custom data • Failed imports or migrations • Ecommerce order data issues • Custom application tables created by plugins • User or content-related data errors In these situations, restoring an entire database is often too disruptive because it can overwrite legitimate changes that have occurred since the backup was created. A table-based restore workflow would allow customers to: • Select one or more tables from a backup snapshot • Preview the tables that will be restored • Restore only the affected tables without impacting the rest of the database • Reduce downtime and data loss risks • Avoid manual database exports, imports, and SQL manipulation This capability would be especially beneficial for agencies, developers, WooCommerce sites, membership platforms, and other data-intensive applications where a full database rollback is often not a practical option. WP Engine already provides granular file and database restore options. Extending that granularity to the table level would provide a powerful middle ground between full database restores and manual database recovery procedures.

Unfortunately, it appears that Agency Sandbox environments do not support multi-site WordPress installs, which is something needed to test before committing to that solution for this specific use case

Option or even manual instructions on how to implement a Tagging Server solution (first party mode) for production sites hosted through WPE using the Advanced Network. Google documentation provides an overview and the type of routing changes needed within the CDN, https://developers.google.com/tag-platform/tag-manager/gateway/setup-guide . As browsers and user privacy tools get more restrictive, this is becoming much more important for marketing.

I love the Sandbox. However, even though they have a tag on them they're still co-mingled together. For me it's showing "Dev (3)" in the Filter, but it doesn't say if they're Paid or Sandbox. And, there's nothing in the Tags. Since there's a tabs that says "All site", "Needs attention" "Needs update" - that would be a great place to put "Paid sites" and "Sandbox sites". I know we can use the CSV to download, however, having a way to clearly distinguish or separate out the Live sites from Sandbox right in "My Sites" would be really great.