Extension talk:MobileFrontend/2018

If you have a feature request just request it here you'll get a much quicker reply :-) We are also around in #wikimedia-mobile if you want a quicker answer!

If you are trying to replicate behaviour you see on Wikimedia sites, please be sure to read through the configuration options before asking a question here.

Skin WPtouch don't Work with MobileFrontend and MW 1.3

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I'm currently testing the migration to the latest version 1.3 of Mediawiki. Unfortunately, the mobile presentation of the page does not work there. I use the Skin WPTouch and the extension MobileFrontend. Both latest versions (Skin WPTouch 1.1 (fbcc249) and MobileFrontend 2.0.0 (5ecc673)) However, the presentation is completely flawed and the images are missing as seen in this example:

https://picload.org/view/ddapdaiw/screenshot_20180102-183658.png.html

Normally it looks like this:

https://picload.org/view/ddapdail/screenshot_20180102-183742.png.html

Both screenshots show exactly the same page in the mobile presentation with the Skin WPtouch, only once (top) with MobileFrontend and once with complete conversion to WPtouch. So the skin itself can not be blamed, especially since Mediawiki 1.29 still works fine. Strangely enough, MobileFrontend apparently shatters the presentation. I set the default skin completely on WPtouch and disable MobileFrontend, it looks correct (second screenshot). Unfortunately, I have this skin on the desktop, which of course is wrong. Does anyone have an idea why that may be? Is there an alternative to using MobileFrontend to automatically show mobile on smartphones? Bye, Mike Shadowman30 (talk) 13:56, 4 January 2018 (UTC)

Do you even need MobileFrontend? It looks like skin WPTouch may be a responsive skin so it might not be necessary. Is the intention to have WPTouch as your mobile skin or are you hoping to have a separate Minerva skin powered mobile site? If you can manage just the one site (rather than separate mobile/desktop sites that may be preferential). If your desktop site works nicely on a mobile phone, you probably don't need a mobile site or any kind of autodetection (I'm not sure whether that's true for WPTouch skin).

If you do need the separate mobile site, I've not got enough knowledge to know exactly what the problem is but several ideas rise to my mind:

1) You need to configured a mobile skin. By default is will use Skin:MinervaNeue so make sure that's installed! If not similar things could happen.

2) Skin you are trying to use has not been made mobile compatible but it is configured as your mobile skin

If this is the case, it should be trivial to fix - https://phabricator.wikimedia.org/diffusion/SWPT/browse/master/skin.json

It looks like both skins.wptouch and skins.wptouch.js both need a 'targets': ['desktop','mobile'] entry to be loadable on mobile. You'll need to raise a bug against that skin. Jdlrobson (talk) 20:24, 8 January 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

How to show navbox by default?

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Users on my site does not care about style at all. They want navbox show as default in MobileFrontend (Skin:Minerva). What can I do to enable the display of navbox?

Navbox disappear after Upgrade MobileFrontend to 1.30 with the Mediawiki system. Deletedaccount4567435 (talk) 06:19, 20 January 2018 (UTC)

Same problem with my wiki. Finally I disabled MobileFrontend. Sniff! Jmarchn (talk) 19:04, 23 February 2018 (UTC)

Configure $wgMFRemovableClasses Jdlrobson (talk) 15:47, 9 March 2018 (UTC)

I try to solve this problem according your instructions. But nothing... the navbox not appears!.

I read Reading/Web/Projects/Performance/Inlining CSS, and try to recreate its steps in my wiki... nothing. Moreover, I believe that in this article exists repeated errors in the code:

$wgMFRemovableClasses = array(

       'stable' => array(),

       'beta' => array( '.references','.navbox' ),

} <--ERROR -> correct ");"

