Wedge

Cleared the phones cache still the same.

Clear your phone's cookies.

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. :(

Shouldn't that be
?

Plus I don't see samsung/bada in there?

Crap, no. Didn't read the foreach declaration.

No... This is an array of short strings that are lowercased, and the user agent is lowercased at this point, too. There's no point in wasting time compiling a regex for that. I'm just scanning the user agent for these strings. It could be faster to do a global regex match for the entire list of devices, but I did some tests earlier and it was actually slower... (Yes, a single preg_match was slower than dozens of strpos calls...)
Maybe it has changed since I did my first tests, but I doubt so.Because it's not committed yet. Currently on wedge.org there's an additional '|samsung|' in the 'generic' list. It should return 0 for ziycon (start of the string), which is !== false (but not != false of course), and thus should return true overall...

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?!