Based on the unstable branch, the article "MediaWiki:All_messages", usedfor maintaining msg values is an interesting idea, but I believe thiswould be better built as a dynamically built page, i.e. as"special:all_messages", rather than as a static page in the database.This would get around the use of external links to edit the variablesinstead of internal links. Is this done to avoid the slow operation ofresolving [[...]] at run time? The problem is that this makes the databasenon-portable between wiki sites. This causes a problem at our site because we update the database on adevelopment server and then move it to our working server. It means I haveto manually edit this page to change all the external links marked up onthat page.It may also cause problems because WikiMedia distributes the wikipediadatabase. That database also will not be portable.I notice that on the wikipedia site, the similarly sized article"Wikipedia:MediaWiki custom messages" does use internal links and seems toresolve in about the same amount of time.We plan to actually change the variable '$wgServer' at run time. We wantto present the server address differently if the user links to our sitevia our VPN intranet versus coming in through an external URL via theInternet. So, we rather not have the server domain defined in thedatabase, but always dynamically determined.By making All_messages a special page, you can hide it to all but sysops,developers and/or bureaucrats, who are probably the ones who should seeand maintain these variables. It also will mean that, that as a developer,if you add variables to "$wgAllMessagesEn" this page will be up to datewithout having to run an install procedure.I also notice this page is built from the variable '$wgAllMessagesEn'. Ifthis were built as a 'special' page, it could build using the language thesite actually represents.Nick Pisarro