I upgraded a test instance of our 1.3.x mediawiki via the command line and almost everything worked perfectly. Thanks very much for making this such a painless process!
One of my users makes use of this javascript/css extension to monobook and it ceases to work after the 1.4 upgrade:
http://meta.wikimedia.org/wiki/User_Styles/bottom_tabs
Is it simply that the HTML has changed and the getElementById calls point to non-existant elements now, or did something else change?
advTHANKSance, Sam
On Fri, Apr 22, 2005 at 09:16:42AM -0400, Sam Rowe wrote: # I upgraded a test instance of our 1.3.x mediawiki via the command # line and almost everything worked perfectly. Thanks very much for # making this such a painless process! # # One of my users makes use of this javascript/css extension to monobook # and it ceases to work after the 1.4 upgrade: # # http://meta.wikimedia.org/wiki/User_Styles/bottom_tabs # # Is it simply that the HTML has changed and the getElementById calls # point to non-existant elements now, or did something else change?
Is this the problem?
@import "/wiki/index.php?title=-&action=raw&gen=css";
Shouldn't there be a username in place of the - ?
What have I broken?
-Sam
On 4/22/05, Sam Rowe mediawiki@samrowe.com wrote:
On Fri, Apr 22, 2005 at 09:16:42AM -0400, Sam Rowe wrote: # I upgraded a test instance of our 1.3.x mediawiki via the command # line and almost everything worked perfectly. Thanks very much for # making this such a painless process! # # One of my users makes use of this javascript/css extension to monobook # and it ceases to work after the 1.4 upgrade: # # http://meta.wikimedia.org/wiki/User_Styles/bottom_tabs # # Is it simply that the HTML has changed and the getElementById calls # point to non-existant elements now, or did something else change?
Is this the problem?
@import "/wiki/index.php?title=-&action=raw&gen=css";
Shouldn't there be a username in place of the - ?
What have I broken?
-Sam
Edit the settings.php file thingy and go to $wgEnableUserStyles (something like that) and turn it on. It's default off because of some possible security flaw.
-- Tom
In 1.4.1, user CSS is disabled by default.
On 4/22/05, Sam Rowe mediawiki@samrowe.com wrote:
On Fri, Apr 22, 2005 at 09:16:42AM -0400, Sam Rowe wrote: # I upgraded a test instance of our 1.3.x mediawiki via the command # line and almost everything worked perfectly. Thanks very much for # making this such a painless process! # # One of my users makes use of this javascript/css extension to monobook # and it ceases to work after the 1.4 upgrade: # # http://meta.wikimedia.org/wiki/User_Styles/bottom_tabs # # Is it simply that the HTML has changed and the getElementById calls # point to non-existant elements now, or did something else change?
Is this the problem?
@import "/wiki/index.php?title=-&action=raw&gen=css";
Shouldn't there be a username in place of the - ?
No, that's standard.
What have I broken?
Are the tabs still at the top, but the body is positioned like it wasn't? Is there any difference? What do you see instead? Is this on Wikipedia, or your own wiki? is it public?
-- Jamie ------------------------------------------------------------------- http://endeavour.zapto.org/astro73/ Thank you to JosephM for inviting me to Gmail! Have lots of invites. Gmail now has 2GB.
On Fri, Apr 22, 2005 at 03:19:03PM -0400, Jamie Bliss wrote: # Are the tabs still at the top, but the body is positioned like it # wasn't? Is there any difference? What do you see instead? Is this on # Wikipedia, or your own wiki? is it public?
The tabs are still at the top. The page renders as default.
I think all user CSS and JS sub-pages are broken.
-Sam
On 4/22/05, Sam Rowe mediawiki@samrowe.com wrote:
On Fri, Apr 22, 2005 at 03:19:03PM -0400, Jamie Bliss wrote: # Are the tabs still at the top, but the body is positioned like it # wasn't? Is there any difference? What do you see instead? Is this on # Wikipedia, or your own wiki? is it public?
The tabs are still at the top. The page renders as default.
I think all user CSS and JS sub-pages are broken.
As mentioned previously by Jamie Bliss: All user CSS and JS sub-pages are OFF by default in 1.4 as a security measure. From the 1.4.0 release notes: http://sourceforge.net/project/shownotes.php?release_id=314389
This fix was made in 1.4 beta 6: * Per-user CSS and JavaScript subpage customizations now disabled by default. They can be re-enabled via $wgAllowUserJs and $wgAllowUserCss.
You must edit your Settings.php to allow these. -tom
Sam Rowe wrote:
On Fri, Apr 22, 2005 at 03:19:03PM -0400, Jamie Bliss wrote: # Are the tabs still at the top, but the body is positioned like it # wasn't? Is there any difference? What do you see instead? Is this on # Wikipedia, or your own wiki? is it public?
The tabs are still at the top. The page renders as default.
I think all user CSS and JS sub-pages are broken.
Sam, in the release notes you'll find:
As of 1.3.10/1.4beta6, per-user customized CSS and JavaScript is disabled by default as a general precaution. Sites which want this ability may set $wgAllowUserCss and $wgAllowUserJs in LocalSettings.php.
Have you turned user CSS/JS on?
-- brion vibber (brion @ pobox.com)
On Fri, Apr 22, 2005 at 01:29:05PM -0700, Brion Vibber wrote: # Sam Rowe wrote: # >On Fri, Apr 22, 2005 at 03:19:03PM -0400, Jamie Bliss wrote: # ># Are the tabs still at the top, but the body is positioned like it # ># wasn't? Is there any difference? What do you see instead? Is this on # ># Wikipedia, or your own wiki? is it public? # > # >The tabs are still at the top. The page renders as default. # > # >I think all user CSS and JS sub-pages are broken. # # Sam, in the release notes you'll find: # # As of 1.3.10/1.4beta6, per-user customized CSS and JavaScript is # disabled by default as a general precaution. Sites which want this # ability may set $wgAllowUserCss and $wgAllowUserJs in # LocalSettings.php. # # Have you turned user CSS/JS on?
That was it. I didn't read that deeply into the RELEASE-NOTES document. Thanks for the help!
mediawiki-l@lists.wikimedia.org