Ingolme

You should only get the error if the setcookie() or header() function is being called. If you're not getting the error it's probably because they aren't getting called. According to your code, you're only calling those functions when this condition is met: if(isset($_POST['submit'])&&(!empty($_POST['remember'])))

This thread has the answer to your problem http://w3schools.invisionzone.com/index.php?showtopic=44106&view=findpost&p=245750

I see this has to do with background-attachment. I haven't looked deeply into how it works. Have you tried changing the background-position of the image?

Can you show the source code of the page it's being included into? PHP's include() directive is just like copying and pasting the code into the other document.

You'll get a headers already sent error as long as the header() function is called. Most likely it isn't called sometimes because the conditions of your if() statement aren't met.

Tables are allowed in HTML 5, the problem is the same as with HTML 4.01: It's not intended for page layout and is far less efficient than other layout methods. You've got quite a high density of errors in your code there. Missing closing <tr> tag, missing one of <td> or <th>, incorrect closing <table> tag. To center a flash document, just apply text-align: center to the parent element. Flash documents are inline-block elements.

There's nothing in the official specification about six rules, just definitions on how tags, attributes, comments and text nodes are written. HTML doesn't require lowercase tags, nor does it require closing certain elements.

I can't imagine how your invert effect would work without using Javascript. When the logo is over two different sections you're going to need to create additional elements to show the colors over both sections.

If you open insert.php accidentally in your browser it will add an empty entry to your database. That's probably the cause of the extra entries.

There don't seem to be two queries. Another possibility is that you're loading the page without sending a POST request. There are a lot of dangerous security issues on your page.

It sounds like your PHP script is sending two INSERT queries.

Sounds cool. The problem is that AJAX still requires a server-side language.

You could store the IP address of the person that's trying to log in and block it after a certain amount of failed attempts as well. But because the IP could belong to a legitimate user who forgot their password you should make sure to unblock it after a certain amount of time.

Sessions rely on the user sending a cookie or query string. A brute force attacker could just not send them. I think systems have a field in the database "number of failed login attempts" which resets to 0 upon successful login or after a certain time has passed (perhaps there's also a "last login attempt" field with the timestamp). When that number is above a certain value logins will no longer be accepted until a certain amount of time has passed after the most recent login.

I guess the PHP script is using extensions that aren't available on one of your servers.

Javascript can't do it. You need a server-side language and a database. The database table probably will have the IP of the user and the timestamp that the user was last seen.

Check the moveTo(), moveBy(), resizeTo() and resizeBy() methods on this page: http://www.w3schools.com/jsref/obj_window.asp

repeatID doesn't change when clearInterval() is called. repeatID just tells the system which timer to stop, but the variable itself doesn't have any significant information so it doesn't need to be changed.

CAPTCHA is the name given to any system that attempts to distinguish robots from humans. There are all kinds of CAPTCHA systems developed by many different people, so we really can't help you unless you specify which one you're using or who made it or what its source code is.

The type attribute is not required in HTML 5 as it's assumed that Javascript is the only scripting language.

Check strlen(). $e = '';if(strlen($str) > 20) { $e = '...';}$output = substr($str, 0, 20);$output .= $e;

There's the URLLoader class and related classes. They need to work together to send data. It might appear complicated but you're going to have to learn it. ActionScript can save some data on the client side using Shared Objects. They're like cookies.

input elements, like every other element, have an innerHTML property, but the innerHTML isn't what sets the text that's displayed in it. The innerHTML property just sets or returns the code that's between the two tags of the element. If, after setting the innerHTML property of an <input> element, you look at the generated DOM you should find it between <input> and </input> tags at least in theory. It's possible that browsers ignore any attempts to modify the innerHTML of an input.

You need to set the value property, not the innerHTML property.

I believe "i" stands for "iterator"