Make it un-ignorably obvious when you're editing a non-canonical environment about wp-stage-switcher

[swalkinshaw]

Isn't the canonical URL always going to be production? If so you can just check for that to add your notices (which is a good idea btw).

[MatthewEppelsheimer]

In most cases yes, but not necessarily.

There are times when we're treating staging (or yet another instance) as
canonical, to stage content edit work before migrating it over to
production, especially during early phases of a site build.

So, which instance is canonical changes regularly throughout our workflows.
In fact it's those transition points that throw people off. This is why we
need this kind of obvious reminder, to help people remember when it has
changed.

On Tue, Sep 29, 2015 at 8:39 AM, Scott Walkinshaw [email protected]
wrote:

Isn't the canonical URL always going to be production? If so you can just
check for that to add your notices (which is a good idea btw).

—
Reply to this email directly or view it on GitHub
#5 (comment)
.

Matthew Eppelsheimer
Rocket Lift

[phone]
[email protected]

I write a newsletter where I share the best articles and podcasts I find on
excellence in digital publishing. Reply with email subject “Subscribe to
Excellence” to join.

[swalkinshaw]

@MatthewEppelsheimer in the use case you explained you'd still need to make changes to your config and move the canonical element to the other env array. The solution I proposed would involve changing a conditional check from production to staging for example. It's basically the same amount of work.

I'm just hesitant to support this because I'd rather people not start adding a lot of other data to ENVIRONMENTS. Having to serialize is bad enough as it is.

[MatthewEppelsheimer]

Your hesitation makes sense and has spurred a lot more thinking that isn't worth going into here.

Let's close this. On my side, we need to get more clear on how best to solve our problem. Thank you for the discussion!