Extension talk:MobileSkin

Further Testing Request
This extension needs more testing with different mobile devices and browsers. I disabled all skins but MonoBook, had my CSS guy create an "iPhone" skin, and copied chick as a skin called "Mobile" (so non-technical users don't get confused by the name). So the list of skins is "Mobile", "MonoBook", and "iPhone". New users are set to "MonoBook" for their desktop/laptop access by default. Then MobileSkin changes skin when pages are displayed, without changing the user's default skin. Makes the login page easier to use on a mobile screen too. Let me know if you see a better way to implement this feature or experience any problems. Chanur 16:33, 19 December 2008 (UTC)

Skin Bug
Fatal error: Cannot access protected property SkinStandard::$skinname in /var/www/vhosts/betazoid.co.za/httpdocs/wiki/extensions/MobileSkin/MobileSkin.php on line 30

This occurs with Classic and Nostalgia when browsing from my PC. Is there a way to detect screen width?


 * Didn't get notified the talk page changed until today. What version of MediaWiki are you running? I haven't tested it with Classic or Nostalgia as default skin, but I will. Chanur 01:30, 25 June 2009 (UTC)


 * Edit MobileSkin.body.php and change line 25 from "$this->mobileDebug = 2;" to "$this->mobileDebug  = 0;". The debug messaging is trying to get the skin name and Nostalgia and Classic do not like that. I did not look at those skins to see why, but this appears to correct the fatal error. Chanur 16:17, 25 June 2009 (UTC)


 * I've changed the code to use the accessor method (hope you don't mind!). —Emufarmers(T 19:19, 27 June 2009 (UTC)


 * No problem. I'm always open to a better way. Thanks Chanur 23:15, 27 June 2009 (UTC)

PHP <? Tag for Source code
The article recommends to copy the code into .php files, yet it does not have the <? php text to identify the file is php code for the server to analyze. This results in the main PHP file being dumped and gives many header errors on execution. Many users using MediaWiki may be unaware of this issue, resulting in failed installations.


 * Good point. Chanur 01:32, 25 June 2009 (UTC)


 * I suggest you add the ?> to the end of the file too. 70.76.32.230


 * As I recall the final ?> is not supposed to be in the text on the page; this is a documentation convention though I don't remember why. Chanur 02:15, 11 July 2009 (UTC)


 * Ahh, having the ?> actually breaks the extension's functionality (causes PHP-parse issue), so it's a good idea to not stick it in. 70.76.32.230 00:29, 18 July 2009 (UTC)

Where are the iPhone skins?
At least on Ubuntu, the mediawiki package does not contain the 'iphone' skin. It sure would be nice if this page linked to where that file was available, rather than forcing a lot of Googling. This plugin and that skin seem more useful together than apart. 70.76.32.230


 * There is no official iphone skin. We put one together for a client but it was very branded. I'll look at generalizing it to provide a starting point. Chanur 02:15, 11 July 2009 (UTC)


 * Simple iPhone skin posted to Manual:Gallery of user styles. Look for "Simple iPhone". Download and modify it (e.g. change colors, etc) to meet your needs. Chanur 02:47, 11 July 2009 (UTC)

IE8 Vista64 Mobile Render
It appears Internet Explorer 8 (x86) on Vista x64 machines renders in mobile mode. HTTP_USER_AGENTS appear to be identical, yet I cannot find the source of why this occurs. This has been reported to occur on two separate machines. I am unsure why this occurs.

32-Bit - Rendered MobileSkin: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.5.21022; .NET CLR 3.5.30729; OfficeLiveConnector.1.4; OfficeLivePatch.0.0; .NET CLR 3.0.30729)

Is anyone able to replicate this issue on a Vista x64 machine using their 32-bit version of Internet Explorer?

Error on 1.16
I'm getting the following error

PHP Fatal error: Call to a member function getNamespace on a non-object in Skin.php on line 222

I'm assuming that it's something to do with a simple change for the new version but haven't been able to track it down.