Ryan McCue
Ryan McCue
I think there's a ticket in Trac about doing similar in core, but unable to find it now. Last I recalled there were some potential compatibility issues but cannot remember...
As a lower effort solution, I think option 1 from upstream (reinstate the author control) may be easier to implement; we would likely need to add some explanatory text, but...
The way signups works is pretty confusing, and mostly makes sense for a massive multisite install like WordPress.com. Long-term, we might want to look at skipping this process entirely for...
(Also, it may be worth considering copying some of the changes I made to the Altis Central auth signup process. Ping me in Slack for more details.)
This may also be coming from the local storage preferences for A/B testing in the sidebar.
Is it better than before?
Yeah, the difficulty of this is the decentralised nature of the configuration; we'd need to pull them together somehow without centralising it somewhere. Alternatively, we could bodge it into a...
> Yeah we can do this by putting a schema.json into each module which contains its module definition, and then the main schema.json in `altis/core` would pull each of them...
> As far as I know we don't have a high turnover of new or removed modules That is true, but it also breaks the conceptual modularity by having dependencies...
Opened documentation PR at https://github.com/humanmade/altis-documentation/pull/430 to encourage users to explicitly set that.