my wiki have installed Extension:MobileFrontend.
i would like to show the logo in mobile version, i put value to $wgMobileFrontendLogo but nothing happens
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.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. See Terms of Use for details.
my wiki have installed Extension:MobileFrontend.
i would like to show the logo in mobile version, i put value to $wgMobileFrontendLogo but nothing happens
We installed Extension:MobileFrontend on our Mediawiki installation but the section headings do not display the down arrow in mobile view.
I am getting feedback from users that they aren't sure what to do with the headings (the obvious thing does seem to be to click on them) but having the down arrow displayed for mobile users would help fix that problem.
There seems to be no documentation as to whether this can be turned on or off.
Website: https://en.believethesign.com/
MediaWiki 1.35.5
PHP 7.4.27 (fpm-fcgi)
MySQL 5.7.36-0ubuntu0.18.04.1-log
Mobile skin: MinervaNeue
Normally this is somewhat controlled by the config parameter $wgMFCollapseSectionsByDefault
hower, be it set to true on false, section headings should display correctly on your system.
Are you able to toggle section to be displayed or collapsed?
We ended up discovering that we were missing some files on MobileFrontend. There was an entry in one of the git config files which was preventing the missing files from uploading. we removed that entry, the files suddenly appeared, and after uploading them, the expand/close arrows on headings appeared. Problem resolved.
Do you know which entry was missing ? I'm actually struggling with the same issue.
Hello, I'm using MF REL1_34 on MW 1.34. For some reason, the ability to expand/collapse sections on pages has completely disappeared. Here is a live example. $wgMFCollapseSectionsByDefault = true;
in my configuration.
Looking at the HTML it seems no elements that pertain to the collapsing are being added so this may me be a back-end issue.
I've just installed the extension and it isn't working for me either. Were collapsible sections fully supported beforehand? My infoboxes rely on them.
I had this issue on a couple pages on my wiki version 1.34.2 and determined that I had a div wrapped around multiple sections was messing up the collapsible sections. Not sure if this is your issue or not, but you could check the page and make sure there aren't any html elements like a <div> wrapping around multiple sections.
Edit: Looking at your site, I notice that on your h2 looks like <h2>
whereas on a working collapsible h2 it should appear like <h2 class="section-heading collapsible-heading open-block" tabindex="0" aria-haspopup="true" aria-controls="content-collapsible-block-0">
.
So MobileFrontEnd must be having trouble interpreting the h2 correctly. I can't view the page's source code, so I'm unable to determine the cause, but I'd guess it's the page's source code. If not that, I'd make sure that nothing in Mobile.css or Mobile.js is messing things up.
Thanks for this, I've made a mistake here. I thought the OP was referring to collapsible tables such as those with class mw-collapsible
. Unfortunately it doesn't look like this was supported at all, but I'm not sure.
Ah, thanks for clarifying. Yeah I think OP was referring to <h2>'s which are collapsible in MobileFrontEnd. Whereas mw-collapsible
is not, which is evident if you check out the collapsible examples in Manual:Collapsible_elements in Mobile View. None of the examples are collapsible in Mobile View, so it appears to not be supported.
I see a few phabricator tickets about mw-collapsible
and MobileFrontend (phab:T71773, phab:T55136), and in general it seems their thought is that 'too many toggleable elements would be a bad design' and that 'Navboxes are hidden on mobile as they are generally cluttered and not mobile friendly.' Although, here is a newer ticket (phab:T111565) where it is being discussed again.
If you're intent on it, the one possible workaround I found was on some HelpDesk Tickets (Topic:Tobruzg16mrbs8f3 and Topic:U9dr0palyjw9fxkd) about this issue, someone mentions: "You'll need to add the jquery.makeCollapsible module which is not added by default on the Minerva skin."
I'm not sure how to do that, so this may not be super helpful, but perhaps it's a starting point if you're intent on getting collapsible infoboxes working. My own approach was just to give them the class "nomobile" so they didn't display on mobile, but I realize that may or may not make sense for your content.
Indeed, thanks for your help.
I have been reading over the documentation for JavaSript modules which aren't loaded in MobileFrontend. This is where my experience ends, I did try a quick fix but it broke the wiki so I'll have to dig a bit deeper!
Anyone reading this looking for mobile support, I'm currently using Skin:Refreshed which has worked well for me over six years, though MobileFrontend has now caught up in terms of available features.
Nice, yeah my next thought was setting a different default skin for MobileFrontend, but you're already on it.
Dumped a couple more hours into this problem and I've tracked it down to src/mobile.init/mobile.init.js (it's minified version to be precise). That file takes care of enabling the collapsing of section and it's simply not being called. I've tried loading it manually but it has too many convoluted dependencies and I can't properly debug their minified code.
I'm going to need to open a phabricator task...
Mobilefrontend does not retrieve items from the filecache, nor does it trigger the generation of a cached version of an article on first viewing. Opening articles on the desktop skin does this. I realise that there is a section on using Varnish, but for those of us that like to keep things simple, is there a way (i.e. a line to add to LocalSettings.php) that would trigger the generation of cached copies of articles for mobile devices? I don't much care if there has to be two cached files, one for desktop and one for mobiles, or one cached file with both data in.
Thanks for any pointers.
Hello! I am also looking for that functionallity, nothing is possible? I can see that load time for desktop version is much quicker than the mobile version, that doesn't make any sense in today's mobile world. CloudFlare doesn't cache the mobile version, either.
hello, I have a problem with Mobile Frontend, There are 2 logos when displayed on a mobile device, one logo is in the header and the other in the footer, it looks awful, I've been looking for a logo for 2 days since unsuccessful, but unsuccessful, I'd rather be there only text as on a wikipedia page. I use MinervaNeuer Skin and version 1.35 mediawiki.
I am using MobileFrontEnd to generate the mobile view.
How can I hide certain elements from mobile view of Mediawiki?
Things like
<noinclude>content</noinclude>
will completely hide the content both from mobile view and desktop view,
but is there any code that will hide the content only from mobile view?
You can use nomobile class, e.g. <span class="nomobile">hide this</span>
.
We also used to use noprint, but it was removed.
Thank you! Your answer helps me a lot. However it seems that there are two things. <span class="nomobile"> and <span class='nomobile'> Is there any difference between the two? Thank you again!
Oh I am sorry, I forgot to put nowiki tag when I put codes in the question. I fixed the question. Thank you!
Thank you! I could check that the tag can hide texts from mobile view. However, it couldn't hide the whole table. I tried
<span class="nomobile"> {| class="wikitable mw-collapsible mw-collapsed" style="width: 50%;" |- ! title |- |dfsdf |- |}</span>
but it didn't hide the table from mobile. So instead I tried this
{| class="wikitable mw-collapsible mw-collapsed" |- !<span class="nomobile">blahblah</span> |- |<span class="nomobile">kk</span> |}
It worked. But isn't there any way to hide the whole table more simply?
Actually I decided to hide it because the table wasn't collapsed in the mobile. So if the question at https://www.mediawiki.org/wiki/Extension_talk:MobileFrontend#mw-collapsible_not_compatible_with_Mobilefrontend.3F_32385 is resolved, then I might not need <span class="nomobile"> in the first place :)
Weird question, but is there a way to make parts of the main page only show up to Mobile view with a similar div class statement?
for show up on mobile only: mobileonly.
just on desktop view: nomobile
When I upgrade from 1.27 to 1.36.2 today, I have issue after upgrade completed.
Deprecated: Registering handler for AuthChangeFormFields before MediaWiki bootstrap complete was deprecated in MediaWiki 1.35 [Called from MobileFrontendHooks::onRegistration in /home/customer/www/xxx.com/public_html/wiki/extensions/MobileFrontend/includes/MobileFrontend.hooks.php at line 1420] in /home/customer/www/xxx.com/public_html/wiki/includes/debug/MWDebug.php on line 376
Deprecated: Premature access to service container [Called from Hooks::register in /home/customer/www/xxx.com/public_html/wiki/includes/Hooks.php at line 54] in /home/customer/www/xxx.com/public_html/wiki/includes/debug/MWDebug.php on line 376
Deprecated: Premature access to service 'HookContainer' [Called from MediaWiki\MediaWikiServices::getInstance in /home/customer/www/xxx.com/public_html/wiki/includes/MediaWikiServices.php at line 252] in /home/customer/www/xxx.com/public_html/wiki/includes/debug/MWDebug.php on line 376
Deprecated: Premature access to service 'ObjectFactory' [Called from Wikimedia\Services\ServiceContainer::{closure} in /home/customer/www/xxx.com/public_html/wiki/includes/ServiceWiring.php at line 535] in /home/customer/www/xxx.com/public_html/wiki/includes/debug/MWDebug.php on line 376
Deprecated: Premature access to service 'MainConfig' [Called from RequestContext::getConfig in /home/customer/www/xxx.com/public_html/wiki/includes/context/RequestContext.php at line 118] in /home/customer/www/xxx.com/public_html/wiki/includes/debug/MWDebug.php on line 376
Deprecated: Premature access to service 'ConfigFactory' [Called from Wikimedia\Services\ServiceContainer::{closure} in /home/customer/www/xxx.com/public_html/wiki/includes/ServiceWiring.php at line 734] in /home/customer/www/xxx.com/public_html/wiki/includes/debug/MWDebug.php on line 376
Deprecated: Premature access to service 'BootstrapConfig' [Called from Wikimedia\Services\ServiceContainer::{closure} in /home/customer/www/xxx.com/public_html/wiki/includes/ServiceWiring.php at line 277] in /home/customer/www/xxx.com/public_html/wiki/includes/debug/MWDebug.php on line 376
When I enable $wgServer and more bug coming up
/wiki/api.php?action=query&meta=siteinfo&siprop=namespaces&format=yamlfm ConfigException: GlobalVarConfig::get: undefined option: 'ResourceLoaderLESSVars'
Backtrace:
from /home/customer/www/xxx.com/public_html/wiki/includes/config/GlobalVarConfig.php(59)
#0 /home/customer/www/xxx.com/public_html/wiki/extensions/MobileFrontend/includes/MobileFrontend.hooks.php(755): GlobalVarConfig->get(string)
#1 /home/customer/www/xxx.com/public_html/wiki/includes/HookContainer/HookContainer.php(338): MobileFrontendHooks::onBeforePageDisplay(OutputPage, SkinApi)
#2 /home/customer/www/xxx.com/public_html/wiki/includes/HookContainer/HookContainer.php(137): MediaWiki\HookContainer\HookContainer->callLegacyHook(string, array, array, array)
#3 /home/customer/www/xxx.com/public_html/wiki/includes/HookContainer/HookRunner.php(1000): MediaWiki\HookContainer\HookContainer->run(string, array, array)
#4 /home/customer/www/xxx.com/public_html/wiki/includes/OutputPage.php(2629): MediaWiki\HookContainer\HookRunner->onBeforePageDisplay(OutputPage, SkinApi)
#5 /home/customer/www/xxx.com/public_html/wiki/includes/api/ApiFormatBase.php(333): OutputPage->output()
#6 /home/customer/www/xxx.com/public_html/wiki/includes/api/ApiMain.php(1900): ApiFormatBase->closePrinter()
#7 /home/customer/www/xxx.com/public_html/wiki/includes/api/ApiMain.php(700): ApiMain->printResult(integer)
#8 /home/customer/www/xxx.com/public_html/wiki/includes/api/ApiMain.php(624): ApiMain->handleException(ApiUsageException)
#9 /home/customer/www/xxx.com/public_html/wiki/includes/api/ApiMain.php(588): ApiMain->executeActionWithErrorHandling()
#10 /home/customer/www/xxx.com/public_html/wiki/api.php(90): ApiMain->execute()
#11 /home/customer/www/xxx.com/public_html/wiki/api.php(45): wfApiMain()
#12 {main}
Any suggest?
Thanks
I downloaded and upgrade MobileFronted from Extension:MobileFrontend, look anything work fine, I'm sorry when I facing the issue, I'm first hand touch this project, someone work before and never provide and transfer any information to me.
I upgraded my MediaWiki from 1.31 to 1.35 and updated MobileFrontend together with the Minerva skin but Special:MobileDiff doesn't show any color. When I compare it to another wiki on 1.31, the whole HTML structure is different. I'm missing all "mw-diff-inline-added" classes for example and so the diffs don't get styled. Does anyone have any idea?
how to use these extension properly? just show desktop version on desktop and mobile version on mobile devices
show a mobile version while on mobile and show a desktop version on desktop?
$wgVectorResponsive = true; - this not looks clean and good
$wgVectorResponsive = false; - this looks responsive version of my vector themes but still not looks good
$wgVectorDefaultSkinVersion = '1'; this make desktop view as default on mobile while 2 is make mobile as default view on desktop?
am i missing something ?
Hello! My wiki has a navbox on the bottom of the page, which ideally should be displayed on the bottom of the page at all times. However, due to the structure of Mediawiki, what ends up happening is that it ends up being part of the last section and then collapsing under that section.
Is it possible to keep one section uncollapsed by default, while having the rest be collapsed? If not, is it possible to make a part of the page "sectionless" (like how the lead section isn't under a section)? Thanks in advance!