Adam

Did you 'lick it a little' before or after you started spraying it daily?

I can't see bleach giving it a funny neck. It there was enough bleach in there to do damage, I'm sure it would have gone blind first.

A vice and some weights.

Well that's not actually Firebug. Admittedly though Firefox's default developer tools are getting much better. The 3D layering is pretty good, but I've not found a use for it yet. In terms of GUI, Firefox's tools may look a little better on the eyes, but there's nothing wrong with Chrome's. Chrome's has more functionality though, so it wins IMO.

I don't think there's anything in Firebug that's not in Chrome's developer tools?

I've had a hair cut, but should still be recognizable

Well work's paying for us to go so it doesn't cost me anything. £115 is pretty steep, but I bet what you learn is worth it. Be interesting to meet up with someone from here though.

Yeah I think that's a bit of an excessive journey. I'm going with some guys from work. I'll try to get some pictures, but imagine there will be plenty on the site afterwards.

Is anybody attending PHP NW this year? http://conference.phpnw.org.uk/phpnw12/

Please do not make any effort to make it PHP4 compatible. As the author of the app you can add whatever dependencies you want, so long as you make them clear. You may need to consider your target audience however, and the server set-up they're likely to have, but even most shared hosts support PHP5 these days. Perhaps even the majority are on 5.3 now (maybe). What do you mean by "3rd Party PHP modules", in relation to a framework?

Just to be sure, is your production server Windows-based?

Welcome gec100! Good luck

You can view the headers, but not 'tamper' with them. Anything like that I would use Charles for though anyway, which can do a lot more.

You need to update the PHP module used by Apache. The module's compiled, so when you update PHP you need to re-compile it to use the new version.

Don't think I've ever heard a better reason to switch to Chrome.

I doubt such a tool exists, and if there is I doubt it's reliable. TL-SQL has features MySQL does not, and vice versa. These go beyond switching one keyword for another, and when you factor in differences in each language across their versions, it's just not feasible. Such a migration requires a developer or DBA to do it manually.

PEAR's essentially just a group of PHP files (kind of a mini-framework) stored on the web server, with a command line package manager. If you're on a shared host it's possible (probably likely) that it's not been upgraded for a while, though it's also perfectly possible it's fully up to date, but the MDB2 package has just never been fixed. As I said, take a look at the PDO extension. PEAR is pretty out dated now. If you have access to the database server, why not just create the database yourself?

You're getting the deprecated notices because you're using an old PEAR package, that hasn't been updated in over two years (assuming you're even using the latest version). PHP has changed in that time, and although they aren't the cause of the issue here, you really should switch to a better, up to date database abstraction layer like PDO. Eventually those notices will turn to fatal errors. There error here is that the user you're connecting with doesn't have read access to the database specified in "DATABASE_BASE".

Depends what the file is going to be used for..?

PEAR::isError() is checking if the ->data property is a PEAR_Error object. You need to trap the error in a variable so you can access it again to get the error: if (PEAR::isError($error = Database::get()->data)) { die('Error: ' . $error->getMessage()); } That should explain the problem. I would recommend you make the move to exceptions sooner rather than later though, PEAR error objects are far too easy to loose. You can tell PEAR how to handle errors with the setErrorHandling() method.

I think what he's saying is that the 3 items should be part of a single drop down menu, but instead they are displaying horizontally in IE9. Ah yes. I don't know how I didn't realise that

This should be done with CSS. JavaScript should never be used to control the position of a static element. Do you have an example online we can look at? Or perhaps able to give us some mark-up to recreate it?

This topic has been moved to Miscellaneous. http://forums.phpfreaks.com/index.php?topic=365380.0

Oh by the way, in the next version of FF it will update automatically in the background

Do you use Windows? Ever seen those pop-ups after an automatic update saying "you've got x minutes to click cancel or we're going to reboot your computer"? .. Then after you click cancel it pops back up again 4 hours later, and every 4 hours until it catches you AFK. I'm aware you can disable auto updates and the auto reboot (though that's not exactly straight-forward), but it's the default behaviour.