feat: configurable site aliases with per-alias offline/robots settings #224

Closed
opened 2026-06-21 15:57:39 +00:00 by jmiller · 2 comments
Owner

Problem

The dev alias system only supports hardcoded dev.{primary_domain}. Need to support any CNAME/domain alias with individual offline and robots settings.

Use Case

Client has clientsite.com (production, online) and dev.clientsite.com (DreamHost CNAME, same folder). The dev domain should:

  • Stay online while production is offline
  • Have noindex, nofollow robots
  • Share the same database, files, and configuration

Current State

  • site_aliases subform field exists in the core plugin XML config
  • getCurrentAlias() only checks for dev.{primary_domain} (hardcoded)
  • Legacy getCurrentAliasLegacy() read from params but was replaced

Required

  1. Restore getCurrentAlias() to read from site_aliases param
  2. Each alias entry: domain, offline (yes/no), robots directive, redirect_backend
  3. When current request matches an alias domain, apply its offline/robots settings
  4. The offline bypass plugin should respect alias settings
## Problem The dev alias system only supports hardcoded `dev.{primary_domain}`. Need to support any CNAME/domain alias with individual offline and robots settings. ## Use Case Client has `clientsite.com` (production, online) and `dev.clientsite.com` (DreamHost CNAME, same folder). The dev domain should: - Stay online while production is offline - Have `noindex, nofollow` robots - Share the same database, files, and configuration ## Current State - `site_aliases` subform field exists in the core plugin XML config - `getCurrentAlias()` only checks for `dev.{primary_domain}` (hardcoded) - Legacy `getCurrentAliasLegacy()` read from params but was replaced ## Required 1. Restore `getCurrentAlias()` to read from `site_aliases` param 2. Each alias entry: domain, offline (yes/no), robots directive, redirect_backend 3. When current request matches an alias domain, apply its offline/robots settings 4. The offline bypass plugin should respect alias settings
Author
Owner

Branch created: feature/224-feat-configurable-site-aliases-with-per-

git fetch origin
git checkout feature/224-feat-configurable-site-aliases-with-per-
Branch created: [`feature/224-feat-configurable-site-aliases-with-per-`](https://git.mokoconsulting.tech/MokoConsulting/MokoSuiteClient/src/branch/feature/224-feat-configurable-site-aliases-with-per-) ```bash git fetch origin git checkout feature/224-feat-configurable-site-aliases-with-per- ```
Author
Owner

Implemented as Domain Aliases & Staging subform table in DevTools plugin

Implemented as Domain Aliases & Staging subform table in DevTools plugin
Sign in to join this conversation.
No labels
Priority Medium
Type Feature
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoSuiteClient#224