KevinM1

http://windows.microsoft.com/en-US/internet-explorer/products/ie-9/system-requirements

For shits and giggles, the system requirements for the latest official versions of Firefox, Chrome, and Opera: http://www.mozilla.org/en-US/firefox/6.0/system-requirements/ http://www.google.com/support/chrome/bin/answer.py?answer=95411 http://www.opera.com/browser/download/requirements/ I don't think requiring users to have Windows XP is too much to ask.

IMO, it's a bad habit. Catering to the minority only forestalls the change they'll need to take in order to join the rest of us in the modern world of the web. It's easier, and better, to have a noscript tag with links to modern browser alternatives they can use. It's akin to wasting time/effort ensuring that a site looks good on 640x480 monitors.

...what? There's no need to have JavaScript code wrapped up in something like: <script type="text/javascript"> <!-- // JavaScript code --> </script> It hasn't been necessary for years, since the early days of IE and Netscape Navigator. It used to be necessary because the old browsers didn't know how to parse JavaScript, and instead merely spit the code out to the screen as text. It doesn't cause a problem. It's just completely unnecessary, and a sign that the coder doesn't know what they're doing. Now, a commented out CDATA block: <script type="text/javascript"> //<![CDATA[ document.write("Hello World!"); //]]> </script> Is used to ensure that an XHTML or XML document will validate. That said, who uses XHTML any more?

He means make it your web root. Aside from your index script, you don't need your PHP code in your web root in order for it to work. In fact, it's more secure to keep your PHP somewhere above your web root in order to block all outside access to it. And, yeah, all static content (read: non-PHP, non-db) should be in its own folder, with whatever folders you need for organization inside. RE: naming conventions - conventions are conventions for a reason. Do you anticipate confusion? Are you aiming for your system architecture to be used by others?

Not necessary in browsers younger than IE5 or so. Placing JavaScript code in HTML comments is evidence that the coder doesn't know what they're doing.

Except, Facebook isn't an agent, and aside from REQUEST_URI, there isn't anything available to you that could help. Even then, REQUEST_URI may not be reliable. The only sure-fire way to detect if you've been framed is to use JavaScript. http://www.php.net/manual/en/reserved.variables.server.php

+1 IE6 is just misunderstood.

How would the server variables associated with your script detect that another script - executing on another server - framed your script?

Feel free to showcase your existing work in our Website Critique sub-forum. You likely won't be able to start off with PHP as your career as, well, the economy is in the shitter, and you're in a rather large pool of other amateurs/quasi-professionals. With no real portfolio to speak of, your chances of getting hired are virtually nil. Your best bet, at the moment, would likely be to start as a freelancer in order to build a respectable portfolio and learn to deal with clients, then move on from there. Also, work on your deficiencies. OOP is more than just syntax. Do you know what composition means? Do you know what a factory is? An adapter? The MVC pattern? How are your database skills? What about your non-jQuery JavaScript?

Embedded audio? Really? Suddenly it's 1998 again. Rule #1 of web design - don't force your users to listen to any sounds they cannot turn off. When you take control away from the user, the user goes away from your site. And, really, there's no design to speak of here. It's a black site with neon green boxes and font. It looks like it took about 3 minutes of planning to come up with. Not trying to be harsh, but there's nothing there to comment on aside from an annoying .mp3 which plays automatically and a form with no layout applied to it. You need some graphical elements. You need to look at making your form elements on your Members page align so it doesn't look haphazard. You need to give users relevant information about: Who the group is. What the group does. Where they operate from. What membership entails. Contact information. Meetings/other activities. What you hope to do with the data (simply store it? plot maps?). Local charter info.

Where is your model code in relation to your index code? I ask because it seems as though the config info is being lost somewhere along the way to you wanting to use it in your model.

Let's see...you could store a variable in: Sessions A generic cookie A database A file You could send it to another script via GET or POST. What other option would you like?

What's your Document class look like?

Do you have session_start() at the top of log_in2.php? Are you sure that the title is set properly when you redirect from your login script to your article? Have you tried commenting out one of the header redirects in order to see which one is actually bringing you back to the index?

The process that you're going through is what will turn you from an amateur to someone with at least a modest idea of what they're doing. All of us had to go through it. It's a painful process, but you'll be thankful you went through it. A lot of beginners think the best way to code is to jump in and out of PHP/HTML whenever they want. The language has that option as a feature, so it must be the way to go, right? Wrong. That's the classic trap of PHP. Well designed sites do ALL of their data processing before they attempt to display anything to the screen. Why? For a multitude of reasons: To avoid header problems like you're currently experiencing. To react better to the HTTP request/response cycle. To make the code itself far tidier, which, in turn, makes maintenance far simpler. Unfortunately, a lot of tutorials available online are (very) dated, and show exactly the wrong way to write scripts, so newbies learn the wrong way to approach the problem. Even worse, many think they're on the right track when they're actually writing badly designed sites. Just remember: process then display.

http://www.php.net/manual/en/ref.pcre.php

You can't use header after output is sent to the browser. This means ANY output, including a simple space or return. See the following thread for more info: http://www.phpfreaks.com/forums/index.php?topic=37442.0

Ultimately, like cssfreakie and the others have said, it's all about using the right tool for the job. When all you have is a hammer, everything starts to look like a nail.

To add to that, it's best to use one of the two functions (htmlentities or htmlspecialchars) before displaying that data. There's no need to use it on data insertion, so don't treat them as you would mysql_real_escape_string. So, for absolute clarity, use mysql_real_escape_string when inserting data into your database. Use one of htmlentities/htmlspecialchars when pulling your data from your database and displaying it in the browser. Regex is best used as validation for other, smaller inputs in your form, like an email address input.

Unless the variables are in separate namespaces, you can't have two with the same name. The compiler cannot guess at your intent when you try to use one of them, regardless if you think the context of their use is explicit. Since it's ambiguous to the compiler, it's an error. Why would you want two variables with the same name in the same namespace anyway? From a useability standpoint, that's just asking for trouble.

In the future, please place all code within either or BBCode tags. I took the liberty of doing it for you this time.

$idInfo = $_GET['id']; list($idNumber, $idText) = explode(':', $idInfo); echo $idNumber;

This topic has been moved to CSS Help. http://www.phpfreaks.com/forums/index.php?topic=341929.0

What does using $_GET have to do with anything?