-----BEGIN PGP SIGNED MESSAGE-----
Moin,
i just updated an 1.3.x installation to v1.4 and run into a couple issues:
* my <graph> extension (see http://bloodgate.com/perl/graph/) stopped working. It turns out that I had the "include(..)" line at the top of Localsettings, but for v1.4 some of the settings (defaulst?) are nec. to come _before_ including the extension. That took a while to figure out because there were no errors/warnings... * I did add an extra menu point in the toolbox in "templates/xhtml_skin.php" (or whatever it was called). It turns out now that the menu is generated in Monobook so I had to hack it in there (which also probably means my extra menu point only shows up when the user uses Monobook :/ * I had some additional buttons on the edit form, these were gone and I had to re-add them, but the file location changed, they are now in "includes/EditPage.php" (I think) instead of "includes/somefile". * if you unpack v1.4 over v1.3, you have a couple unused files lying around. I haven't made an exact list, but it seems at least "templates/" and "stylesheets/images" are now no longer nec.
It would have been usefull for me to have a more detailed UPGRADE file which mentions some of these issues, so maybe this info can be incorporated by someone :)
Hope this is usefull for someone,
Tels
PS: Is somebody working on a project to make the Mediawiki interface more easily customizable, e.g. removing the logo, adding/renaming menu entries etc by editing a local settings file or even via GUI? The current way in either changing the equivalent of "Special::AllMessages" or hacking the source is not very nice and it breaks with each revision of Mediawiki again - causing me work on updates :)
- -- Signed on Wed Mar 23 17:40:22 2005 with key 0x93B84C15. Visit my photo gallery at http://bloodgate.com/photos/ PGP key on http://bloodgate.com/tels.asc or per email.
"We have problems like this all of the time," Kirk said, trying to reassure me. "Sometimes its really hard to get things burning." -- http://tinyurl.com/qmg5
On Wed, Mar 23, 2005 at 05:51:19PM +0100, Tels wrote:
PS: Is somebody working on a project to make the Mediawiki interface more easily customizable, e.g. removing the logo, adding/renaming menu entries etc by editing a local settings file or even via GUI? The current way in either changing the equivalent of "Special::AllMessages" or hacking the source is not very nice and it breaks with each revision of Mediawiki again - causing me work on updates :)
I think I will do something like that for my site... Because I'm greatly disappointed by the way things are done, but what disappoints me more is that there is _no_ better alternative.
In 1.4.0, as far as I can see, lots of work was done to make customization possible to the maximum extent. Yet I see another couple of shortcomings: I have enabled editing user CSS/JS, and it doesn't work at all (preview shows garbled stuff -- it is based on static version of CSS, and not, say, Mediawiki:Monobook.css (which is used in rendering the site), and after saving there is no effect). Moreover, I have removed my user CSS and cannot get rid of it... It appears from nowhere. Adding new stuff does not work, either. This is both in 1.3.11 and 1.4.0.
If there is another "magic variable" besides $wgAllowUserCSS, it must be documented. Otherwise it is a pain to use.
Jaroslaw Fedevych (UALUG wrote:
I have enabled editing user CSS/JS, and it doesn't work at all (preview shows garbled stuff -- it is based on static version of CSS, and not, say, Mediawiki:Monobook.css (which is used in rendering the site), and after saving there is no effect). Moreover, I have removed my user CSS and cannot get rid of it... It appears from nowhere. Adding new stuff does not work, either. This is both in 1.3.11 and 1.4.0.
Cleared browser cache?
-- brion vibber (brion @ pobox.com)
On Wed, Mar 23, 2005 at 01:19:43PM -0800, Brion Vibber wrote:
Cleared browser cache?
-- brion vibber (brion @ pobox.com)
Of course I did. More than that: I've tried to load it up on a PC from which I have never logged in before :) Still the same. I have no slightest idea where does it resurrect from.
On Thu, 24 Mar 2005 00:40:35 +0200, Jaroslaw Fedevych (UALUG wrote:
Of course I did. More than that: I've tried to load it up on a PC from which I have never logged in before :) Still the same. I have no slightest idea where does it resurrect from.
Wild guess: object cache? That was the culprit when I kept getting old versions served on the RecentChanges feed. Turns out we only keep _one_ timekey for _two_ feeds, so if an edit happens and the RSS cache gets updated, the Atom version won't be (and vice versa).
On a busy WP:en you wouldn't notice that, but on Wikis with less traffic it may take a day for the latest edit to turn up in your feed.
The object cache is a blob in the database, so it's really a perfect hiding place. If the files are gone and the browser cache is empty, there aren't that many other options. I didn't take a closer look at the code for the User CSS stuff, though.
Roger
Roger Luethi wrote:
On Thu, 24 Mar 2005 00:40:35 +0200, Jaroslaw Fedevych (UALUG wrote:
Of course I did. More than that: I've tried to load it up on a PC from which I have never logged in before :) Still the same. I have no slightest idea where does it resurrect from.
Wild guess: object cache?
User CSS (from User:<Username>/<skinname>.css) would not be stored in the object cache, so far as I can tell. However, CSS is marked with *very* aggressive client-side cache options and hitting the 'refresh' button in many browsers is not enough by itself.
MediaWiki:<Skinname>.css might be taken from the message cache stored in the objectcache table, however.
That was the culprit when I kept getting old versions served on the RecentChanges feed. Turns out we only keep _one_ timekey for _two_ feeds, so if an edit happens and the RSS cache gets updated, the Atom version won't be (and vice versa).
Did you just discover this, or did you forget to report the bug? :)
-- brion vibber (brion @ pobox.com)
On Fri, 25 Mar 2005 01:55:51 -0800, Brion Vibber wrote:
That was the culprit when I kept getting old versions served on the RecentChanges feed. Turns out we only keep _one_ timekey for _two_ feeds, so if an edit happens and the RSS cache gets updated, the Atom version won't be (and vice versa).
Did you just discover this, or did you forget to report the bug? :)
I tracked this down yesterday. It's so blindingly obvious when you look at the code that I suspected it might be intentional. For my own installation, I just cut $expire down by a few orders of magnitude.
While I was debating whether I should still report it or write a patch, along came a list message that allowed me to sneak in my discovery and off-load responsibility.
Btw, is there a deeper reason why the limit on RC entries is encoded twice in the URL (previous and current value)?
Roger
Roger Luethi wrote:
Did you just discover this, or did you forget to report the bug? :)
I tracked this down yesterday. It's so blindingly obvious when you look at the code that I suspected it might be intentional. For my own installation, I just cut $expire down by a few orders of magnitude.
While I was debating whether I should still report it or write a patch, along came a list message that allowed me to sneak in my discovery and off-load responsibility.
Please do! File a bug at http://bugzilla.wikimedia.org/ to make sure we don't forget about it.
Btw, is there a deeper reason why the limit on RC entries is encoded twice in the URL (previous and current value)?
Stupidity? Forgetfulness? :)
Looks like it's just taking the whole current URL and tacking on the additional parameter. It ought to be merging the sets of values instead.
File a bug...
-- brion vibber (brion @ pobox.com)
On Fri, 25 Mar 2005 05:29:12 -0800, Brion Vibber wrote:
Please do! File a bug at http://bugzilla.wikimedia.org/ to make sure we don't forget about it.
Bugs 1754, 1755.
Roger
Tels wrote:
It would have been usefull for me to have a more detailed UPGRADE file which mentions some of these issues, so maybe this info can be incorporated by someone :)
"If you hacked up your source code you may have to change it."? :)
PS: Is somebody working on a project to make the Mediawiki interface more easily customizable, e.g. removing the logo, adding/renaming menu entries etc by editing a local settings file or even via GUI?
There was some partial work on this at some point but I don't think it's anywhere near ready, if it works at all.
MediaWiki is primarily aimed at Wikimedia's wikis, where we're running several hundred wikis off of a single central source set with a complex centralized configuration.
-- brion vibber (brion @ pobox.com)
-----BEGIN PGP SIGNED MESSAGE-----
Moin,
On Wednesday 23 March 2005 22:21, Brion Vibber wrote:
Tels wrote:
It would have been usefull for me to have a more detailed UPGRADE file which mentions some of these issues, so maybe this info can be incorporated by someone :)
"If you hacked up your source code you may have to change it."? :)
:o)
Well, something like:
* if you changed the menu, the code for that is now in foo.php * if you changed the skin, it is now in bar.php
etc :) That would especially usefull if you unzip 1.4 over 1.3, because all the now unused files (with your changes) are still around.
I know, I know, I should send a patch instead of wishlists. :o)
PS: Is somebody working on a project to make the Mediawiki interface more easily customizable, e.g. removing the logo, adding/renaming menu entries etc by editing a local settings file or even via GUI?
There was some partial work on this at some point but I don't think it's anywhere near ready, if it works at all.
MediaWiki is primarily aimed at Wikimedia's wikis, where we're running several hundred wikis off of a single central source set with a complex centralized configuration.
I know, but MediaWiki is really usefull for (often internal) documentation colloberation projects - and for these the "standard" mediawiki menu and look&feel are not always ideal :-)
Best wishes,
Tels
- -- Signed on Wed Mar 23 23:06:59 2005 with key 0x93B84C15. Visit my photo gallery at http://bloodgate.com/photos/ PGP key on http://bloodgate.com/tels.asc or per email.
"The Palmer proposal. What ever happened to that?"
wikitech-l@lists.wikimedia.org