On Tuesday, 15th August 2006 at 09:41:30 (GMT +0300), Rotem Liss wrote: I have found this "web interface" for modifying things to be extremely unreliable. As an illustration (which was already posted here before), take a look at our wiki's MediaWiki:Sidebar: http://vincentdepaul.sk/skola/MediaWiki:Sidebar It does not correspond to our sidebar *at all*, even after you switch to the MonoBook skin. The only way we could modify the Sidebar to our liking was to edit the code directly (in Messages.php). Still, we have failed to find a way to insert <hr>, or horizontal lines, into our Sidebar. The Sidebar currently looks messy and disorganized with so many links of various kinds in it. Finding a way to insert horizontal rulers in our Sidebar is currently one of our priorities. There seems to be no easy way to achieve this... -- Yours, Alex. [processed by "The Bat!", Version 3.80.06] (MediaWiki: 1.6.8 / PHP: 4.4.1 (cgi) / MySQL: 4.1.19-standard)

On Tuesday, 15th August 2006 at 10:03:46 (GMT +0300), Rotem Liss wrote: Thank you for the pointer. However, that's what seems very difficult to achieve: creating another distinct group in the sidebar. It seems no matter what you do, the links in that second group would simply be added as new lines in the navigation bar, and there would be nothing left for the skin to interpret. For example, even if we edit our MediaWiki:Sidebar file like this: http://vincentdepaul.sk/skola/MediaWiki:Sidebar and enable $wgUseDatabaseMessages, the resulting two groups of links appear jointly as one navigation bar, both in the MonoBook and Classic skins, with nothing but simple <br> separating them in the HTML output. Inserting <hr> in MediaWiki:Sidebar has no effect, either, even when $wgUseDatabaseMessages is enabled. So how can you create another group in the sidebar, or split it to several groups? Yes... I switched if off because I was basically re-writing all translated messages and the only efficient way to do that seems to be to use a plain-text editor and FTP upload of the MessagesXX.php file. If for every modification in a translation string, you'd first have to navigate to the above webpage, then locate the string, then click through to its page, then click on Edit, then Save... it could be very time-consuming. Also, the following note in DefaultSettings.php seemed scary: # Translation using MediaWiki: namespace # This will increase load times by 25-60% unless memcached is installed # Interface messages will be loaded from the database. It seemed safer to go with $wgUseDatabaseMessages = false... -- Yours, Alex. [processed by "The Bat!", Version 3.80.06] (MediaWiki: 1.6.8 / PHP: 4.4.1 (cgi) / MySQL: 4.1.19-standard) http://vincentdepaul.sk/skola