Peter, the build worked and I am pretty sure I found and used the right artifacts.

But within seconds of opening the site and starting the installer, I got this yellowness.

If you try and don't see this, would you please give me some steps/help in getting to the right artifacts for the build of this PR?

Ah ... the installer. Rrright. That one has no portal so this new code bombs when trying to determine whether to override the app settings. OK, fix incoming.

Okay, logged in as Host, things look like they work well. I was able to flip between Global override and not, the SITE version appeared, tested a bit, no issues.

The rewrite of the CRM paragraph is really great. It always bugs me when things are only written so the developer in the moment knows what it means. Your new version will hopefully make sense to anyone!

Two issues now, first is minor: The UI feels a little awkward. Would you consider stacking them in just one of the columns? I am sure the blank right column will get taken by something upcoming in v10.02.04 or higher. Or, just put only the big paragraph in the left column and stack the 3 items in the right column: Override toggle, Host Inc, Site Inc. Also, rather than have the Site Inc group disappear, I'd pretty strongly suggest just disabling it instead so its grey'd out but still visible. For new users that will feel more intuitive and self-explanatory-at-a-glance as to how the toggle will work (since the default is off).

Second, this one is more serious... to me. When Override Global CDV is True, I believe a Portal Administrator should be able to increment their SITE VERSION.

If you disagree with that, the rest can be ignored.

If it should be an option, here is what a portal admin sees if he goes to the same panel in the PB. Maybe a future contribution if it doesn't make sense right now?

Point taken about 1. You can tell I struggled to make things a bit more coherent.

Point 2 opens quite the box of Pandora. Currently none of the server settings are accessible by an admin. The entire controller is locked down. Opening up stuff selectively is possible, of course, but is tricky and can introduce security vulnerabilities. I.e. a high risk intervention. Which I hate.

One way we could address that is to move the portal version increment button to some other place. Both in the UI as well as backend code. But where should it go?

Agreed. Leave idea 2 for a future discussion or issue, if/when. I double-checked that it was not an option in v9.any

Thanks again for accidentally teaching me how to install a build of a PR! 🙂

I've pushed a change to the layout to address the first point. I'm still quite attached to the two column approach so I left that (if we ever need that space we'll cross that bridge when we get there IMHO). But now the right hand is always visible and is just disabled if the switch is off.

Works!! ✅