#5768 - After upgrading alpha2 to alpha3 I lost "pages" on the front and can't load the control panel.

I did notice after doing the "file" upgrade portion and then doing the database update that this was shown to me and I thought to myself uh oh these options may have been installed and or adjusted when some of them are turned off or were not installed originally AKA Word Filter and a few others.

Do a database upgrade (upgrade/install core-database/modules/blocks)
Upgraded/installed:

Installed module purchase <- originally not installed
Installed apache_config_files
Installed banners <- originally not installed
Installed cns_multi_moderations <- originally not installed
Installed e-commerce <- originally not installed
Installed installer <- originally not installed
Installed ldap <- originally not installed
Installed newsletter <- originally not installed
Installed shopping <- originally not installed
Installed SMS <- originally not installed
Installed syndication <- originally not installed
Installed welcome_emails <- originally not installed
Installed wiki <- originally not installed
Installed wordfilter <- originally not installed

Just ran the updater on the local site. I should have also mentioned that after all was done going back to the home page after upgrading I was placed into the Rules Agreement page and had to accept to get into the home page... as the admin? both local and live are now with control panel error the same.

That's interesting. I haven't seen that issue before where the upgrader is installing stuff that was previously uninstalled. That may be in connection with another bug I'm seeing. Report that as a separate issue please if you could.

For the rules agreement, it's a new feature. For better data law compliance, member accounts now have a new custom profile field containing the exact text of the declarations they agreed to. When a member's text does not match the currently configured site declarations, they are forced to re-read and agree to the rules (so at first, this means everyone since the CPF is new and thus blank). This also applies to admins. My logic behind that is because admins are bound by their own rules / ToS as well especially should they no longer be an admin anymore in the future. So again for legal compliance with data regulations, we need to make sure they consented to their own rules / ToS.

Note this will happen again whenever you change the text of the declarations setting; all members and staff/admins will be required to re-read and re-agree to the rules.

Eventually in a future update members will also receive an e-mail copy of their agreement, which is also required by some new laws being put in place by states in the US.

Actually disregard what I said about making a new issue. This became a critical fix and thus I made a quick release 11.alpha4.

See https://composr.app/news/view/releases/composr-11-alpha4.htm

Resolved except the missing pages portion cannot be reproduced. Feel free to create a new tracker issue if you can gather more information / a good reproduction case with steps and server info / site config.