Basic installation and configuration steps for Drupal
Terms : Hide Images
| 180072668 | Quick install installer steps | Browse to your new Drupal site. This will take you to the Drupal installer, which starts with: "Select an installation profile." Save and continue. Choose "Standard." Save and continue. Choose English or learn how to install Drupal in other languages. Save and continue. Choose the type of database you created (e.g. MySQL or SQLite). Enter the name of the database you created, the username, and password. Save and continue. Set the site name and email from which the site will send out mail. Set the username, email, and password of the first administrator account. Save and continue. | |
| 180072669 | Quick install for developers | Download Drupal, put the Drupal files in the correct directory, create the configuration file, create the Drupal database, run the installation script | |
| 180072670 | Quick install for developers: Run installation script | Point your browser to the base URL of your website (e.g. http://www.example.com, http://www.example.com/drupal or http://localhost/drupal). The installation wizard will guide you through several screens to set up the database, add the first user account, and provide basic website settings. Follow the wizard to finalize the installation and start working with your Drupal website. | |
| 180072671 | Quick install for developers: Put the Drupal files in the correct directory | Move the files to a directory within your web server's document root or your public HTML directory using the following command, substituting drupal-x.x with the actual version number. (On many *nix computers the path from the server's root will be /var/www/.) mv drupal-x.x /var/www/ | |
| 180072672 | Quick install for developers: Create the configuration file | In the sites/default directory, copy the default.settings.php file and rename the copied file to settings.php: cp sites/default/default.settings.php sites/default/settings.php . Give the web server write privileges (666 or u=rw,g=rw,o=rw) to the configuration file: chmod a+w sites/default/settings.php . Give the web server write privileges to the sites/default directory: chmod a+w sites/default | |
| 180072673 | Quick install | download and Upload all of the files inside your Drupal folder into the web root folder on your server, create a database, make the /sites/default directory writable (e.g. set to set permissions to 777), run the installer | |
| 180072674 | Quick install for developers: Create the Drupal database | Create an empty database and a user with full access the newly created database for Drupal to use. mysqladmin -u | |
| 180072675 | Quick install for developers: Set permissions for the Drupal database | GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER, CREATE TEMPORARY TABLES, LOCK TABLES ON databasename.* TO 'username'@'localhost' IDENTIFIED BY 'password'; | |
| 180072676 | Install with Drush | Get (only the) Drupal base with Drush, execute the Drush site-install command. The installation profile used can be left out, it defaults to standard, or set to something else. | |
| 180072677 | Get Drupal base with Drush | drush dl drupal --drupal-project-rename=example | |
| 180072678 | Execute the Drush site-install command | cd example; drush site-install standard --db-url=mysql://[db_user]:[db_pass]@localhost/[db_name] --site-name=Example . Use drush help si to see more flags available for the site-install command. | |
| 180072679 | Set up Drupal database with Drush | Drush will create the database for you if the db_user above has the privileges to. By default the UID 1 account is given a username and password of 'admin'. | |
| 180072680 | Change default database login with Drush | You can set the login with flags added to the site-install command: --account-name=admin --account-pass=[useruser_pass] | |
| 180072681 | Apache requirements | Verify Clean-Urls in Apache. Confirm AllowOverride All is in effect, and mod_rewrite is available. | |
| 180072682 | Server migration basics | Check php memory, check DB support, check GD image toolkit support, check php upload_max_filesize, post_max_filesize, check that include_path contains '.' (the working directory), check the error_reporting level, set up cron, check the presence of the .htaccess file | |
| 180072683 | Install contributed modules | Choose the release version that is compatible with your version of Drupal, Access the files (download the .tar.gz or .zip file to your computer) | |
| 180072684 | Install contributed modules manually | Extract the module archive (e.g. execute the command: tar -zxvf modulename-drupalversionnumber.tar.gz); Upload the folder into the sites/all/modules directory; Read the module directions for module-specific configuration; Enable the module; Set up permissions; Adjust settings | |
| 180072685 | Enable contributed modules | Navigate to Administer > Modules or http://example.com/admin/modules. Check the 'Enabled' box next to the module and then click the 'Save Configuration' button at the bottom. Note: If you are updating an existing module, you'll need to click 'update script' at the top of the page or load http://www.example.com/update.php, then click 'Continue' (after making a backup of both your database and 'sites' folder). | |
| 180072686 | Set permissions for contributed modules | Permissions information may be in the instructions that came with the module. Navigate to Administer > Modules and click on the 'Permissions' button for the desired module. You can also do this on the Permissions page (Administer > People > Permissions). Scroll down to see if the module appears in the list and, if it does, give the appropriate permissions to desired roles. | |
| 180072687 | Adjust settings for contributed modules | Most modules will have some type of settings page. It will vary from module to module but if not described in the README.txt file, it can usually be located by navigating to (Administer > Modules) and clicking on the 'Configure' link for that module. Not all modules have settings pages. | |
| 180072688 | Install themes | Download the theme, extract the files, upload the folder, read the directions, enable the theme, make it the active or default theme if desired, save the configuration (e.g. click the 'Save Configuration' button at the bottom of the themes page) | |
| 180072689 | Enable themes | Go to administer > site building > themes. Check the 'Enabled' box next to the theme. | |
| 180072690 | Upload a theme folder | FTP/Copy/SCP your files to the desired themes folder in your Drupal installation. Since the themes folder at the top level of Drupal is typically reserved for Drupal core themes, you should create a sites/all/themes/ directory and put uploaded themes there. If you are running a multi-site installation of Drupal, you can create a themes folder under sites/my.site.folder and put themes there that are specific to a particular site in your installation. Themes that will be shared between all sites should be placed in sites/all/themes. | |
| 180072691 | Download themes | Themes can be found on http://drupal.org/project/themes, as well as some external sites. Make sure the version of the theme matches your version of Drupal. Note that themes labeled "DEV" are in a development stage. They may be written for a previous/current/future version of Drupal, and they are considered unstable and should be handled with care. | |
| 180072692 | Migrate to Drupal | Migration involves mapping data fields from the original application's database into Drupal's database. For some applications this can be a simple task, with tools or scripts available to do the migration. Other applications may have complex database schemas, lack documentation, and are uncommon enough that there are no tools available. | |
| 180072693 | Steps for migrating to Drupal | In the absence of automatic migration tools: You will need to map all your current users into Drupal's users table; Import databases (MySQL, etc.) containing content and users from your previous CMS into Drupal; | |
| 180072694 | Process CCK file types | If your tables are available in your Drupal database, you can use the Table Wizard to expose them to Views, and then use the Migrate module to copy the data from the old columns to the CCK content types. Also, the Node Convert module can convert imported node types to other node types; it supports, at least, CCK fields, book and forum nodes, and probably others like blog, etc. | |
| 180072695 | Import existing databases to Drupal | Export the databases first to CSV (comma-separated values) or similar files. Tools such as phpMyAdmin for MySQL can make this task easier. You can then import these files with import/export modules such as Node Import, User Import, CSV Parser, Migrate, or Transformations (see a module comparison). | |
| 180072696 | Map all current users into Drupal's users table | If you have different roles (for example, read-only, author, editor/reviewer, admin), you will need to assign your users to properly set up and configured roles in Drupal. This can mostly be done through Drupal's admin interface, although if you have a large number of users, you may want to find a way to automate the assignment. Editing each user by hand could be time consuming. If the content being migrated is text, it would likely map into the node and node_revisions tables, with comments in the comments table. | |
| 180072697 | Migrate from Wordpress | The wordpress import takes a feed of your existing wordpress site and generates nodes and vocabularies from that data in your Drupal site. (1) Setup a base Drupal site (see our beginning with drupal articles); (2) Configure it to your new site as much as you can ( you could install an existing theme or modify an existing theme to your preference ); (3) Install the Wordpress Import module and enable it in your module configuration; (4) Follow the instructions in the Wordpress Import module (read the project page and any text files that come with the tarball) and execute the import; (5) If necessary, theme the created nodes from your wordpress import that are generated from your wordpress import. | |
| 180072698 | Migrate from Wordpress: Categories vs. Vocabularies | Wordpress uses the concept of "categories" but in Drupal they are called "Vocabularies", terms form a taxonomy which belong to a vocabulary, but in the end, they are all the same thing, just be aware of the difference in terminogoly however there are many plugins for Drupal that can do very cool things depending on the Vocabulary/Taxonomy (or category) of a post. |
