Naijeru

Okay, cool. To me as developer I think of viewport and screen resolution as very different things. But I understand that design decision.

Thanks for the help in getting it working, and I already have ^^ Thanks again

I feel like I’m being fussy, but it’s listing the screen resolutions wrong.

It’s listing the only viewer, as 1680×925. But it should be 1680×1050.

However I’m fully aware that this could be Chrome (17.0.963.83 m) reporting that wrongly to the javascript.

I’ve created the tables manually now. I noticed when doing that, that you have a mix of {$wpdb->prefix} and {$wpdb->base_prefix}.

But it appears to be working now. Thanks for that. Still confusing as to why it didn’t attempt to create the tables.

All I can see is updates to wp_options. Would you like the raw binary.000007 file?

Ahh, nope. Not an MU as that’s the first I’ve heard about it. Standard, default 3.3.1 install.

It’s actually a dedicated vhost running arch linux, suhosin php, apache and mysql. WordPress was put directly into the root / folder too.

That could definitely be a problem. Only the 11 base tables from WP are there, with my correct prefix. There are no wp_slim_ or any _slim_ tables whatsoever.

Also, forgot to say I don’t know where the log files are for mysql. I am trying to find them though.