1000 FAQs, 500 tutorials and explanatory videos. Here, there are only solutions!
[DRUPAL] Setting up a new installation
Actions to be carried out
Unzip the archive on to the server
Move files to the root directory (optional)
Create a directory named /files within /sites/default and give it CHMOD 777 permissions
Into the same place, copy the file default.settings.php
Rename this to settings.php and change its permissions to CHMOD 777
Go to your site
Follow the steps and enter your MySQL login info
Once the installation is complete, set the files mentioned back to their original access permissions
To install a module, you must place the archive and unzip it directly into /sites/all/modules
Installing Drupal 7.26
Errors during installation and issues during use: click here for solutions
The Drupal environment was not designed to be used on shared platforms.Its architecture is too inflexible to allow sufficient customisation for it to be hosted with such plans. The default database-based cache system is plainly inefficient: a site generating a low number of visitors is brought to its knees in a matter of minutes.
If you get "Warning: MySQL server has gone away" messages, the issue is due to the fact that Drupal is attempting to execute a caching request that takes too long. In order to remedy this issue, various forums recommend doubling the maximum packet size in my.ini: max_allowed_packet = 2M
Unfortunately, this variable is not modifiable, even via an .htaccess file, nor will it be possible for us to change it on your behalf. The solution suggested by these forums does not actually solve the problem. Instead, you must check that your Drupal application is optimised, along with the various modules installed and databases used. You are reminded that your account is hosted in a shared environment, as are your databases. Such a system means that accounts share a set of unmodifiable, non-negotiable parameters that can only be set by our teams to ensure the system is appropriately balanced and that it performs satisfactorily. Unfortunately, these settings cannot be changed on a case-by-case basis: we would not be refusing your individual request but rather an increase to max_allowed_packet for all customers on that server.
Link to this FAQ: