ICT:FinalConfig-Clutter and protection - Revision history

Mngr at 17:27, 13 February 2026

2026-02-13T17:27:44Z

Show changes

Mngr at 17:22, 13 February 2026

2026-02-13T17:22:15Z

Show changes

Mngr at 16:31, 13 February 2026

2026-02-13T16:31:36Z

Show changes

Mngr at 16:20, 13 February 2026

2026-02-13T16:20:27Z

← Older revision		Revision as of 16:20, 13 February 2026
Line 222:		Line 222:
	This configuration went to preliminary tests demonstrated satisfaction: no possible links in and around the pages Anonymous and Users should have access to. Of course if one knows the MediaWiki structure and how to access particular pages he or she might view configuration files. Trying to avoid this was very problematic and tries to do so were abandoned.		This configuration went to preliminary tests demonstrated satisfaction: no possible links in and around the pages Anonymous and Users should have access to. Of course if one knows the MediaWiki structure and how to access particular pages he or she might view configuration files. Trying to avoid this was very problematic and tries to do so were abandoned.

	As we go along with defining more pages in Dashboard, we will experiment if the actual situation is acceptable or not. This means that this configuration is certainly not final.		As we go along with defining more pages in Dashboard, we will experiment if the actual situation is acceptable or not. This means that this configuration is certainly not final. For example, the top bar is gone in the Dashboard namespace for users, but is not gone for anonymous users in the Main namespace. This should certainly be possible, but will be finetuned later.

Mngr at 16:08, 13 February 2026

2026-02-13T16:08:22Z

← Older revision		Revision as of 16:08, 13 February 2026
Line 220:		Line 220:
	= Testing =		= Testing =

	This configuration ~~was tested and~~ demonstrated satisfaction.		This configuration went to preliminary tests demonstrated satisfaction: no possible links in and around the pages Anonymous and Users should have access to. Of course if one knows the MediaWiki structure and how to access particular pages he or she might view configuration files. Trying to avoid this was very problematic and tries to do so were abandoned.
	~~However, we should see~~ if ~~all protection in LocalSystems~~.~~php makes sense~~ and ~~does not forbit too much~~.
	~~This needs to be discovered as~~ we go along.		As we go along with defining more pages in Dashboard, we will experiment if the actual situation is acceptable or not. This means that this configuration is certainly not final.

Mngr at 15:55, 13 February 2026

2026-02-13T15:55:26Z

