Wedge

I know... But if a phone looks ugly, I'm not excited about it. I'm not excited with the Razr i because it doesn't look/feel great in my hand... (Or worse, the Motorola Razr HD.)
I like the S3 Mini's looks.
As for power... I don't know if I need a nuclear plant in my pocket, see..? Maybe the S3 Mini is enough for me.
Then again... It's probably a tad expensive just for the looks.Note II is definitely too wide. But it feels great in my hands (very sensual if I may say...?), plus the S-Pen is fantastic. It's the only smartphone I know of that supports :hover in CSS...! (Just have your pen close to the screen, anything below it will get the hover effect... I tried here!)
I tried the Razr HD and I just thought it wasn't too exciting or innovative, from what I could see.I've tried the Nexus 7, not the same I know, but I liked it. Except for the screen. Even in 720p, it's a bit... pixelized.
Nexus 4 has a big issue to me: it doesn't have a SD slot. It's a no-go then... I absolutely need the SD slot. I listen to tons of music on my devices. My iPod 4 with 32GB is already too small for me...When I close my hand on my phone, it has to fit exactly between the center of my palm and my intermediate phalanges, so that I have a perfect grip of it, and full freedom to use my thumb on the screen. Plus I need to be able to access the entire screen with the thumb. If I have to use two hands for that, it's too big for me.

So, from what I can see, the best width for me is around 60mm (like the Razr i, or a bit wider than an iPod), although I've held ~64mm phones that were pretty okay, such as the Xperia S. (And yes, the Xperia S doesn't have a SD slot IIRC, so it's hard to consider it...)
After trying a 65mm phone like the One S, it started feeling awkward. The Xperia T was even harder to hold. The S3 was quite obviously impossible to hold like my iPod. It's pretty much the same as holding a Note II, so between the two, I'd probably prefer the Note II.

Plus, the Note II doesn't have the deal-breaking feature that the S3 has: when you scroll something (whatever, settings page or web page), and you release your finger, you'll see the screen scroll itself automatically quite fast, then suddenly stop and keep scrolling very slowly for like half a second. It doesn't sound terrible when I say it, but once you see it in action, it's hard not to take this into account. The Note II seems to fix that. I NEVER was able to find a website discussing this. It looks like no one on the net has ever noticed that. And yet, everytime I showed this to other people with a S3 in hand, they admitted that it was odd.

This one is fixed, right..?

Asking again... Fixed or not?

It's just something I never got around to fixing before...
Fact is, it's a bit odd that item descriptions don't show this bug, even though they were handled in a similar fashion... :-/

- I don't think APC is installed or at least enabled. It doesn't show up in the phpinfo stuff.

- Hmm yeah, westr_foundation doesn't show up when the error happens, it's not that I forgot to paste it or anything. (The 102 first entries are regular PHP classes.)

Could the main difference between westr_foundation and wesql/wetem be that it doesn't have a __construct() magic function..?
I don't know.

It's indeed quite odd that westr_foundation itself isn't registered, but its descendants are... :-/

Still, it's a server-related problem, I'm pretty sure. Must be somethin' with the PHP version... I don't know.

rev 1774
(1 file, 2kb)

- Committed a working copy by mistake. (index.css)

From rev 1773, forgot to mention it:

* Optimized space saving on !important and content rules in Wess. (Subs-Cache.php)

Nope... Didn't work a bit. Reproduced the bug, moved loadDatabase() to index.php, even manually added the wesql::getInstance() before loadDatabase(), and it STILL gave me the same error. And it's always caused by Load.php::sessionWrite(). It doesn't seem to remember the wesql class at all... Although it DOES remember $user_info and other globals. That's quite odd.

There may be a hint though: it looks like sometimes, the sessionWrite function is executed twice at the end of the flow... (?)
And it only generates the error on the second call.
But sometimes it's also only executed once, and then generates the error.

Forget what I said, it's never executed twice...

So, I did a get_declared_classes() when $user_info['is_admin'] is on.

Normal execution:

 ...
    [103] => wetemItem
    [104] => wetem
    [105] => wesql
    [106] => westr_foundation
    [107] => westr_entity
    [108] => westr_mb
    [109] => westr

Failed execution:

...
    [103] => westr_entity
    [104] => westr_mb
    [105] => westr

So... It's interesting that both wetem and wesql are seen 'differently' and don't always remain in scope while westr is always seen.
Any clues, Pete...?

Also, very very oddly, it seems like IE9 NEVER shows me the error... (Which is why I thought it couldn't be reproduced.) Chrome does.

Meh... I really don't see any differences between how westr and wesql are declared.
I've removed a couple of globals that are declared but never used in __construct and getInstance, but I don't think it's got anything to do with it eh...

Strangest thing ever...
Added this at the beginning of the function.


Guess what? Now the page crashes on loadDatabase's wesql::getInstance() call.... :-/

I'm not exactly sure what you mean by scoping in this case.
Also do note that it really happens only once in a while. On every single page the sessionWrite function is executed, and if I do echo class_exists('wesql'), it'll return 1... Except for the times when it returns false, and then the error message.