No staging for addon domains?

rdbf

One client uses a few addon domains, with separate app installations. These websites receive separate vhosts by Enhance, with separate options under development tools. But why, when I want to create a staging for it, can I only choose the primary domain to make a staging from?

Btw, when I clone the primary domain as staging, it clones everything, including the addon domain apps, which then end up broken as staging because the DNS can't figure out what the entries need to be.

Besides just using a plugin for this, would there be any way to make this work?

xyzulu

Only way to make it work is not use addon domains.
Alternatively, use another staging tool ie a plugin

rdbf

xyzulu Only way to make it work is not use addon domains.

True, but the use of addon domains came about as a 'fix' to the issue of resource limits not applying to packages, but to 'websites'. Plugins work off course, but require a bunch of extra work, and I don´t see most of our customers being able to do that even with a proper guide. And I'd have to update products and guides to specifically say that staging can only work for the primary domain, but clones everything including addon domains (although, not working....) and might break the addon domains again on pushing live.

I'm wondering if I'm the only one running into this because of the resources/package issue.

Orlando

I agree that staging websites should work for addon domains too, not only for the plan’s primary domain. Each addon domain should get its separate staging settings.