Daniel0

If you're concerned about interception then you need to use SSL.

But how many people do you think know that? From a technical standpoint, www.example.com and example.com could be two distinct machines and strictly speaking it should be considered as two different websites. It's up to the sysadmin to make sure that people who choose the incorrect domain name gets forwarded to the correct one.

Google says otherwise:

The nameserver would be the phonebook and the IP address would be the phone number.

You can always just use the SID as CSRF token instead of manually generating a new one each time. Alternately you could keep an array of CSRF tokens for that user as session data. Either way, your code above is rather inefficient.

Using the database is overkill. Just use sessions. A brief example is given here: http://www.phpfreaks.com/tutorial/php-security/page8

Sure, here you go: http://en.gentoo-wiki.com/wiki/Apache2/SSL_and_Name_Based_Virtual_Hosts Server Name Indication (SNI) is defined in RFC 4366, section 3.1. Unfortunately, the fact that the majority of Internet Explorer deployments don't support it makes it practically impossible to use in a production environment.

I once bought a PDF version of php-architect. Like thorpe, I found virtually no information I didn't already know in that issue. That's not to say others might not benefit from it. I just didn't. Considering it was a PDF purchase it was available for me instantly though.

I read an article a while ago that alleged that consumer grade wireless electricity was safe for people to pass through. Or at least it would be. It was a long time ago though, probably half a year or so.

Yeah yeah that's fine, but when do they invent a lightsaber?!

You want a tutorial on best practices? That's going to be difficult. That topic is highly subjective.

I just don't see the point in e.g. (Smarty): <ul> {foreach from=$myArray item=foo} <li>{$foo}</li> {/foreach} </ul> instead of <ul> <?php foreach ($myArray as $foo): ?> <li><?php echo $foo ?></li> <?php endforeach ?> </ul> With discipline and proper app design it shouldn't be a problem to keep it separated (and enforce it separated).

Then you'll just be mixing another language than PHP with HTML. I don't see the point in that.

You're going to have to mix it some time. How else would you iterate over an array to output each element for instance?

You can use the svn:externals property to include files/folders from external repositories.

This is a diff of the vanilla stylesheet (style.css) and our stylesheet (style_mod.css): --- style.css 2009-01-10 12:48:42.000000000 -0500 +++ style_mod.css 2009-02-15 05:49:40.000000000 -0500 @@ -1,3 +1,25 @@ +#header { + width: 100%; + background: url(/media/images/forums/bg_header.png) repeat-x; + height: 133px; + margin: 0; + padding: 0; +} + +#header h1 { + padding: 0; + margin: 0; +} + +#header h1 a { + text-indent: -9999em; + width: 429px; + height: 133px; + background: url(/media/images/forums/logo.png) no-repeat; + display: block; + outline: none; +} + /* ************************************* */ /* Common styles for the theme */ /* ************************************* */ @@ -241,23 +263,23 @@ /* A quote, perhaps from another post. */ blockquote { - color: #000000; - background-color: #D7DAEC; - border: 1px solid #000000; + background: url(images/quote_bg.png) 5px 5px no-repeat #eee; + border: 1px solid #AAA; margin: 1px; - padding: 1px; - font-size: x-small; + padding: 5px 5px 5px 28px; + font-size: 8pt; line-height: 1.4em; } /* A code block - maybe even PHP . */ -code +code, .phpcode { color: #000000; background-color: #dddddd; display: block; font-family: "courier new", "times new roman", monospace; - font-size: x-small; + /*font-size: x-small;*/ + font-size: 9pt; line-height: 1.3em; /* Put a nice border around it. */ border: 1px solid #000000; @@ -393,6 +415,17 @@ background-color: #E0E1E8; } +/* Solved Topic Background colors */ +.solvedbg { + color: #000000; + background-color: #D6F5D3; +} +.solvedbg3 { + color: #000000; + background-color: #D6EFDC; +} + + /* Color for background of posts requiring approval */ .approvebg { @@ -529,6 +562,7 @@ width: 100%; overflow: auto; line-height: 1.3em; + font-size: 85%; } /* Sometimes there will be an error when you post */ @@ -865,4 +899,4 @@ padding: 2px; cursor: pointer; color: white; -} \ No newline at end of file +} Doing that adds a large amount of vertical whitespace in the post body.

It happens for me in this topic as well. Chrome on XP.

No, it was taken out of beta a while ago. Anyway, I don't know why it would behave like that.

Dude, that doesn't even make sense. In your opinion there are more? Either there is or there isn't - opinion is irrelevant.

You need to put quotes around your values.

How doesn't it work? Saying that it "doesn't work" doesn't help very much. What does your code look like? What errors do you get? etc.

Just remember that MyISAM is non-transactional. You'll have to use InnoDB.

That's what abstraction is for.

Also, you might want to look into transactions so you can roll back if either of the queries fail.

From the information given it could potentially have been overridden in ChildA. Parent::method() isn't declared final so the person who implemented ChildA would be free to do that. Anyway, the PHP manual uses that notation as well. Example: http://php.net/manual/en/mysqli.query.php