$wgMFLazyLoadImages = array( ...

README.md does not give any relevant information about how to use it. Jmarchn (talk) 07:43, 12 March 2018 (UTC)

Is this a public wiki? If so maybe I can help debug.

To check if

wgMFRemovableClasses is working you should check the source code of the HTML to see if the navbox is present. If it is they may be hidden by a css rule in which case you'll need to override it inside MediaWiki:Mobile.css. the current version of Minerva hides navboxes in mobile mode but displays them in desktop. Still working hard to get them presenting nicely on a mobile screen. Jdlrobson (talk) 22:58, 21 March 2018 (UTC)

Sorry!. I had not seen your answer.

It is public, a page with a navbox: http://saniwiki.cat/index.php?title=Ecografia:_ascites. (navbox from http://saniwiki.cat/index.php?title=Plantilla:Navegador_ecografia). Jmarchn (talk) 05:50, 31 March 2018 (UTC)

LazyLoading images should have nothing to do with navboxes. Jdlrobson (talk) 22:59, 21 March 2018 (UTC)

I have tried several ways to configure $wgMFRemovableClasses, but nothing would work.

I am testing an implementation which uses CSS classes to differentiate between desktop and mobile users.

To help others, I have posted my prototype Lua module and complete documentation here: Module:User:Lady G2016/NavboxMobile

Both the desktop (Module:Navbox) and mobile (Module:NavboxMobile) modules are called from the same Template:Navbox. Two templates will be seen by the browser, but only the relevant template (mobile or desktop) will be displayed.

I am using MedaWiki 1.27.4 (Long-Term Support) and MobileFrontEnd 1.0.0 (29 June 2016). Lady G2016 (talk) 01:35, 2 April 2018 (UTC)

I am using MediaWiki 1.30.0 and MobileFrontEnd 2.0.0. With your suggestions, @Lady G2016, finally navbox appears in Mobile mode. But, with listclass = hlist and with Mobile mode, a dot separator (for each item) don't appears. You can view this result in my wiki, with a template that uses navbox: http://saniwiki.cat/index.php?title=Plantilla:Navegador_ecografia Jmarchn (talk) 21:22, 3 April 2018 (UTC)

I have copied your template to my prototype (test) wiki. The dot separator does appear. The difference is the CSS style.

Extension MobileFrontend depends on the existence of MediaWiki:Mobile.css to render all CSS rules and styles. (Desktop view depends on MediaWiki:Common.css).

Your wiki has no content for MediaWiki:Mobile.css. I think this is your problem. The web browser does not display the dot separator because there is no CSS style property.

I have uploaded an example MediaWiki:Mobile.css page here. Use your wiki's MediaWiki:Common.css to create your own mobile version. I have modified the documentation in Module:User:Lady G2016/NavboxMobile to include the hlist style. See the "Implementation" section of the documentation. Lady G2016 (talk) 01:01, 4 April 2018 (UTC)

Wonderful!. It's run correctly!. Thanks you very much, @Lady G2016!. Jmarchn (talk) 09:53, 7 April 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Language list for articles

Hi! I have set up a wiki family for different languages, and linked them with interwiki links (following this: Manual:Interwiki#Interwiki links to other languages). The interwiki links work in the Desktop view, but in the mobile view there is no available language. How can I solve this? 1.64.130.216 (talk) 19:35, 20 January 2018 (UTC)

mw-collapsible is ignored

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Looks like MobileFrontend ignores class mw-collapsible. Is there a solution for it?

Example of issue: http://playground.sysadminwiki.ru/o/Mobile

MediaWiki: 1.27.1, MobileFrontend: 1.0.0 (717861c) Pavel Malakhov (talk) 05:26, 15 March 2018 (UTC)

Some unsuccessful attempts I've made to solve the problem:

1. Readme.md have options for collapsable sections only:
   • $wgMFNamespacesWithoutCollapsibleSections
   • $wgMFCollapseSectionsByDefault
2. Copy MediaWiki:Common.js to MediaWiki:Mobile.js and MediaWiki:Common.css to MediaWiki:Mobile.css
3. Copy jquery.makeCollapsible.js to MediaWiki:Mobile.js

Does anybody have something to suggest? How to make class mw-collapsible work in MobileFrontend? Pavel Malakhov (talk) 04:08, 9 April 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

can't use media viewer with mobilefrontend extensions in mobile pages

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

must be confliction. is there any help about it?

jjw9301@gmail.com 210.99.172.101 (talk) 03:52, 17 March 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Collapsing section heading for H3, H4, H5 and H6

It is not possible to collapse h3,h4,h5 and h6 at current time.

I want to collapse by default not only H2 sections ($collapseSectionsByDefault = true;) but also H3, H4, H5 and H6 sections.

This function seems to exist, I've found up these lines line 240 of extensions/MobileFrontend/ressources/mobile.toggle/toggle.js (see here):

// Also allow .section-heading if some extensions like Wikibase
// want to toggle other headlines than direct descendants of $container.
$firstHeading = $container.find( '> h1,> h2,> h3,> h4,> h5,> h6,.section-heading' ).eq( 0 );
tagName = $firstHeading.prop( 'tagName' ) || 'H1';

How to toggle other headlines than H2 in MobileFrontend 1.30 or 1.31 (the code is the same)?

Thank you in advance! Manu.wikidebats (talk) 08:43, 15 April 2018 (UTC)

This is not possible in MobileFrontend right now. Jdlrobson (talk) 17:32, 24 August 2018 (UTC)

It is actually possible by using this code in extensions/MobileFrontend/resources/mobile.toggle/toggle.js (for Mediawiki 1.31):

( function ( M, $ ) {

   var browser = M.require( 'mobile.startup/Browser' ).getSingleton(),

       escapeHash = M.require( 'mobile.startup/util' ).escapeHash,

       arrowOptions = {

           name: 'arrow',

           additionalClassNames: 'indicator'

       },

       Icon = M.require( 'mobile.startup/Icon' );

   /**

    * A class for enabling toggling

    *

    * @class

    * @extends OO.EventEmitter

    */

   function Toggler() {

       OO.EventEmitter.call( this );

       this._enable.apply( this, arguments );

   }

   OO.mixinClass( Toggler, OO.EventEmitter );

   /**

    * Using the settings module looks at what sections were previously expanded on

    * existing page.

    *

    * @method

    * @param {Page} page

    * @return {Object} representing open sections

    * @ignore

    */

   function getExpandedSections( page ) {

       var expandedSections = JSON.parse(

           mw.storage.get( 'expandedSections' ) || '{}'

       );

       expandedSections[page.title] = expandedSections[page.title] || {};

       return expandedSections;

   }

   /**

    * @ignore

    * @param {Object} expandedSections

    * Save expandedSections to localStorage

    */

   function saveExpandedSections( expandedSections ) {

       mw.storage.set(

           'expandedSections', JSON.stringify( expandedSections )

       );

   }

   /**

    * Given an expanded heading, store it to localStorage.

    * If the heading is collapsed, remove it from localStorage.

    *

    * @param {jQuery.Object} $heading - A heading belonging to a section

    * @param {Page} page

    * @ignore

    */

   function storeSectionToggleState( $heading, page ) {

       var headline = $heading.find( 'span' ).attr( 'id' ),

           isSectionOpen = $heading.hasClass( 'open-block' ),

           expandedSections = getExpandedSections( page );

       if ( headline ) {

           if ( isSectionOpen ) {

               expandedSections[page.title][headline] = ( new Date() ).getTime();

           } else {

               delete expandedSections[page.title][headline];

           }

           saveExpandedSections( expandedSections );

       }

   }

   /**

    * Expand sections that were previously expanded before leaving this page.

    * @param {Toggler} toggler

    * @param {jQuery.Object} $container

    * @param {Page} page

    * @ignore

    */

   function expandStoredSections( toggler, $container, page ) {

       var $sectionHeading, $headline,

           expandedSections = getExpandedSections( page ),

           $headlines = $container.find( '.section-heading span' );

       $headlines.each( function () {

           $headline = $( this );

           $sectionHeading = $headline.parents( '.section-heading' );

           // toggle only if the section is not already expanded

           if (

               expandedSections[page.title][$headline.attr( 'id' )] &&

               !$sectionHeading.hasClass( 'open-block' )

           ) {

               toggler.toggle( $sectionHeading, page );

           }

       } );

   }

   /**

    * Clean obsolete (saved more than a day ago) expanded sections from

    * localStorage.

    * @param {Page} page

    * @ignore

    */

   function cleanObsoleteStoredSections( page ) {

       var now = ( new Date() ).getTime(),

           expandedSections = getExpandedSections( page ),

           // the number of days between now and the time a setting was saved

           daysDifference;

       Object.keys( expandedSections ).forEach( function ( page ) {

           var sections = expandedSections[ page ];

           // clean the setting if it is more than a day old

           Object.keys( sections ).forEach( function ( section ) {

               var timestamp = sections[ section ];

               daysDifference = Math.floor( ( now - timestamp ) / 1000 / 60 / 60 / 24 );

               if ( daysDifference >= 1 ) {

                   delete expandedSections[page][section];

               }

           } );

       } );

       saveExpandedSections( expandedSections );

   }

   /**

    * Given a heading, toggle it and any of its children

    *

    * @param {jQuery.Object} $heading A heading belonging to a section

    * @ignore

    */

   Toggler.prototype.toggle = function ( $heading ) {

       var indicator,

           wasExpanded = $heading.is( '.open-block' ),

           page = $heading.data( 'page' ),

           sectionNumber = $heading.data( 'section-number' ),

           $content = $heading.next();

       $heading.toggleClass( 'open-block' );

       $heading.data( 'indicator' ).remove();

       /**

        * @event toggled

        */

       this.emit( 'toggled', wasExpanded, sectionNumber );

       arrowOptions.rotation = wasExpanded ? 0 : 180;

       indicator = new Icon( arrowOptions ).prependTo( $heading );

       $heading.data( 'indicator', indicator );

       /**

        * @event section-toggling Emitted before a section is being toggled

        */

       M.emit( 'before-section-toggled', {

           page: page,

           wasExpanded: wasExpanded,

           $heading: $heading,

           isReferenceSection: Boolean( $content.attr( 'data-is-reference-section' ) )

       } );

       $content

           .toggleClass( 'open-block' )

           .attr( {

               'aria-pressed': !wasExpanded,

               'aria-expanded': !wasExpanded

           } );

       /**

        * @event section-toggled Emitted after a section has been toggled

        */

       M.emit( 'section-toggled', wasExpanded, sectionNumber );

       if ( !browser.isWideScreen() ) {

           storeSectionToggleState( $heading, page );

       }

   };

   /**

    * Enables toggling via enter and space keys

    *

    * @ignore

    * @param {Toggler} toggler instance.

    * @param {jQuery.Object} $heading

    */

   function enableKeyboardActions( toggler, $heading ) {

       $heading.on( 'keypress', function ( ev ) {

           if ( ev.which === 13 || ev.which === 32 ) {

               // Only handle keypresses on the "Enter" or "Space" keys

               toggler.toggle( $( this ) );

           }

       } ).find( 'a' ).on( 'keypress mouseup', function ( ev ) {

           ev.stopPropagation();

       } );

   }

   /**

    * Reveals an element and its parent section as identified by it's id

    *

    * @ignore

    * @param {string} selector A css selector that identifies a single element

    * @param {Object} $container jQuery element to search in

    */

   Toggler.prototype.reveal = function ( selector, $container ) {

       var $target, $heading;

       // jQuery will throw for hashes containing certain characters which can break toggling

       try {

           $target = $container.find( escapeHash( selector ) );

           $heading = $target.parents( '.collapsible-heading' );

           // The heading is not a section heading, check if in a content block!

           if ( !$heading.length ) {

               $heading = $target.parents( '.collapsible-block' ).prev( '.collapsible-heading' );

           }

           if ( $heading.length && !$heading.hasClass( 'open-block' ) ) {

               this.toggle( $heading );

           }

           if ( $heading.length ) {

               // scroll again after opening section (opening section makes the page longer)

               window.scrollTo( 0, $target.offset().top );

           }

       } catch ( e ) {}

   };

   /**

    * Enables section toggling in a given container when wgMFCollapseSectionsByDefault

    * is enabled.

    *

    * @param {jQuery.Object} $container to apply toggling to

    * @param {string} prefix a prefix to use for the id.

    * @param {Page} [page] to allow storage of session for future visits

    * @param {Page} [isClosed] whether the element should begin closed

    * @private

    * @constructor

    */

   Toggler.prototype._enable = function ( $container, prefix, page, isClosed ) {

       var tagName, expandSections, indicator, $content,

           $firstHeading,

           self = this,

           collapseSectionsByDefault = mw.config.get( 'wgMFCollapseSectionsByDefault' );

       // Also allow .section-heading if some extensions like Wikibase

       // want to toggle other headlines than direct descendants of $container.

       $firstHeading = $container.find( '> h1,> h2,> h3,> h4,> h5,> h6,.section-heading' ).eq( 0 );

       tagName = $firstHeading.prop( 'tagName' ) || 'H1';

       if ( collapseSectionsByDefault === undefined ) {

           // Old default behavior if on cached output

           collapseSectionsByDefault = true;

       }

       expandSections = !collapseSectionsByDefault ||

           ( mw.config.get( 'wgMFExpandAllSectionsUserOption' ) && mw.storage.get( 'expandSections' ) === 'true' );

       function processHeaders ( i ) {

           var isReferenceSection,

               $heading = $( this ),

               $indicator = $heading.find( '.indicator' ),

               id = prefix + 'collapsible-block-' + i;

           // Be sure there is a div wrapping the section content.

           // Otherwise, collapsible sections for this page is not enabled.

           if ( $heading.next().is( 'div' ) ) {

               $content = $heading.next( 'div' );

               isReferenceSection = Boolean( $content.attr( 'data-is-reference-section' ) );

               $heading

                   .addClass( 'collapsible-heading ' )

                   .data( 'section-number', i )

                   .data( 'page', page )

                   .attr( {

                       tabindex: 0,

                       'aria-haspopup': 'true',

                       'aria-controls': id

                   } )

                   .on( 'click', function ( ev ) {

                       // don't toggle, if the click target was a link (a link in a section heading) - T117880

                       if ( !ev.target.href ) {

                           // prevent taps/clicks on edit button after toggling (bug 56209)

                           ev.preventDefault();

                           self.toggle( $( this ) );

                       }

                   } );

               arrowOptions.rotation = expandSections ? 180 : 0;

               indicator = new Icon( arrowOptions );

               if ( $indicator.length ) {

                   // replace the existing indicator

                   $indicator.replaceWith( indicator.$el );

               } else {

                   indicator.prependTo( $heading );

               }

               $heading.data( 'indicator', indicator.$el );

               $content

                   .addClass( 'collapsible-block' )

                   .eq( 0 )

                   .attr( {

                       // We need to give each content block a unique id as that's

                       // the only way we can tell screen readers what element we're

                       // referring to (aria-controls)

                       id: id,

                       'aria-pressed': 'false',

                       'aria-expanded': 'false'

                   } );

               enableKeyboardActions( self, $heading );

               if ( !isReferenceSection && ( !isClosed && browser.isWideScreen() || expandSections ) ) {

                   // Expand sections by default on wide screen devices or if the expand sections setting is set

                   self.toggle( $heading );

               }

           }

       }

       if ( $container.hasClass( 'mw-parser-output' ) && mw.config.get( 'wgNamespaceNumber' ) !== -1 ) {

           $container.find( 'h1,h2,h3,h4,h5,h6' ).each( function ( i ) {

               var $heading = $( this ),

                   ne1 = $heading.next(),

                   ne1tagName = ne1.prop( 'tagName' ),

                   ne2 = ne1.next(),

                   $wrapper;

               if ( $heading.nextSibling || ne1tagName !== 'DIV' || ne1.length && ne2.length && ne1tagName[0] !== 'H' && ne2.prop( 'tagName' )[0] !== 'H' ) {

                   $wrapper = $( '<div>' );

                   while( ne1.length && ne1.prop( 'tagName' )[0] !== 'H' ) {

                       if ( $heading[0].nextSibling ) {

                           $wrapper.append( $heading[0].nextSibling );

                       }

                       $wrapper.append( ne1 );

                       ne1 = $heading.next();

                   }

                   if ( $heading[0].nextSibling ) {

                       $wrapper.append( $heading[0].nextSibling );

                   }

                   $wrapper.insertAfter( $heading );

               }

           } );

           $container.find( 'h1,h2,h3,h4,h5,h6' ).each( processHeaders );

       } else {

           $container.children( tagName ).each( processHeaders );

       }

       /**

        * Checks the existing hash and toggles open any section that contains the fragment.

        *

        * @method

        * @ignore

        */

       function checkHash() {

           var hash = window.location.hash;

           if ( hash.indexOf( '#' ) === 0 ) {

               self.reveal( hash, $container );

           }

       }

       /**

        * Checks the value of wgInternalRedirectTargetUrl and reveals the collapsed

        * section that contains it if present

        *

        * @method

        * @ignore

        */

       function checkInternalRedirectAndHash() {

           var internalRedirect = mw.config.get( 'wgInternalRedirectTargetUrl' ),

               internalRedirectHash = internalRedirect ? internalRedirect.split( '#' )[1] : false;

           if ( internalRedirectHash ) {

               window.location.hash = internalRedirectHash;

               self.reveal( internalRedirectHash, $container );

           }

       }

       checkInternalRedirectAndHash();

       checkHash( this );

       // Restricted to links created by editors and thus outside our control

       // T166544 - don't do this for reference links - they will be handled elsewhere

       $container.find( 'a:not(.reference a)' ).on( 'click', function () {

           // the link might be an internal link with a hash.

           // if it is check if we need to reveal any sections.

           if ( $( this ).attr( 'href' ) !== undefined &&

               $( this ).attr( 'href' ).indexOf( '#' ) > -1

           ) {

               checkHash( this );

           }

       } );

       if ( !browser.isWideScreen() ) {

           expandStoredSections( this, $container, page );

           cleanObsoleteStoredSections( page );

       }

   };

   Toggler._getExpandedSections = getExpandedSections;

   Toggler._expandStoredSections = expandStoredSections;

   Toggler._cleanObsoleteStoredSections = cleanObsoleteStoredSections;

   M.define( 'mobile.toggle/Toggler', Toggler ); // resource-modules-disable-line

}( mw.mobileFrontend, jQuery ) ); Manu.wikidebats (talk) 10:29, 8 September 2018 (UTC)

Error after installing MobileFrontend

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

MediaWiki version 1.30.0

MobileFrontend version for MediaWiki 1.30.0- Special:ExtensionDistributor/MobileFrontend

Localsettings.php changes done -

wfLoadExtension( 'MobileFrontend' );

$wgMFAutodetectMobileView = true;

Current skin - Vector

After doing this getting the following error both on desktop and mobile when visiting the website -

MediaWiki internal error.

Original exception: [WtY8JkXDfFUAA8YuE7cAAAFb] 2018-04-17 18:25:42: Fatal exception of type "RuntimeException"

Exception caught inside exception handler.

Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information

Please help. Biologically (talk) 18:34, 17 April 2018 (UTC)

The error solved. Actually, I forgot to write the default skin class in localsettings.php ($wgMFDefaultSkinClass = "SkinMinerva";). After doing it the website is working again. Thank you everyone. Biologically (talk) 18:51, 17 April 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Error MobileFrontend/includes/MobileFrontend.hooks.php: Call to undefined method OutputPage::enableTOC()

OutputPage deprecated MediaWiki 1.30.0. COmmented out line and I'm working now but may get TOC on Mobile Pages.

Johnny JohnWunder (talk) 13:48, 30 April 2018 (UTC)

Cookie issue

Setting $wgCookieExpiration to 0 stops MobileFrontend from setting cookies to remember a user's choice to use or not use mobile view.

Instead, MobileFrontend should have set such cookies for the duration of the user's session only, instead of not at all.

Well, that is what the manual suggested. Minoa (talk) 12:46, 12 May 2018 (UTC)

Text being placed wrong in headers

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Prepping a move from 1.24 to 1.30, but MobileFrontend is giving me fits. Specifically, if I use Minerva as the default class (as we've done previously), it ends up giving me this: https://imgur.com/a/DrXNjY0

It basically looks like it's placing the header text outside of the span for no obvious reason. Anyone seen similar behavior and know how to fix it? I've tried reinstalling the MinervaNeue skin, MobileFrontend, etc., to no avail. Timeless and Vector don't share this problem, either. Balerion300 (talk) 19:23, 15 May 2018 (UTC)

Turns out that in fact the whole install is doing this, it's just Minerva in mobile that makes it obvious by setting the span to width 100%. Have posted to the general support desk. Balerion300 (talk) 12:19, 16 May 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

last edited

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

this link to article history is not very helpful. The username shown more often than not is someone who just fixed a link or a typo. Clicking on it a new user does not necessarily get in contact with someone who can easily answer questions about a given article. Why not show who created the article instead? Or show a selection of authors (like wikibu.ch does)? How about https://xtools.wmflabs.org/articleinfo-authorship/? HHill (talk) 07:38, 29 May 2018 (UTC)

Thanks for the input

You may be interested in

https://phabricator.wikimedia.org/T193993 which i think may make this more helpful. What do you think? Feel free to subscribe and comment on that ticket. your thoughts are welcomed! Jdlrobson (talk) 22:03, 26 June 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Mobile Frontend Minerva Neue - Settings page on mobile only shows "READING PREFERENCES"

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I have the latest mobile frontend and Wikimedia packages installed. 1.129.108.96 (talk) 06:04, 23 June 2018 (UTC)

I am not getting anything when I click on the settings page on minerva skin Amirfaour (talk) 06:32, 23 June 2018 (UTC)

There are currently no configurable settings.

You can enable beta mode and settings with:

$wgMFEnableBeta = true;

This is confusing so I've setup: https://phabricator.wikimedia.org/T198265 Jdlrobson (talk) 21:41, 26 June 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

don't load mobile.css

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

http://wiki.apb-r.ru/go/MediaWiki:Mobile.css

http://wiki.apb-r.ru/w/index.php?title=MainpageMobile&mobileaction=toggle_view_mobile

Please help

I think MobileFrontend does not work correctly on mediawiki 1.31 Liikaqp (talk) 16:22, 26 June 2018 (UTC)

Add mw.loader.using('mobile.site.styles') to your Mobile.js

This was broken in https://phabricator.wikimedia.org/T191596 Jdlrobson (talk) 21:45, 26 June 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

How can i change login URL in mobil version

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hi,

I use Medawiki with Discourse login system. I change login URL in desktop version.

/includes/skins/SkinTemplate.php

$login_url = [

'text' => $this->msg( $loginlink )->text(),

'href' => '/discourse.php',

//'href' => self::makeSpecialUrl( 'Userlogin', $returnto ),

'active' => $title->isSpecial( 'Userlogin' )

|| $title->isSpecial( 'CreateAccount' ) && $useCombinedLoginLink,

];

And it works. But in the mobile version i can't change login URL. How can i change that login URL? Any idea? Bekircem (talk) 09:49, 28 June 2018 (UTC)

This is not possible at time of writing. But, please feel free to submit a patch to MobileFrontend to make this configurable. Jdlrobson (talk) 17:26, 24 August 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

MobileFrontend doesn'nt change the layout on mobile

Hi folks!

I've installed the extension and (aparently) everything was ok. But when I access to the mobile version of my web it has the same layout as in desktop mode. Do I need to add something more to my LocalSettings.php?

Specs:

Producto	Versión
MediaWiki	1.30.0
PHP	5.5.9-1ubuntu4.3 (apache2handler)
MySQL	5.5.38-0ubuntu0.14.04.1

Extensión	Versión	Licencia	Descripción	Autores
MobileFrontend	2.0.0	GPL-2.0+	Interfaz móvil	Patrick Reilly, Max Semenik, Jon Robson, Arthur Richards, Brion Vibber, Juliusz Gonera, Ryan Kaldari, Florian Schmidt, Rob Moen, Sam Smith y otros

And in my LocalSettings.php:

wfLoadExtension( 'MobileFrontend' );

$wgMFAutodetectMobileView = true;

$wgMFDefaultSkinClass = 'SkinVector'; 217.125.71.90 (talk) 08:02, 2 July 2018 (UTC)

The Vector mobile skin is just the desktop version in mobile mode (so mobileonly CSS classes will show and nomobile won't). Try the MinervaNeue skin instead. Tinss (talk) 05:53, 16 August 2018 (UTC)

> The Vector mobile skin is just the desktop version in mobile mode (so mobileonly CSS classes will show and nomobile won't).

That's actually not true. nomobile classes will still be stripped in Vector mobile mode.

The Vector skin will actually behave subtly different in mobile mode. See http://en.m.wikipedia.org/wiki/Spain?useskin=vector and resize the screen.

This configuration looks correct to me. If you use a mobile device do you notice anything different between the modes?

To check mobile is installed you should look for the "Desktop link"/"Mobile link" in the footer, this will tell you things are working as expected. Jdlrobson (talk) 17:30, 24 August 2018 (UTC)

How can i add code between head tags?

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Hi,

I want to add Google Adsense ads code between head tags on mobile version. (Just mobile version, not the desktop version)

I look into minerva.mustache file but i can't reach in {{{headelement}}} tag. Any help? Bekircem (talk) 07:01, 4 July 2018 (UTC)

For desktop/mobile it's best to use a hook to add this kind of thing to the head. https://www.guyrutenberg.com/2014/10/13/displaying-google-adsense-in-mediawiki/ looks like it's probably still relevant for you. Jdlrobson (talk) 08:07, 30 July 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Mobile Version of Copyright Footer

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I edited the MediaWiki:Copyright page which shows the copyright message in the footer. The desktop skins (such as Vector) show the updated text but it still shows the default copyright message on mobile skins (such as Minerva). Does MobileFrontend use a different page for it's copyright notice? Jer Hughes (talk) 16:51, 10 July 2018 (UTC)

You can see which messages are used where by appending ?uselang=qqx to the page (or &uselang=qqx if there are other arguments). Based on that, it looks like it uses Mediawiki:Mobile-frontend-copyright Clump (talk) 17:04, 10 July 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

MediaWiki:Sitenotice Equivalent?

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Is there a MediaWiki:Sitenotice equivalent for MobileFrontend to show a message at the top of every page on mobile view? Jer Hughes (talk) 16:01, 27 July 2018 (UTC)

I think you are asking for one for the Minerva skin (default mobile skin)? MobileFrontend doesn't have much to do with site notices.

The Minerva skin has a config option $wgMinervaEnableSiteNotice which is disabled by default. Jdlrobson (talk) 08:05, 30 July 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Cannot add or create a page via search in MobileFrontEnd

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

When I search for a page that does not exist on Mobilefrontend, it does not provide me with a "redline" to create a page - just like what you would except on the desktop site of MediaWiki. How do you create a page on mobilefrontend? I am using the MinervaNeue skin. Amirfaour (talk) 09:49, 23 August 2018 (UTC)

@Amirfaour, I looked around and you're not the first person to notice this. :) It looks like this was done by design. There is a task regarding this that goes into a little more detail. CKoerner (WMF) (talk) 14:31, 23 August 2018 (UTC)

Thank you for your answer.

Where do you add:

.mw-search-createlink { display: block; }

Do you add it to MediaWiki:Mobile.css? Amirfaour (talk) 17:03, 23 August 2018 (UTC)

I added it to MediaWiki:Mobile.css however it has not fixed the problem Amirfaour (talk) 17:21, 23 August 2018 (UTC)

Hmm, I can add it to my personal CSS for Minerva and it works.[1] MediaWiki:Mobile.css is the right spot according to the documentation. I bet @Jdlrobson could tell us what's going on. :) CKoerner (WMF) (talk) 14:47, 24 August 2018 (UTC)

MediaWiki:Mobile.css is the correct place. You might want to also try appending !important to the rule.

.mw-search-createlink, .mw-search-profile-tabs { display: block !important; }

If that's not working you'll likely impacted by this bug. Jdlrobson (talk) 17:39, 24 August 2018 (UTC)

Thanks @Jdlrobson

Yes I was impacted by that bug.

Adding mw.loader.using('mobile.site.styles') to MediaWiki.Mobile.js fixed the problem. Amirfaour (talk) 02:45, 27 August 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Prevent mobile pages from being indexed

I see this, my viki pages also indexed with Mobilefrontend mobile version. It causes confusion. How i prevent mobile pages from being indexed?

Thanks. Bekircem (talk) 00:29, 2 September 2018 (UTC)

Mobile frontend minerva talk-back-to-page redlinks

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I defined a custom namespace called "WikiPCI" with the number 3001 in local settings.php.

At the bottom of pages created on that namespace, e.g. WikiPCI:About, on the mobile version of the site there are redlinks where it says Return to "name of page" page. See: http://wikipci.org/index.php?title=WikiPCI:About&mobileaction=toggle_view_mobile

When using the useland=qqx toggle it shows that the MediaWiki page its linking to is: MediaWiki:Mobile-frontend-talk-back-to-page and contains: Return to "$1" page.

http://wikipci.org/index.php?title=WikiPCI:About&uselang=qqx&mobileaction=toggle_view_mobile

When I look at the source code of the html pages I see the following:

<a href="/index.php?title=Special:Badtitle/NS3000:About&amp;action=formedit&amp;redlink=1" class="new return-link" title=":About (page does not exist)">Return to "About" page.</a></div>

Its linking to NS3000:About - why is it linking it to that page?

Thanks.

Using:

MobileFrontend: 2.1.0

ProductVersionMediaWiki1.31.0

PHP7.2.9 (cgi-fcgi)

MySQL5.6.40-84.0-log

ICU4.8.1.1 Amirfaour (talk) 12:48, 12 September 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

How to use minerva.mustache to show ads?

Can anybody show me how to place adsense ads in minerva.mustache, banners.mustache or header.mustache? 2601:601:CD80:A7E0:53B:C2F2:C434:408 (talk) 18:25, 13 September 2018 (UTC)

Major compatibility issues

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

When I use this extension, regardles of what type of mobile skin, almost all my extensions stop working correctly. I've even tried to put a simple js script in the mobilefrontend without any success.

Am I doing something wrong? I installed the extension and mediawiki, I use the latest download of them both and I made sure that wfLoadSkin is installed after the call to wfLoadExtension.

Thanks in advance! Ztiruam (talk) 15:11, 5 October 2018 (UTC)

Ztiruam (talk) 15:31, 5 October 2018 (UTC)

This incompatibility only occurs in mobile mode. If I use Minerva Neue in Desktop mode, everything works as it should... Ztiruam (talk) 16:31, 5 October 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

How do I enable resourcemodules?

Mobilefrontend disables all resourcesmodules by default. How do I enable them? Ztiruam (talk) 18:10, 7 October 2018 (UTC)

I found this tutorial: http://www.examsmyantra.com/article/135/mediawiki/enable-resource-loader-module-to-work-with-mobile-frontend-extension

Where do I place the code? Ztiruam (talk) 18:59, 7 October 2018 (UTC)

Fatal exception of type "RuntimeException" Exception caught inside exception handler.

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

MediaWiki version 1.30.0

Skin is "Vector"

After MobileFrontend successful installation in LocalSettings.php following adds were made:

wfLoadExtension( 'MobileFrontend' );

$wgMFAutodetectMobileView = true;

Result is at desktop as usual, mobile "Fatal error":

Fatal exception of type "RuntimeException"

Exception caught inside exception handler.

After reading topis here I added

$wgMFDefaultSkinClass = "SkinMinerva";

to LocalSettings.php but result is same: desktop mode is working, mobile is not working with same error.

Before installation of MF mobile mode in Vector was working as same as desktop but I wanted to improve view with MF. Please help to solve. B.Shapoval (talk) 14:56, 12 October 2018 (UTC)

@B.Shapoval, did you install skin Minerva on "/skin" directory?

see on Skin:Minerva Neue for details. আ হ ম সাকিব (talk) 15:22, 12 October 2018 (UTC)

It is working. Thank you. Vector in desktop. Minerva in Mobile. B.Shapoval (talk) 17:34, 12 October 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

How current is this extension? As in, is it really necessary if you have a skin which is built using responsive design principles?

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

Having a completely separate site seems a bit antiquated doesn't it? AslanFrench (talk) 00:51, 16 October 2018 (UTC)

If you have a fully responsive skin installed and have confirmed that it works fine in mobile and on desktop, you can probably forego this extension unless it has some feature you want. 「ディノ奴千？！」^{☎ Dinoguy1000} 04:18, 16 October 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

How do I enable extensions for mobile users?

MobileFrontend disables some kind of resource module, how do I enable extensions for mobile users? Ztiruam (talk) 09:25, 19 October 2018 (UTC)

Table of contents, table sorting, wikitable

Hey. Lovely extension this one is! I was curious, will you ever add the option to enable the table of contents for mobile view? Or maybe add it in the sidebar. Also, will it be possible, in the future, for table sorting to work? And speaking of tables, why doesn't the extension recognize the "wikitable" class? 109.103.213.222 (talk) 21:11, 23 October 2018 (UTC)

Can I use collapsible headings on desktop mode?

I love the collapsible headings, but they only show up on mobile. Can I enable it on desktop mode? Ztiruam (talk) 16:37, 25 October 2018 (UTC)

@Ztiruam , Use Minerva Skin for collapsing mode on desktop. আ হ ম সাকিব (talk) 14:22, 27 October 2018 (UTC)

How do I enable collapsing mode on desktop? The headings are non-collapsible by default in desktop mode. Ztiruam (talk) 12:07, 28 October 2018 (UTC)

Table of Contents appears everywhere on tablets

If the browser is wide enough, a TOC appears on all pages, even on the main page, and on pages without section headings. Looks like this is added by Javascript, and the criteria to determine whether a TOC should be included are completely ignored. On my main page, MF places an empty TOC at the bottom of the page. How can I disable this undesirable behavior? It ignores __NOTOC__, it ignores everything. 2A02:AB88:B2C0:EA00:9C72:1FF9:B58A:9657 (talk) 14:05, 3 November 2018 (UTC)

OK, I figured it out. The problem comes from the Minerva skin, and is already fixed on github but not included in the download served for MW 1.31. The latest development version of the skins/MinervaNeue/resources/skins.minerva.tablet.scripts/toc.js file should be used. 2A02:AB88:B2C0:EA00:D0D:7CCF:7551:C3DF (talk) 00:38, 4 November 2018 (UTC)

Is there a way to have the wiki load on mobile with all the headings expanded

Now it is loading the headings collapsed by default, and I want them to load expanded. I am also using the Minerva Neue skin. 2601:280:4200:42E6:D8FC:89DF:D9F4:6091 (talk) 03:44, 11 November 2018 (UTC)

How to change mobile's fonts?

I have been messing around with MediaWiki:Mobile.css just to change the fonts displayed and I couldn't get it to work. After every change I wiped the cache of the browser and reload the page but no luck.

Could someone provide me with a tutorial on this? Leduyquang753 (talk) 10:55, 17 November 2018 (UTC)

go to Address: wikicod.ir

sample: @Leduyquang03mediawiki:Mobile.css

Sokote zaman (talk) 08:09, 16 December 2019 (UTC)

Mobile / SkinMinerva broken on Safari with predictive keyboard turned on

I observe a severe show stopper in MobileFrontend using SkinMiverva on iOS. The iOS keyboard can be switched to "predictive" mode. In this case the virtual keyboard shows another line above the keyboard but still below the "Done" line where it displays words which the user probably has meant while writing.

When editing a Wiki page this has the sad side effect that the caret is hidden by that additional line and you can no longer see what you are typing. You can't fix this issue easily: If you manually scroll then at the next key entry / return key pressed, the textarea again repositions the caret and you again cannot see it.

I would be grateful if this could be fixed or for some pointers where to start looking (I am not familiar with this extension and do not understand it sufficiently). 217.95.165.6 (talk) 19:33, 23 November 2018 (UTC)

How can i add code between head tags?

Hi,

I want to add Google Adsense ads code between head tags on mobile version. (Just mobile version, not the desktop version)

I look into minerva.mustache file but i can't reach in {{{headelement}}} tag. Any help?

Actually i want to enable page level ads. So i need to add codes into head tags in MobileFrontEnd extension. I am already use simple Adsense ads format on my wiki.

Thanks. Bekircem (talk) 20:01, 5 December 2018 (UTC)

Timeless and Vector look GREAT except NO TOC!

I was looking at the Vector and Timeless skins and they look really nice on mobile, except the TOC shows up, blank. I don't mind the TOC being there, the sections are not collapsed like they are in the default skin. However, the TOC block is empty (says Contents and then nothing).

Is there a way to change this behavior? Titanshadow (talk) 20:52, 13 December 2018 (UTC)

There's a bug for this: https://phabricator.wikimedia.org/T182069 Prod (talk) 01:59, 14 December 2018 (UTC)

Is there some workaround ? For example hide it via MediaWiki:Mobile.css ? Olekdia (talk) 21:30, 9 January 2019 (UTC)

I have added:

#toc { display: none !important; } to MediaWiki:Mobile.js for now.

Please fix this, it is an old bug. Olekdia (talk) 21:43, 9 January 2019 (UTC)

jQuery script broken in MFview

using JQuery like $("<div></div>").prependTo() in Widgets seems broke in mobile view, script output as plaintext.

How to fix this. Mikumikuer (talk) 02:37, 14 December 2018 (UTC)

GlobalVarConfig::get: undefined option: 'ResourceLoaderLESSVars'

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I am getting the below error with 3.33 and trying to use Mobile Frontend with the following setup:

wfLoadExtension( 'MobileFrontend' );

$wgMFAutodetectMobileView = true;

$wgMFDefaultSkinClass = 'SkinVector'; // use Vector skin

^{MediaWiki internal error.}

^{Original exception: [e21caa824241ba159b043d0d] /Main_Page ConfigException from line 53 of /var/www/gwart.co.uk/mediawiki/includes/config/GlobalVarConfig.php: GlobalVarConfig::get: undefined option: 'ResourceLoaderLESSVars'}

^Backtrace:

^{#0 /var/www/gwart.co.uk/mediawiki/extensions/MobileFrontend/includes/MobileFrontend.hooks.php(707): GlobalVarConfig->get(string)}

^{#1 /var/www/gwart.co.uk/mediawiki/includes/Hooks.php(174): MobileFrontendHooks::onBeforePageDisplay(OutputPage, SkinVector)}

^{#2 /var/www/gwart.co.uk/mediawiki/includes/Hooks.php(234): Hooks::callHook(string, array, array, NULL, string)}

^{#3 /var/www/gwart.co.uk/mediawiki/includes/OutputPage.php(2711): Hooks::runWithoutAbort(string, array)}

^{#4 /var/www/gwart.co.uk/mediawiki/includes/MediaWiki.php(869): OutputPage->output(boolean)}

^{#5 /var/www/gwart.co.uk/mediawiki/includes/MediaWiki.php(881): MediaWiki->{closure}()}

^{#6 /var/www/gwart.co.uk/mediawiki/includes/MediaWiki.php(517): MediaWiki->main()}

^{#7 /var/www/gwart.co.uk/mediawiki/index.php(42): MediaWiki->run()}

^{#8 {main}}

^{Exception caught inside exception handler: [e21caa824241ba159b043d0d] /Main_Page ConfigException from line 53 of /var/www/gwart.co.uk/mediawiki/includes/config/GlobalVarConfig.php: GlobalVarConfig::get: undefined option: 'ResourceLoaderLESSVars'}

^Backtrace:

^{#0 /var/www/gwart.co.uk/mediawiki/extensions/MobileFrontend/includes/MobileFrontend.hooks.php(707): GlobalVarConfig->get(string)}

^{#1 /var/www/gwart.co.uk/mediawiki/includes/Hooks.php(174): MobileFrontendHooks::onBeforePageDisplay(OutputPage, SkinVector)}

^{#2 /var/www/gwart.co.uk/mediawiki/includes/Hooks.php(234): Hooks::callHook(string, array, array, NULL, string)}

^{#3 /var/www/gwart.co.uk/mediawiki/includes/OutputPage.php(2711): Hooks::runWithoutAbort(string, array)}

^{#4 /var/www/gwart.co.uk/mediawiki/includes/exception/MWExceptionRenderer.php(136): OutputPage->output()}

^{#5 /var/www/gwart.co.uk/mediawiki/includes/exception/MWExceptionRenderer.php(53): MWExceptionRenderer::reportHTML(ConfigException)}

^{#6 /var/www/gwart.co.uk/mediawiki/includes/exception/MWExceptionHandler.php(98): MWExceptionRenderer::output(ConfigException, integer)}

^{#7 /var/www/gwart.co.uk/mediawiki/includes/exception/MWExceptionHandler.php(172): MWExceptionHandler::report(ConfigException)}

^{#8 /var/www/gwart.co.uk/mediawiki/includes/MediaWiki.php(544): MWExceptionHandler::handleException(ConfigException)}

^{#9 /var/www/gwart.co.uk/mediawiki/index.php(42): MediaWiki->run()}

^{#10 {main}} Jamiehutber (talk) 02:46, 24 December 2018 (UTC)

"3.33" of what exactly? Malyacko (talk) 19:09, 12 January 2019 (UTC)

What is version 3.33?

Does your version of MobileFrontend match the MW version? Reedy (talk) 19:16, 12 January 2019 (UTC)

Sorry guys, my mistake. 3.33 of mediawiki. Interesting point about MFE match MW version. I will check that now. Jamiehutber (talk) 21:33, 30 January 2019 (UTC)

3.33 of mediawiki does not exist. See Download Malyacko (talk) 21:39, 30 January 2019 (UTC)

`<meta name="generator" content="MediaWiki 1.33.0-alpha"/>` I checked out the repo which contained 3.33 inside there as an alpha.

But your suggestion worked a treat, as mobileFrontend also had an version 3.33. Though I think this is buggy, being as it is also alpha.

I consider this fixed as far as the error goes.

Thanks you Jamiehutber (talk) 21:43, 30 January 2019 (UTC)

Again: There is no 3.33. 1.33 is not 3.33. Malyacko (talk) 22:00, 30 January 2019 (UTC)

Ah sir, you are indeed correct :D Thank you!

You wouldn't happen to know about galleries would you?

Category talk:Image gallery extensions Jamiehutber (talk) 22:05, 30 January 2019 (UTC)

It appears I am running version 2.1.0 of MFE:

```

"name": "MobileFrontend",

"version": "2.1.0",

``` Jamiehutber (talk) 21:35, 30 January 2019 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.

Mobile.css doesn't load

The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

---

I have the current version mediawiki-1.31.1 and the current versions of MobileFrontend + MinervaNeue. Everything works fine, but the Mobile.css doesn't load.

The page header has:

<link rel="stylesheet" href="/load.php?debug=false&amp;amp;lang=en&amp;amp;modules=mediawiki.hlist%7Cmediawiki.ui.button%2Cicon%7Cskins.minerva.base.reset%2Cstyles%7Cskins.minerva.content.styles%7Cskins.minerva.icons.images%2Cloggedin%7Cskins.minerva.loggedin.styles%7Cskins.minerva.mainPage.styles%7Cskins.minerva.tablet.styles&amp;amp;only=styles&amp;amp;skin=minerva">

<script async="" src="/load.php?debug=false&amp;amp;lang=en&amp;amp;modules=startup&amp;amp;only=scripts&amp;amp;skin=minerva&amp;amp;target=mobile"></script>

but the Mobile.css is lacking. In a former version (mw 1.26) everything worked. Gerd-Lothar Reschke (talk) 18:58, 26 December 2018 (UTC)

This has been brought up in this discussion: https://www.mediawiki.org/w/index.php?title=Extension%20talk%3AMobileFrontend/2018#c-Jdlrobson-2018-06-26T21%3A45%3A00.000Z-Liikaqp-2018-06-26T16%3A22%3A00.000Z Prod (talk) 19:57, 27 December 2018 (UTC)

You are right! I used this advice and now it works! Thanks!

(Strange that there seem to be so few people using Mobile.css.) Gerd-Lothar Reschke (talk) 21:15, 27 December 2018 (UTC)

The discussion above is closed. Please do not modify it. No further edits should be made to this discussion.