Philip

If you're not linking it publicly, and neither are they, there is no way for the crawlers to find your pages without doing a lot of guessing. For example, http://www.example.com/123jhl342j3lk/preview/ is going to be pretty hard to guess

If it is the Google Analytics async code, then you'll want to put it right before the </head>

This topic has been moved to PHP Coding Help. http://www.phpfreaks.com/forums/index.php?topic=346284.0

global_header.php

I'm closing this since it is technically against the rules:

Typically if you have a public_html folder, it'll be in there. Since we don't know how your site is setup we can't give too much info. Hopefully your site uses a templating system of some sort and you wont have to edit 100s of files.

This topic has been moved to mod_rewrite. http://www.phpfreaks.com/forums/index.php?topic=346275.0

Don't allow viruses. Seriously though, what kind of site do you run that gets that many viruses? Ban IPs/users that provide bad files, do some checking on the files, etc.

We've actually been toying with the idea for a while to automate some of our technical specifcation documents via XML / XSLT... it's doable for sure, did you have any specific questions or just looking for general tips?

Then the sample code you gave is not working.... are you sure your query is working? PS - you're calling fetch_assoc outside of the loop, which will essentially skip getting the first row (since the loop overwrites $row)

<?php $data = array(); while ($row = mysql_fetch_assoc($result)) { $data[$row['colone']] = $row['coltwo']; }

Most don't identify themselves as crawlers. Besides the big name ones, most go for spoofing a browser's user agent instead of showing their own.

TBH it depends on the data that you're storing in the table. If there are multiple values, they should be split up into another table (if you're using a RDMS, which from the sounds of it you are - MySQL.) This will provide a relationship between a user and some of their options/settings/whatever. An example of what should be in a single table row: Age Sex Location Name However, things like the following should be setup in separate tables: Transactions "likes" (bands, celebs, etc.) Websites (if you allow for unlimited, or really more than 1, websites to be listed) Etc... Does that make sense?

Anytime that you may need to filter for users based off of that data, you should not serialize it. TBH, it's rare I serialize data in my databases. So basically, yes, if there is a group of data that you will never need to seperate when performing a request for multiple users you can use serialization (note: not always a good idea, but it is typically OK) I like to be able to pull statistics on what people are using (ex: template choice), about them (ex: average age), etc.... but then again my profession is based off of web analytics

So... like Codepad?

You're able to reply to others, so I know you can read just fine. Why not re-read these statements: either your just not listening or your not properly updating your question. Have you tried what PFMaBiSmAd suggested? if so what is your new code and what is the current error? If not, why not?

IMO you should be using a firewall/filter instead of a keylogger.

Just out of curosity, can you post the base64_decoded string here within tags?. You can use an online tool or create a quick script to decode the string. Of course, take out any private information for your site

Bingo. We see quite a few of these kinds of 'hacked sites' that follow the same pattern, so it's unlikely you were targeted specifically (unless you think you have reason you would be.) Find all instances of the base64_decode as a start, then take a look at the way you're handling any user inputs (especially things like file uploads.) Also as mentioned above, change your passwords, etc.

I think he meant optimize, not compile.

Back at ya big boy (and to the OP)

This might help you: http://forums.macrumors.com/showthread.php?t=962699