Wedge

And it absolutely never, ever happened to me in either Firefox or Opera. (And IE as well I think...)

I don't see the reason behind WebKit being a problem when it comes to server-side session handling...!

I did a phpinfo both here and locally. The only differences between the two installs are: PHP 5.2.14 on wedge.org (5.3 locally), and session settings: wddx is added to 'registered serial handlers' locally. Also, 'use_only_cookies' is set to On locally, and Off on wedge.org.
Since ini_set() can change that, I don't really see much of a difference...

Even the PHP.net documentations wasn't helpful. I did read a lot of it...

I'm a bit torn between either returning false if !class_exists('wesql'), or instead using mysql_* functions directly to handle session saving... Uh.

I have no problems with anyone trying to make a translation for Wedge... But as I said, this translator would have to be proficient in using diff tools because we're not going to release a language-centric online tool like the SMF team did. (Well, if they shared said tool with us, we could install it on our server but I'm not sure why they would do that in the first place, to be honest.)

Also, sorry about still being very largely absent from here... I can't even keep up with the new posts. I have a few things that are getting close to being committable (fixes and improvements, mostly to Wess), but I just can't find the motivation to come back into the game for now.
Given that it's the very first time it has happened since our officiel début two years ago, and it didn't even happen in my previous burnout situations, I can only reckon that this is half-due to my current burnout, and half-due to my satisfaction at having a half-working alpha out, something like 'now it's your time to work guys' ;)

However, I'll still have to complete Wess and document it either way...
Would love it if some testers were willing to write additional code to add UIs for features like board types and show_when and all those cool features I never wrote a UI for. Honestly, it's not that I don't want to write the UI.. It's that the admin area has become Pete's, and it feels wrong of me to touch it too much. (Or maybe it's just because I hate writing both the French and English versions of every string I have to add... -_-)

Anyway. Wedge looks so cool. I hadn't used it in a couple of days, and it's so cool really.

PS: Pete, the wesql not found error still occurs... And exclusively on Chrome and Safari. Really, it baffles me. I'd suggest we just don't bother, and do a class_exists() test, and if false, just return instead of proceeding. After all, it doesn't seem to affect sessions in any way...

Okay, I reproduced it... I also managed to trigger a bug when doing a 404 on a regular add_css_file call (which I fixed locally.)
I'm gonna have to leave my PC for now so I'll look into fixing the plugin bug later. (i.e adding fault tolerance for '.css.css')

Maybe we should test for '.css' if the file is not found, i.e. just replace '.css.css' with '.css'...? For starters.

Except If You dont have net access around..?

Anyway it's not a free service is it?

Plus the next delivery for nexus 4 is in 3 weeks... If I manage to get one this time! (an id rather buy it in a shop anyway...)

If your css file doesn't exist, it shouldn't even loop through $branches, i.e. not encounter that $ex_string line...??

I'm really upset about that bug.

Although maybe last time you voted for the 3rd one, the one I removed in the meantime and replaced with the new #3 and #4...? In which case it'd make sense that your vote got removed.

The font/style is supposed to be the only difference between all these choices. Basically, the logo, square, colors etc. are pretty much final at this point, at least for the footer logo. I'm keeping my options open when it comes to the homepage logo...

Looks like the 2nd logo font is still the popular one, doesn't it?
Well, at least it looks good in small sizes ;)