PIE Hosting Companion

What it does

A PIE-internal hosting companion that loads as a Must-Use plugin so it can't be accidentally deactivated by clients. Requires PHP 8.0+.

• PIE admin access — Treats any user with an @pie.co.de email address (or pie_admin_override user meta) as a PIE admin, granting administrator capabilities.
• Plugin hiding — Hides Ultimate Branding, WP Hummingbird, and this plugin itself from non-PIE admin users, while keeping them fully functional.
• WPMU DEV restriction — Limits WPMU DEV suite access to PIE admin users via WPMUDEV_LIMIT_TO_USER.
• Branda restriction — Restricts Ultimate Branding access to PIE admin users via its permissions filter.
• URL redirections — Regex-based redirect system with capture group support, conditions (always, not_logged_in, logged_in, not_admin, or a custom callable), and standard HTTP status codes. Rules added via PIE\Redirections\filters\redirect_rules.
• CSP header management — Settings > Pie Security Headers page (pie_admin only) for configuring a Content-Security-Policy header across frontend, admin, and login. Overridable via PIE_CSP_HEADER constant in wp-config.php.
• Staging detection — Detects staging clones by comparing the live URL to a protected option (resilient to search-and-replace). On staging: disables CF7 spam checks and updates Multisite domain mappings for *.staging.tempurl.host.
• Auto-updates — Deploys MU plugin files atomically on activation and after updates, sourcing releases from GitHub via plugin-update-checker.
• Update watchdog — Tracks plugin/theme updates and sends an alert email if an update appears to stall mid-process.

---

Installation:

1. Download the latest copy of pie-custom-functions.zip from https://github.com/pie/pie-custom-functions/releases
2. Upload via wp-admin
3. Activate & enjoy

Deploying updates:

This plugin template is set up to work with integrated WordPress updates through the use of yahnis-elsts/plugin-update-checker and rymndhng/release-on-push-action

In order to deploy an update:

1. (Once) Enable Github Pages on your repository (Settings > Pages) so that a update.json can be read by the Update Checker in production sites.
2. Create a pull request to merge your branch into main and add the appropriate label:
   • release:major
   • release:minor
   • release:patch
3. When merged, the release.yml workflow will update all of your version numbers and commit them back into main and create a github release with an extra artifact:
   1. plugin-slug.zip - the uploadable plugin for manual installation
4. Updates should then show in wp-admin for any users of the plugin