sudo a2enmod rewriteapache2ctl -Mnano) to edit the appropriate Apache configuration file for your Drupal site in the /etc/apache2/sites-available/ directory. For a single site, the file is /etc/apache2/sites-available/default; if you have multiple sites, the file names should reflect the names of the sites to which they refer. Thus, to edit the default site configuration, usesudo nano /etc/apache2/sites-available/defaultDirectory section referring to the folder where your Drupal site lives (in /etc/apache2/sites-available/default, this is typically AllowOverride None to AllowOverride Allsudo /etc/init.d/apache2 reload
Subdomain SetupInstead of creating multiple virtual host files, you can create one virtual host file that uses a wildcard in the ServerAlias. Both a simple multi-site Drupal setup and multiple Drupal versions can run this way, if the different subdomains are defined for each site in settings.php.Consider the following and modify your configuration file to fit your needs.Here is a partial listing of a virtual host configuration file that would support the last two lines in the above example. Note this is not intended to be a COMPLETE configuration file, but rather provide guidance for your development setup.
DocumentRoot "/www/Dr6"
ServerName example
ServerAlias *.dr6.example
AllowOverride All
Edit & save your config file to suit your development needs. Assuming the site is already enabled, then reload Apache./etc/apache2/apache2.conf.sudo a2enmod rewritesudo a2dismod rewritesudo nano /etc/apache2/apache2.conf
AllowOverride Allsudo /etc/init.d/apache2 reload
Step 1 - Method C: Add Rewrite Rules Directly to Virtual Host or apache2.confIf you do not wish to allow .htaccess overrides, you can add the rewrite rules directly to a virtual host file or apache2.conf. The following should work:
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
This can provide slightly faster server performance since Apache will not look in every directory for an .htaccess file.Note that, for proper security, you will need to add in the rules from the Drupal files directory's .htaccess file as well.More info >> http://drupal.org/node/134439
If you have locked yourself out, visit http://example.com/?q=user just like you do to re-enable offline sites. You can log in there, enough to become admin, although none of the navigation will work yet.
Next, enter http://example.com/?q=admin/settings/clean-urls (in DRUPAL 5 and 6) to view the page where you can unset clean URLs.
Your interface will be usable again.
Other options that should get the same result include:
drush vset clean_url 1 --yes
UPDATE variable SET value = 's:1:"0";' WHERE name = 'clean_url';
DELETE FROM cache;
$conf['clean_url'] = 0;Chances are, your webhost will do this for you if you are on shared hosting.
If you want to support mixed-mode HTTPS and HTTP sessions open up sites/default/settings.php and add $conf['https'] = TRUE;.
This enables you use the same session over HTTP and HTTPS both -- but with two cookies where the HTTPS cookie is sent over HTTPS only. You will need to use contributed modules like securepages to do anything useful with this mode, like submitting forms over HTTPS and so on. While your HTTP cookie is still vulnerable to all usual attacks, a hijacked insecure session cookie can only be used to gain authenticated access to the HTTP site. It will not be valid on the HTTPS site. Whether this is a problem or not depends on the needs of your site and the various module configurations. For example, if all forms are set to go through HTTPS and your visitors can see the same information as logged in users then this is not a problem.
For even better security, leave $conf['https'] at the default value (FALSE) and send all authenticated traffic through HTTPS and use HTTP for anonymous sessions. Once again contributed modules like Secure Login can help you here. Drupal 7 automatically enables the session.cookie_secure PHP configuration on HTTPS sites, which causes SSL-only secure session cookies to be issued to the browser.
$conf['https'] can be left at its default value (FALSE) on pure-HTTPS sites.
cd DRUPAL-ROOT patch -p1 <>
* Be warned: this may break your Drupal installation , so make sure to have a backup at hand.
If you get errors like Reversed (or previously applied) patch detected or 1 out of 2 hunks FAILED while running the patch dry run (second command above) immediately interrupt patching and upgrade following the steps explained in UPGRADING.txt.
See the tutorial video here.
This module provides a language switching block that is very similar to that provided by the core locale module, however its behavior differs from the locale block in several ways:
1. The visibility of language links in the block is consistent and independent from the existence of translations for the page that you are viewing. The logic here is that the user should be able to change the language of the interface at all times. This is important because often there are menus and blocks that are language specific and the user should always be able to find the link back to their language.
*** For those who would like to have it so that languages which are not translated also do not have language links you should use the Language Icons module in conjunction with the core Locale module. ***
It is considered a good practice to do all development work on a separate test site before making changes to a production site. A test site allows you to evaluate the impact of upgrades, new modules, modifications to themes etc. without causing disruption to your live site. For information about setting up a web server on a local computer, see the Local Server Setup section of the Developing for Drupal guide.
Drupal files, and associated modules, are compressed in the .tar.gz format and can be extracted using most compression tools.
On a typical Unix command line, use:wget http://drupal.org/files/projects/drupal-x.x.tar.gztar -zxvpf drupal-x.x.tar.gz
This will create a new directory drupal-x.x/ containing all Drupal files and directories and will preserve all of Drupal's file and directory permissions. Move the contents of that directory into a directory within your web server's document root or your public HTML directory.
mv drupal-x.x/* drupal-x.x/.htaccess /var/www/html
The base URL for your Drupal installation will be set in your Web server's configuration file. You will need to know this URL before proceeding to the next step of the installation. If you are installing Drupal on your local machine the base URL may be: http://localhost. If you are installing Drupal onto a Web server your base URL may be a specific domain name (such as http://example.com).
Note for Windows users.tar.gz files. To use 7-Zip, right-click on the .tar.gz file and, in the menu that appears, select 7-Zip -> Extract Here. A .tar file will appear. Right-click on the .tar file and again select 7-Zip -> Extract Here. In a few moments, the final Drupal folder will appear.Your Drupal download comes with a default configuration file at drupal/sites/default/default.settings.php which needs to be prepared so that the installer can edit it.
default.settings.php to settings.php. You can do this from the command line using cp default.settings.php settings.php.drupal/sites/default directory.chmod a+w sites/default/settings.phpchmod 666 sites/default/settings.phpchmod a-w sites/default/settings.phpchmod 555 sites/default/settings.php.This step is only necessary if you don't already have a database set-up
(e.g. By your host). In the following examples, 'username' is an example MySQL user which has the CREATE and GRANT privileges. Use the appropriate user name for your system.
First, you must create a new database for your Drupal site here, 'databasename' is the name of the new database):
mysqladmin -u username -p create databasename
Next you must login and set the access database rights:
mysql -u username -p
You will be asked for the 'username' database password. At the MySQL prompt, enter following command:
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER ON databasename.* TO 'username'@'localhost' IDENTIFIED BY 'password';
where
| 'databasename' is the name of your database |
| 'username@localhost' is the username of your MySQL account |
| 'password' is the password required for that username |
FLUSH PRIVILEGES;
the database should be created with UTF-8 (Unicode) encodingTo run the install script point your browser to the base URL of your website.
The base URL is defined in your Web server configuration file and is specific to the document root where you placed your Drupal files. If you have installed Drupal on your desktop machine this URL might be http://localhost.
You will be guided through several screens to set up the database, create tables,
add the first user account and provide basic web site settings.
