Adam

Companies do cater for their users, but given it makes the developer's job harder, they have that urge to complain amongst fellow sufferers. I agree that IE9 has largely over come a lot of the old issues and I don't think it's a bad browser, but as others have said, the old issues haven't suddenly disappeared. People are still dealing with them daily, which is why people still get munk on about it.

<center> is deprecated, and alone wouldn't achieve what the OP is after. You're much better off using display: inline-block on each of the .container08 elements, with a parent element containing text-align: center. Unfortunately this isn't supported in older browsers, so there's a few little hacks you need to include. Created this to demonstrate: http://jsfiddle.net/EcPcw/ Ensure the last four properties remain in that order.

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

Your JS is within a script tag that includes external code. You need separate script tags: <script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/1.8.1/jquery.min.js"></script> <script type="text/javascript"> function SubmitThisForm() { location.href = 'statuses.php'; } </script>

Not just the better you get, but the more you begin to customise it. That's the real beauty of vim. They say you should learn/add a new feature every week, and in time you basically build up the perfect IDE for yourself. I find it hard moving to a different editor/IDE though, I'm forever writing ":wq". Even in Word documents.

Just looked like a vim colour scheme to me, but it's obviously doing something. What's output if you run this in the terminal: echo $LS_COLORS

I don't know exactly what that .reg files does to your PuTTy session, but after a quick look on the website I didn't spot any screen shots of ls output. Are you sure it's actually for that? By default I believe the --colour option for ls is disabled. You might want to add an alias in your .bashrc file to ensure it's using them: alias ls='ls --color=auto' You can go a step further and define the colours you want to use yourself (this guy explains how). Although I guess the .reg file could be trying to do that and failing. I'm not sure with PuTTy. We'll see how the alias goes first. I always work within vim. The bog standard set-up isn't great, but the whole purpose of vim is you progressively customise it exactly how you like it. Once you learn the commands and define your own, set-up your colour scheme, add tags, etc. You'd be surprised how fast you can work with it. I've even got a PHP debugger configured so I can step through the code as it executes, add in break points, etc.

Bit odd, but okay. In the anonymous function then you will need to manually trigger the form submit (if needed): document.formName.submit();

The result of the AJAX request should not determine whether the handleLogin() function returns true or false. The return statement is simply to stop propagation. Even if the request fails, we don't want the form to then go on and submit. Yeah, although nothing will be waiting for the return values of the anonymous function, so you may as well remove them.

Well technically when it comes to arrays, PHP is actually the black sheep amongst languages. JS is pretty standard, in that you can only have sequential, integer indexed arrays. If you want the equivalent of an 'associative' PHP array, just use a standard object.

May I recommend the freelance board? Seriously, we're not sat here waiting for you to give us something to do.

Glad it's sorted. I don't think you can blame it on the while loop being 'bugged' though. They work exactly as they do in PHP, or any other language.

What exactly are you trying to do? You've just provided a load of random code and said 'I need to another d(v4)' ..

You're only returning from the anonymous function assigned to the state change event, not the actual handleLogin() function. You need to always return false from handleLogin(), regardless of what happens with the request. Remember that the callback you assign to the XHR object isn't called for a relatively long time; handleLogin() has long since returned by that point.

Fair enough it's valid, but your question was what 'lines MUST end with a semi-colon'. Semi-colons aren't required there, and shouldn't be used there.

Nope.

Are the return statements within a callback? Can you show the whole code please.

The time it takes to build a CMS is not free, if you're a freelancer. I've actually got a bit of a background project I keep coming back to that's building my own CMS; it's no simple task, if it's done properly.

That screenshot doesn't explain at all what's not working.

Sounds like you're using history.back(), in which case the browser will always ask if the user wants to resubmit the form, for security. You should form a completely new request to the previous page, and pass along whatever data is needed.

Your selector is an <li> tag, which will match each of the items in the list. You need to provide them with something unique to use within the selector, or access the 'nth child' if it's all dynamic.

Variables within single quotes are not parsed, so you're literally trying to delete '$code'. You could use double quotes (which are parsed), but there's no reason to wrap just a variable in quotes anyway. Drop the quotes..

As thorpe was getting at, you're not handling errors. "Overwriting" issues are not the problem. Please add in some error handling and then report what's actually going wrong.

I'm not ruling out that it's real people wasting their lives spamming, but it's also possible the captcha system you're using at registration has been cracked. While the letters are a little sketchy looking, they're still pretty clear. I would switch to something like reCAPTCHA and see if the problem persists.

You could just use PuTTY to access the server's VI(M?) editor (assuming it's Linux). That's real easy to transport, heck it's even available as an iPhone app now!