v1.6.5

Retires the site plugin. Core owns sites now.

Schema step 332 (fogproject working-1.6) reconstructs the plugin's data into the core sites tables and then drops the plugin's own, so every file in the plugin read tables that stop existing the moment an admin runs the schema updater.

Leaving it installed was not the safe option. Four of its hooks enforced the site boundary by asking the dropped tables which sites a user belonged to — and Route::getIds() returns an empty array rather than raising when its table is gone, so the answer came back "no sites" and the plugin denied every host, user, group and usergroup to every non-* user. Silent: no error, no log line, just an empty host list, on exactly the installs that had site data to migrate.

Core replaced all four surfaces first:

Removed hook	Core replacement
sitescopecheck	Authorization::objectInScope() (#1069)
listsitehosts	the AJAX list path in FOGPage::index() (#1071)
filtersitemassdata	Route::_applySiteScope() (#1071)
sitedeletemassitems	the site membership map in Route::deletemass() (#1071)

The management half is removed with them — its pages, tabs and reports read the same dropped tables, so keeping them would trade a lockout for broken pages. Core's site management UI is still being built; until it lands this leaves an install with sites enforced correctly and no page to administer them from. A visible gap, chosen over an invisible lockout.

Requires fogproject with schema >= 333 and #1067, #1069, #1071. Pair with the FOG_PLUGINS_VERSION bump to v1.6.5.