What does it matter if the homepage isn't doing well? If the content pages are ranking well, that's all that matters. The homepage is just a landing page until people can go off to the page they actually want. What's probably happening is people are searching for "heating systems" and Goog...
1) Nothing
2/3) Use fgetcsv(). It's a function specifically built to read in CSV files, and takes care of parsing escaping "", and all that jazz. It's just easier.
I usually do this instead: <input type = "text" name = "userid[]"... /> <input type = "text" name = "points[]"... /> <input type = "text" name = "teamname[]"... /> This will give you POSTed information like userid => ['user1','user2','user3...
Since you've already cobbled together something I doubt you'll want to revisit, but here's my input anyway: There's no need for a 404 error to be triggered. In fact, it might muddy up the logs if you have legitimate 404 errors, and Google's SEO will almost certainly not be happy. @Celauran's rule wi...
You're going to get 1000 responses, and 2000 recommendations. 1) Every framework is simple/hard to use depending on your experience. What you're looking for is great documentation/community. Laravel is extremely popular. 3) For speed, Phalcon is pretty much the undisputed king: http://systemsarchite...
About the only way I know of is to use Javascript. Create an invisible <div> off screen that is the same width as the textarea will be, then insert the content into that div. Then, find the height of that div and set the height of the textarea to the same.
It looks like your elements are floated, but they're not a uniform size. The square with the car is getting caught on the middle element on the row above. If you make all the elements the same height, this problem will go away.
Once I saw $username = $_REQUEST['username']; $pass = $_REQUEST['password']; $qry = "SELECT * FROM `user` WHERE `email` = '$username' AND `password` = '".(md5($pass)."'"; I stopped reading. This is horrible. There is no sanitation of user provided input, so it would be incredible...
- Maybe do a check on your login page to make sure the POST request is coming from your site, not from somewhere else? - Change the name of the username field to a random string, that is stored in the user's session. Then when a login occurs, check that POST variable. This way, you know you are only...