← Older revision		Revision as of 15:55, 13 February 2026
Line 1:		Line 1:
	= Final Configuration ~~concerning~~ general clutter reduction and page protection =		= Final Configuration: general clutter reduction and page protection =
	Document revison: {{#time:Y-m-d\|{{REVISIONTIMESTAMP}}}} by {{REVISIONUSER}}		Document revison: {{#time:Y-m-d\|{{REVISIONTIMESTAMP}}}} by {{REVISIONUSER}}

	The project is using a lot of namespaces, both system default ones and proprietary ones.		The project is using a lot of namespaces, both system default ones and proprietary ones. Although the general default philosophy of MediaWiki is to be as open as possible, we go for a as closed as possible scenario.
	Although the general default philosophy of MediaWiki is to be as open as possible, we go for a as closed as possible scenario.
	This needs a lot a configuration and during 3 days of struggling with this configuration it was observed that it is not fully possible with too much extra lines of code to deal with this ending up in a stable and predictable system.		This needs a lot a configuration and during 3 days of struggling with this configuration it was observed that it is not fully possible with too much extra lines of code to deal with this ending up in a stable and predictable system.
	The historical heritage project as intended to be used by senior people mostly older than 70 and have historical reflexes more than IT reflexes.		The historical heritage project as intended to be used by senior people mostly older than 70 and have historical reflexes more than IT reflexes.
	A very first ~~requirment~~ is the use of DARK MODE and for now this is only present in an easy way in the vector-2022 skin. However this skin is rather complex so we learned the lesson the hard way not to use too much private css. An experiment to use the more simpler Minerva skin for all or a number of namespaces was not successfull due to the lack of Dark mode.		A very first requirement is the use of DARK MODE and for now this is only present in an easy way in the vector-2022 skin. However this skin is rather complex so we learned the lesson the hard way not to use too much private css. An experiment to use the more simpler Minerva skin for all or a number of namespaces was not successfull due to the lack of Dark mode.
	This finally means that we ended up in extra configuration for vector-2022 in constant dark mode with clutter reduction and protection ~~realised~~ in LocalSystems.php and some elementary css files.		This finally means that we ended up in extra configuration for vector-2022 in constant dark mode with clutter reduction and protection realized in LocalSystems.php and some elementary css files.

	The idea is the following:		The idea is the following:
Line 13:		Line 12:
	# Anonymous users should see the final public documents from the reserach effort, without any MediaWiki clutter.		# Anonymous users should see the final public documents from the reserach effort, without any MediaWiki clutter.
	# Sysop of course should be capable of dealing with the system as a normal sysop		# Sysop of course should be capable of dealing with the system as a normal sysop
	# The users = senior historians, should only have access to		# The (only) users = senior historians, should only have access to
	## Dashboard: namespace for introducing data		## Dashboard: namespace for introducing data - workflow and help subpages are also foreseen here.
	## Research: namespace for creating ~~and~~ editing and reviewing publication pages coming out of the research These, once validated and accepted by the users = Costa Sano ~~clubmembers~~, should then be copied to the Main namespace for public access.		## Research: namespace for creating, editing and reviewing publication pages coming out of the research These, once validated and accepted by the users (Costa Sano club members), should then be copied to the (Main) namespace for public access.
			## Each data entity has its own namespace with the pages concerning the data of that entity NOT accessible by users. Data input and editing is only accessible via the Dashboard.
			## Remark: all access to the data goes through the PageForms extension. Forbidding direct access to data has no influence on the PageForms access.

	This ~~means: the~~ user workflow is		This ens up in a user workflow:

	# Introducing and documenting media data via the Dashboard namespace		# Introducing and documenting media data via the Dashboard namespace
Line 48:		Line 49:

	= Protection =		= Protection =
	~~Protection settings are realised in the following way.~~		What is documented by MediaWiki as of using the following approach:

	What is documented by MediaWiki as of using the following approach:

	# forbid everything		# forbid everything
	# and ~~the~~ allow specific function and actions (with Lockdown)		# and then allow specific function and actions (with Lockdown)

	gives no result at all, because this is against the spirit of what Lockdown is supposed to do.		gives no result at all, because this is against the spirit of what Lockdown is supposed to do.

Mngr at 15:42, 13 February 2026

2026-02-13T15:42:23Z

Show changes

Mngr at 15:23, 13 February 2026

2026-02-13T15:23:42Z

← Older revision		Revision as of 15:23, 13 February 2026
Line 60:		Line 60:

	LocalSystems.php snippet		LocalSystems.php snippet
			<pre>

Mngr at 15:19, 13 February 2026

2026-02-13T15:19:36Z

← Older revision		Revision as of 15:19, 13 February 2026
Line 48:		Line 48:

	= Protection =		= Protection =
	Protection settings are realised in the following way. ~~What is documented by MediaWiki as of using the following approach:~~		Protection settings are realised in the following way.
	~~forbid everything~~
	~~and the allow specific function and actions (with Lockdown)~~

	~~Gives~~ no result at all, because this is against the spirit of what Lockdown is supposed to do.		What is documented by MediaWiki as of using the following approach:

			# forbid everything
			# and the allow specific function and actions (with Lockdown)

			gives no result at all, because this is against the spirit of what Lockdown is supposed to do.

			The adopted solution is as follows:

			LocalSystems.php snippet

Mngr at 15:17, 13 February 2026

2026-02-13T15:17:14Z

← Older revision		Revision as of 15:17, 13 February 2026
Line 23:		Line 23:

	There are no other users in the system than the onces described above.		There are no other users in the system than the onces described above.

			== Configuring the correct skin ==

			LocalSystems.php snippet
			<pre>
			# =================================================
			# SKIN & INTERFACE
			# =================================================
			# --- RESTORE VECTOR 2022 ---
			wfLoadSkin( 'Vector' );
			$wgDefaultSkin = "vector-2022";

			# --- ENABLE NATIVE DARK MODE (For Vector 2022) ---
			# This unlocks the "Appearance" menu for users without manual CSS hacks.
			$wgVectorNightMode = [
			'beta' => true,
			'logged_in' => true,
			'logged_out' => true,
			];

			# --- OPTIONAL: Force 'Dark' as the default for all users ---
			$wgDefaultUserOptions['vector-theme'] = 'night';
			</pre>

			= Protection =
			Protection settings are realised in the following way. What is documented by MediaWiki as of using the following approach:
			forbid everything
			and the allow specific function and actions (with Lockdown)

			Gives no result at all, because this is against the spirit of what Lockdown is supposed to do.