-
Just a heads up. Not sure if it's still being worked on and not sure if there is a mobile version yet but on my phone, Samsung Wave, it doesn't look pretty at all and doesn't auto detect it as a mobile device.
-
There's a mobile version, can be seen here as well, but it's really mostly geared towards iOS...
Not that I prefer iOS, but I simply have no other devices to test on.
-
Will other mobile platforms be supported by a generic mobile site and will auto-detect be added?
-
Nothing will be done until I have an opportunity to play with any devices people want support for.
As for detection, iirc Wedge should redirect most mobile and tablet devices to the wireless skin. If it doesn't, go to your profile, change skin and check whether you're on the wireless or weaving skin.
-
Grand, no worries.
-
So..?
-
Hadn't looked, I was just saying thanks as in I was going to but now that I've had a chance, its set to the forum default. :)
-
Okay. I'll have a look at the ua for Wave and add it to my list if it isn't there.
-
There aren't any 'wave' ua strings available, only phone models which I'm not going to care about, so I added a generic 'samsung' string... I doubt they'll ever release a desktop browser, so it should be fine forever.
Can you confirm you get the wireless skin by default, now..?
-
Sorry, site was down for some time...
Didn't realize my FTP client had failed to upload Class-MoDe.php properly -- so it was generating errors on new sessions.
-
Was this the error as this is what I was getting for a good while now!?
Fatal error: Class 'weMoDe' not found in /Sources/Load.php on line 368
-
Yes, and it should be working for you, are you sure you didn't change the skin *while* you were visiting the site on your mobile, by any chance..?
If not, go there and copy/paste your Wave's user agent here:
http://whatsmyuseragent.com/
-
Still the same, heres my user agent.
SAMSUNG-GT-S8500/S8500BWKB1 Bada/1.0 Dolfin/2.0 NexPlayer/3.0 SMM-MMS/1.2.0 profile/MIDP-2.1 configuration/CLDC-1.1 OPN-B
-
Well it should be working then... Very odd.
-
Cached in SESSION?
-
Oh yeah, forgot to suggest logging off :)
-
Cleared the phones cache still the same.
-
Cleared the phones cache still the same.
-
Yup... And/or log out ;)
-
Cleared everything I could possible clear and logged out and back in, still the same. <_<
-
It's no fun anymore. :(
-
if (strpos($ua, $device) !== false)
return true;
if (preg_match('/' . $device . '/i', $ua))
return true;
Plus I don't see samsung/bada in there?
Posté : 6 Juin 2012 à 13:16
Crap, no. Didn't read the foreach declaration.
-
if (strpos($ua, $device) !== false)
return true;
if (preg_match('/' . $device . '/i', $ua))
return true;
Maybe it has changed since I did my first tests, but I doubt so.Plus I don't see samsung/bada in there?
-
It is case sensitive. samsung won't match anything as it's SAMSUNG (strpos is case sensitive, stripos isn't).
-
Look at the strtolower............. :whistle:
-
What the f....I got no idea why that won't work.
-
Hence my original reply...
Perhaps it always worked for him, but he chose to go Weaving at some point during his mobile tests, and I can't do anything for him...
But if he's logged out (a guest), and has cookies disabled, then it SHOULD work...
-
Did a test run using that UA, code is evaluating it fine (after adding |samsung|). So must be something else.
-
Yup...
-
The only other thing I can think of is that the mobile site is being applied but it doesn't like working with my device, can you post a screen of what the mobile site should look like?!
-
It's simple enough: the user name (in topic pages) is ABOVE the post, and there's no message counter below it. The date is on the right side. There is no permalink to the post, either.