Daniel0

The version is 5.0.60-log

One wordpress install taking up 590.7 KiB where all tables are MyISAM. There are no other databases except for the standard mysql ones. I.e., the database is very small and that's why I'm wondering what it's using all that RAM for.

There are plenty of free editors that'll allow you to do that. Gimp, Paint.NET for instance. There are also online editors that can do this.

Well, if I was your teacher and you turned this in for an assignment then I would fail you. To me there is no valid reason why you would not want to write proper code. As for your bet, I'd say you lost. My advice would be to work on a smaller project and then do it properly. When you have more experience then you can start working on a larger scale project.

I didn't know Google Code had private repos. I thought they were all public and that it was for open source projects.

Why does it appear as though InnoDB is "disabled"? Ooops, sorry. I've updated the file with InnoDB enabled. I don't think that's the case. The server isn't used that much and there aren't even any InnoDB tables on the server.

It could just be something subtle like underlining #header ul #current.

403

Try to style the byline to make it not look like body text. You could make it smaller, italicize it, choose a lighter color or a combination of those. Also, make the entire tab clickable in the navigation bar. I kind of expect that when people use tabs.

Better than the green one you had before at least.

You should bring back the blue line on the very top. I liked it. I still don't like your background though. Try to see colourlovers.com for some color schemes.

In order to make it easy you'd probably have to work on the install script to make the user able to enter various values in there instead of having to edit files. That doesn't make any sense. Why waste your time deliberately write it poorly first and then make it better? Why not just make it better from the start?

The background is really annoying to look at. It actually sort of hurts the eyes. I'm not too fond of that green color either. It's too bright in my opinion. I'd probably also make the sidebar text smaller and give it a slightly larger leading. Otherwise it looks okay. Oh yeah finally, if you don't like the picture then take another one or don't put the existing up in the first place...

Gives me another reason to post this clip again: http://www.youtube.com/watch?v=FdpqH1_EC7A

Here is the output of that script: http://daniel0.net/mysql_profile.txt

Seeing as you've decided to use short tags that means it'll not run on many systems. Short tags is disabled by default on PHP5+. Seeing as I couldn't run it (I didn't bother to turn short tags on) I've decided to comment on your code. To be honest, it's really bad. All your pages are essentially one big mess of conditionals (if this do that, otherwise to this, but if something is like this you should do that instead). Just look at your index.php, it's one giant mess of code. The HTML is all mixed up with the PHP code as well. I'm wondering how you are going to implement those "templates" that your directory structure suggests will come at a later point. As it is right now that will be completely impossible. You use deprecated superglobals like $HTTP_COOKIE_VARS. Your way of doing error handling is also horrible. Simply calling die() is not error handling. It gets even worse when you start actually printing verbose information to the screen regarding the errors. That is really bad as it will potentially aid attackers in compromising the application (see the tutorial PHP Security). Then there are things like $postselect3. Do you have a constant called post? No, so don't use a constant called that. Yes, it works and I know you don't care about such stuff as long as it works (which you've previously stated), but if you set the error reporting to E_ALL then you'll see it actually results in an E_NOTICE. You need to use quotation marks around strings. I'm sorry to say it but the code is absolutely horrendous. It's poorly designed, you use deprecated stuff, you have errors, you use short tags, you have security flaws, it doesn't scale, and it will be incredibly difficult to maintain. I'd say it's back to the drawing board... Oh yeah, you should code it to be W3C compliant from the start. It'll be a pain in the ass to have to go back and make it all compliant. Especially considering how your code is structured.

I thought Flash files were vector. If that's true then it'll be ∞*∞.

LinuxForum is owned by The Web Freaks like PHP Freaks is. It will likely be brought up again eventually. As of right now it's being redirected to here instead.

It's hosted at Yahoo so we cannot do anything it if it is missing. I've never experienced that though.

And only if expose_php is set to On.

Neither does this server and I can guarantee you we are running PHP

Works for me.

There are loads of way to compress it and you can compress it at different levels. Higher compression means smaller size but more overhead when compressing and extracting. Lower compression is the opposite obviously. The Windows right-click thing doesn't give you many options but a full-fledged archiving program (my favorite is 7-Zip which supports many formats and is open source) does.

Aren't you the person who is supposed to be making the comparison based on e.g. what features they provide?

Yeah me too, only it didn't work so I got through to a human representative. She spoke Swedish though, it was pretty difficult to understand. It was a long time ago.