Philip

It's weird to me to think that HTML & the WWW were created in the early '90s. I always thought it was mid-80's.

Within the link are a few external links to databases with postcode -> lat/long. Of course you'll need to get the one that is for the correct country.

http://www.phpfreaks.com/forums/index.php?topic=208965.0 should get you started

It really depends on the person. For the most part, I'd agree with you... however sometimes learning a new language (or even just a different project) requires a different approach than what you're used to and can be more difficult to break your old habits than if you were starting fresh.

Put some clothes on those people!

Canada has technology?

What sort of reports are you looking to pull?

A WYSIWYG editor is exactly what you're looking for (or trying to make... but let's stick to looking for, at least for now.) As defined by Wikipedia: And according to a decent (an older one, yes, but still good) Smashing Magazine article:

Personally, I'd make the things like "__By" linked to the user table via ID. You do this for Stories, but not for Likes, View, Comments, etc.

I wouldn't say we would do a complete blackout, nor do I think those bigger sites will. I think though that adding a 'blackout' screen on a visitors first visit on a scheduled day with 'With SOPA, you wouldn't be able to access the site and would see something like this [sample site taken down img.] We don't support these bills, and here are some resources to help fight them' would be the most beneficial.

pics or gtfo

What about people like me, who were assigned to be a hybrid designer/programmer? I don't see why we couldn't at least have a sub-forum in Client Side - Other. I honestly don't think a graphic design will be too popular for a while though.

We're working on upgrading the forums + the main site. The Craw - can you PM me more info about that issue?

<?php $user = 'munsiem'; echo 'Hello ', $user, '!';

$this is reserved. See the manual for more info:

Check for any scripts with file uploads that might have a security hole, change your ftp passwords (and really all of them, since they should be changed every X months), and remove the offending code if you haven't already. You might be able to find something within the access/error logs on how they got in.

Gotta admit, that's actually a clever hack. Is security.inc.php yours?

IMO I would use <ul> and <li> tags instead, since this is essentially a giant list. However, for the float issue, you can use a clearfix (sort of a hack, but it works well.) My favorite implementation is over at http://stackoverflow.com/a/211467/398516

You can look into using AJAX for checking these. It will allow you to have JS call a PHP script (which can then check for a specific username/email/etc in the database.) Using a JS framework such as jQuery or prototype will help you dive into the JS world easily

You can easily remove the failsafe, but I would not really recommend it. The reason for adding it is so that you don't have 5 scripts that will never end because there was an error on the cpanel processing side for whatever reason. The failsafe does not just have to break out of the loop and that's that, it could also call an error logger or something along those lines.

Sounds like this is a job for the while loop <?php // somewhat psuedo-code $i = 0; while(filesize('file.zip') == 33kb) { // Add a timeout, otherwise you'll end up in an endless loop if($i > 1000) break; $i++; // sleeeep! sleep(15); }

Do note that it isn't PHPs fault. This is a standard set by the IETF quite a while ago and likely never allow what you're wanting.

You cannot use them in the way you want in the URL. It is against the specs: http://tools.ietf.org/html/rfc3986#section-2.2 The only time [ and ]'s are allowed within the URI is for IPs: I believe you can do this though: foo.php?x%5Bfoo%5D=bar would allow you to get $_GET['x[foo]']; But I know you wanted it all for looks, but thats a no-go on looks IMO.

[] cannot be used in the URL without escaping/encoding it

Make sure session_start() is at the top.