I just upgraded the OpenOffice.org Wiki from MW 1.11.0 to MW 1.13.3, and I'm having a few minor issues. I'm hoping someone here can provide some insight for me....
- The sub-page breadcrumbs are "missing". This Wiki makes fairly heavy use of Sub-pages, and the breadcrumbs that we had in 1.11.0 we quite nice. I can't figure out if this is an option we enabled in 1.11.0 or if it's just something that has changed since 1.11.0. I have set $wgNamespacesWithSubpages[NS_MAIN] = true; in LocalSettings.php Is this only possible now through an extension? Or is it a setting thing?
- The extension LabeledSectionTransclusion no longer works. I have updated to the latest Trunk version, and also tried the download from the SVN that is tagged for 1.13.x. The extension is enabled, and shows in the Special:Version page, yet calls to the LST extension no longer work. Is anyone else using this extension? Is it known to work (or not work) with 1.13.3? An example of the LST where it should be working is here: http://wiki.services.openoffice.org/wiki/Documentation The headings Administration Guide, BASIC Programmers Guide and Developers Guide should have the book Table of Contents below each heading - inserted via the LST functionality.
C.
ccornell - OpenOffice.org skrev:
I just upgraded the OpenOffice.org Wiki from MW 1.11.0 to MW 1.13.3, [...]
- The sub-page breadcrumbs are "missing". ... since 1.11.0.
Should work. Have you tried disabling other extensions one by one to see if any of them are intrefering with the parser?
I have set $wgNamespacesWithSubpages[NS_MAIN] = true; in LocalSettings.php
Should work.
Impressing MW site btw. You might want some of your expert users to be able to switch to a RILPoint skin, no? http://wiki.rilnet.com/wiki/Main_Page
:)
// Rolf Lampa
- The extension LabeledSectionTransclusion no longer works. I have
updated to the latest Trunk version, and also tried the download from the SVN that is tagged for 1.13.x. The extension is enabled, and shows in the Special:Version page, yet calls to the LST extension no longer work. Is anyone else using this extension? Is it known to work (or not work) with 1.13.3? An example of the LST where it should be working is here: http://wiki.services.openoffice.org/wiki/Documentation The headings Administration Guide, BASIC Programmers Guide and Developers Guide should have the book Table of Contents below each heading - inserted via the LST functionality.
C.
I just upgraded the OpenOffice.org Wiki from MW 1.11.0 to MW 1.13.3, [...]
- The sub-page breadcrumbs are "missing". ... since 1.11.0.
Should work. Have you tried disabling other extensions one by one to see if any of them are intrefering with the parser?
Yes. I've had them all disabled, and then all enabled.. disabled one-by-one etc. I will have a go at it again though in the next day or so. It is possible that something is interfering... what though... that is the hard answer to find.
I have set $wgNamespacesWithSubpages[NS_MAIN] = true; in LocalSettings.php
Should work.
I thought so too :-)
Impressing MW site btw. You might want some of your expert users to be able to switch to a RILPoint skin, no? http://wiki.rilnet.com/wiki/Main_Page
:)
Interesting skin... looks very WindowsXP-like though... like th file manager I think (not sure since I haven't used Windows in many years.
The MW skin we are using is a modification of the MonoBook skin - almost 100% CSS changes (ie it's still MonoBook underneath).
C.
ccornell - OpenOffice.org skrev:
[...]
Impressing MW site btw. You might want some of your expert users to be able to switch to a RILPoint skin, no? http://wiki.rilnet.com/wiki/Main_Page
:)
Interesting skin... looks very WindowsXP-like though... like th file manager I think (not sure since I haven't used Windows in many years.
The RILPoint skin is mimicking the MS SharePoint skin.
The MW skin we are using is a modification of the MonoBook skin - almost 100% CSS changes (ie it's still MonoBook underneath).
Everything visible in the RILPoint skin is new from scratch. There's also a new rilpoint.php (because it's an essential part of the integration with Drupal), where all the page layout stuff essentially is a "merge" with/from Drupal's page layout. This was done in order to integrate the two.
The skins are "physically" separate though.
At last the overall look and feel is intentionally mimicking the look and feel of MS SharePoint (where the underlaying functionality on the pages are intersecting). (some compare Drupal with SharePoint although they're not fully comparable).
== Office feeling at work ==
The idea with this skin is to give more of an "in-house office" feeling (as opposed to a being _lost_out_there-feeling) when such a feeling is desired (mostly for such work which is traditionally done "in-house").
You get the idea. :-)
Regards,
// Rolf Lampa
== Office feeling at work ==
The idea with this skin is to give more of an "in-house office" feeling (as opposed to a being _lost_out_there-feeling) when such a feeling is desired (mostly for such work which is traditionally done "in-house").
You get the idea. :-)
I've never seen MS Sharepoint... never will either since my work environment is Linux and Solaris.
A large percentage of the end users of OpenOffice.org are not using Windows nor do they want to. Guessing here, but providing a Wiki skin that mimics a major app of an OS vendor that is not viewed with much appreciation or admiration is not going to win me any points.
C.
Clayton wrote:
== Office feeling at work ==
The idea with this skin is to give more of an "in-house office" feeling (as opposed to a being _lost_out_there-feeling) when such a feeling is desired (mostly for such work which is traditionally done "in-house").
You get the idea. :-)
I've never seen MS Sharepoint... never will either since my work environment is Linux and Solaris.
A large percentage of the end users of OpenOffice.org are not using Windows nor do they want to. Guessing here, but providing a Wiki skin that mimics a major app of an OS vendor that is not viewed with much appreciation or admiration is not going to win me any points
Well, as said, if *some* expert users would want to have a more office like feeling at work.
But for MS users, that is, potential OO users the skin makes sense since the look and feel one is used to may helps some people to feel at home.
Which is the idea. The Drupal skin was originally designed for use on non-public internal company sites. Well, now it has a buddy in the Mediawiki skin.
It wasn't meant to offend non-users of "other major OS vendors" though... :)
Regards,
// Rolf Lampa
You have done a good work on the skin. However, I find it lacks an accompaning license. The terms at http://www.rilnet.com/skins/commercial-version also make it more confusing, as it seems to be unfree. Still, as you're linking against MediaWiki (and even derivating code from it), it should be GPL. You can still sell or provide it for free to whoever you want, but the lack of GPL notice on the copies is in itself a GPL violation.
Platonides skrev:
You have done a good work on the skin.
Thanks, I'll forward this to my son who created the skin.
However, I find it lacks an accompaning license.
Oops.
The terms at http://www.rilnet.com/skins/commercial-version also make it more confusing, as it seems to be unfree.
It's very free. And it's free to steal. :)
Registering is only for reason of giving the greedy a bad feeling when used in incredibly profitable commercial businesses or institutions with an incredibly fat budget. :)
Still, as you're linking against MediaWiki (and even derivating code from it),
Hm, forgot that.
it should be GPL. You can still sell or provide it for free to whoever you want, but the lack of GPL notice on the copies is in itself a GPL violation.
No problem with that. We'll fix that, no problem. Thank you for reminding!
Regards,
// Rolf Lampa
mediawiki-l@lists.wikimedia.org