Talk:MediaWiki 1.24

From mediawiki.org
Latest comment: 8 years ago by Florianschmidtwelzow in topic update to 1.24.2

Drop down menus[edit]

We've moved to v1.24, and our former extension (drop down menus in the left nav) don't seem to be working anymore. Any clues? --Orange-quarter (talk) 06:24, 2 June 2014 (UTC)Reply

It's in the release notes, had you checked them (if yes please suggest how to make it clearer)? Copied to this page as well now. --Nemo 06:57, 2 June 2014 (UTC)Reply
Thanks Nemo ... is this the part that you mean? "(bug 44591) The dropdown actions menu (little triangle next to page tabs) in the Vector skin has gained a label that should make it more discoverable." If so, yes, I'm not sure what that means in terms of what we need to do to make the drop down menus work again? Orange-quarter (talk) 07:11, 10 June 2014 (UTC)Reply
The tabs dropdown does work. I assume you're talking of MediaWiki 1.24#Performance instead? The feature might be developed in an extension, try asking. --Nemo 08:45, 10 June 2014 (UTC)Reply
Thanks again...think we are talking about different things. Yes, tabs drop down works, but the extension that makes the dropdowns work in the left navigation bar has stopped working since upgrade. Will ask. Ta. Orange-quarter (talk) 06:19, 26 June 2014 (UTC)Reply
Maybe this could be added to an extension. For example re start the vector extension and add CollaspibleNav to it. It would allow for the website to use it without creating any thing in Mediawiki:common.css or .js. 109.151.116.0 22:45, 2 September 2014 (UTC)Reply

__NOTITLE__ does not work anymore[edit]

in 1.24 as well as 1.25

NoTitle is still an Extension, right? Then you should ask the developer, if he can look, why his extension doesn't work anymore. Maybe he can fix it without changes in core, otherwise he can request changes in core to fit his needs :) --Florianschmidtwelzow (talk) 17:24, 4 October 2014 (UTC)Reply

Skin error[edit]

So it seems with the changes made to skins in 1.24, something broke on my end when trying to update. Now when trying to load any skin, I get this:

Fatal error: Call to undefined method MonoBookTemplate::getIndicators() in /.../skins/MonoBook/MonoBookTemplate.php on line 58

Looking at MonoBookTemplate.php (or the corresponding file for other skins), $this->getInidicators() is called, but it doesn't exist. Right now this line is the only thing showing up. Am I missing something important here? Schiffy (talk) 03:44, 28 November 2014 (UTC)Reply

You should download the REL1_24 branch of Monobook in order to use it with your MediaWiki 1.24 :) getIndicators is a function added in MW1.25 development cycle (git #6f5b29ff) and isn't available in MW 1.24, but you want to use Monobook with the latest master version, which is built to work with the latest development version of MediaWiki. That can not work :) So, download the 1.24 release of Monobook and use this version, that will work. --Florianschmidtwelzow (talk) 07:04, 28 November 2014 (UTC)Reply

Leave page warning missing[edit]

I updated from 1.22.5 in the hopes of getting the drafts extension to work after a pc crash caused me some stress. Just made it worse by losing the "Leaving page warning" and then the WYSIG editor i had installed. Strangely the WYSIG worked yesterday after the install but not this morning despite not being able to recall any changes. I tried moving back to the old version by running the db update but now if i login to edit a page (thats not the mian page) i get a db error. I imagine this is somethig to do with table prefixes not being downgraded in the web updater. My primary concern is getting 1.24.1 to work with the "Leave page" warning as its otherwise to dangerous to use. Hoping the WYSIG issue is a one of fluke.

Release schedule[edit]

Any news to share on the planned 1.24.2 release? I realize that the dates are anticipated dates and not hard and fast ones, but the MediaWiki development team is usually pretty bang on with their target dates. Other than the mediawiki-announce mailing list, is there somewhere that an administrator can track pending releases? --Peculiar Investor (talk) 13:45, 29 January 2015 (UTC)Reply

I can't speak for the release engineering team, but with the MediaWiki Developer Summit wrapping up, things have been pretty chaotic. mediawiki-announce is the best way to track upcoming releases. Legoktm (talk) 17:13, 29 January 2015 (UTC)Reply
There are open security issues, which - although obviously not disclosed to the general public and not widely exploited - are considered that urgent, that they will be fixed prior to the next release. So long, these dates are not sure at all - as you e.g. saw with the February releases. --88.130.110.84 00:29, 14 March 2015 (UTC)Reply
Will there be a release next week? If not, how much notice will we be given before the release? If these security issues are significant enough that 3 maintenance releases would be missed, I'd like to be able to plan the rollout to my sites as soon as the details are available. -- Prod (talk) 15:41, 17 March 2015 (UTC)Reply
A release is scheduled for later today. --88.130.66.161 13:07, 31 March 2015 (UTC)Reply

Collapsible Content?[edit]

My collapsible content is no longer working since my upgrade. How can I get it back?

update to 1.24.2[edit]

You have to set $wgUseAjax = true; $wgEnableAPI = true; in your LocalSettings. The update script does not do that for you. Without, a lot of functions are not available any more. --[[User:Bmrberlin| Bernd M.]] (talk) 04:47, 29 April 2015 (UTC)Reply

That's the default behavior of the updater script, if you already have a LocalSettings.php, it will not create a new one :) --Florianschmidtwelzow (talk) 06:01, 29 April 2015 (UTC)Reply