how to work with drupal
Saturday 6 April 2013
CREATE DRUPAL WEBSITE
Once you have Drupal, it is wise to use all its tools and get the general feel of the CMS. If you are an expert, this should not be a problem but a beginner might feel a bit frustrated in using all the commands. Therefore be patient and create something as a way to learn before really going for your final version of your website
Labels:
create drupal,
drupal sites
Location:
United States
Tuesday 2 April 2013
how to work with drupal
Are you a professional blogger? Then you
must have understood the prominence of WordPress, overshadowing Drupal.
Many professional bloggers are now converting their web pages from
Drupal to WordPress. Reason? WordPress is easier, better, and
user-friendlier. Many tech savvy people may argue that Drupal is the
ideal place for technically sound ones; however, there are many, who
cite for the struggle, they have faced during posting their blogs in
Drupal. There are a couple of reasons, why many web users are switching
from Drupal to WordPress. If you are interested to imbibe the process
for a better blogging experience, here are some tips on how to migrate
from Drupal to WordPress, mentioned below. Before landing on the topic,
let’s take a look why you might need the switch.
Why WordPress is better than Drupal:
WordPress is quicker than Drupal. The tasks that you can perform on Drupal, can be executed much faster on WordPress.
WordPress has the autosave option, which takes care of your incomplete content, while on Drupal, there is no such option in the text editor.
WordPress offers more Plugins.
WordPress has the Thesis theme, which takes extra care to make your page rank higher in search engines.
There is WYSIWYG (What You See Is What You Get) editor on WordPress, with which you don’t have to take extra burdens to add HTML links.
Moderating comments is easier on WordPress.
How to switch to WordPress from Drupal:Migrating from Drupal to WordPress is not an easy task. You first need to work on the offline copies in the archive. Dump Drupal database from your system and import it into a fresh database. You can use MySQL for this conversion.
Install WordPress into your system, using the old database server, where the Drupal database is kept. You now have Drupal and WordPress running on the same server but in separate database. Don’t forget to give unique names to the databases.
You may need some programming knowledge with MySQL and PHP to work on Drupal. You can enable PHP on Drupal following the path:
/drupal/admin/settings/filters
You need to change the location; else Google will consider it as duplicate content. With slight coding, you can inform Google that the content is being shifted from Drupal to WordPress. After the switch, whenever, you need to post something, just enable ‘Input Format’.
This is the basic procedure of migrating from Drupal to WordPress. Now log in to WordPress site and you will supposedly find all your contents and posts along with the comments on your new WordPress site. If you find all your posts and comments in the migrated database, you can dump the WordPress database and import the archive into a new database on the server. Now a new WordPress should be installed and configured on the server so that you can use the new database properly.
Do you use Drush and Drupal? Then you may want to read this:
What are your favorite/most used commands with Drush, an open source command line utility that we recommend using to build and maintain your Drupal website. Here is our top 9 most used commands on how to use Drush with Drupal, an open source Content Management System (CMS). This is too good of a list to not share with the community.
Drush is by far my favorite tool when it comes to working with Drupal. While grapical tools are often easier to use initially, command-line tools more often give you more power and control, the drush project is an active Drupal project with a major release (3.x) in the works. While it does change some of the basic command names, it organizes and restructures the design to make it easier to extend. The new release also introduces new features/commands, some of which were prior add-ons.
My Favorite/Most Used Commands
Drush provides a number of commands that permit you do perform drupal installation, maintenance, and status operations. Among my most frequently used commands/operations:
1. View the update status of modules
2. Update site modules
3. Clearing caches
4. Download drush modules
5. Enabling modules
6. Disabling modules
7. Download drush to create a new installation
8. Get the list of enabled (disabled) modules
9. Get the list of and status of a specific module
In v2.x, I would do this by:
1. drush -n update
2. drush update
3. drush clear cache
4. drush download m1 m2 m3
5. drush enable m1 m2 m3 (I often use the -y option in order to skip the confirmation)
6. drush disable m1 m2 m3 (I often use the -y option in order to skip the confirmation)
7. drush download (followed by renaming the drupal-N.nn directory to a more meaningful name)
8. drush statusmodule | grep ‘Enabled’ (or ‘Disabled’)
9. drush statusmodule | grep ‘my guess at module name’
Now, with the formal release of v3.x. The revised commands for the above are:
1. drush -n pm-update
2. drush pm-update
3. drush cache-clear all (all, theme, menu, css+js are the available options)
4. drush pm-download m1 m2 m3
5. drush pm-enable m1 m2 m3
6. drush pm-disable m1 m2 m3
7. drush pm-download –drupal-project-rename=my.sitename drupal
8. drush pm-list –type=module –status=enabled
9. drush pm-list –type=module –package=”Package Name” (if you know the exact package name) ordrush pm-list –type=module | grep ‘part of package name or module name’ (if you are not sure of a package or module name)
Your site is ready.
www.creatorshadow.com
Why WordPress is better than Drupal:
WordPress is quicker than Drupal. The tasks that you can perform on Drupal, can be executed much faster on WordPress.
WordPress has the autosave option, which takes care of your incomplete content, while on Drupal, there is no such option in the text editor.
WordPress offers more Plugins.
WordPress has the Thesis theme, which takes extra care to make your page rank higher in search engines.
There is WYSIWYG (What You See Is What You Get) editor on WordPress, with which you don’t have to take extra burdens to add HTML links.
Moderating comments is easier on WordPress.
How to switch to WordPress from Drupal:Migrating from Drupal to WordPress is not an easy task. You first need to work on the offline copies in the archive. Dump Drupal database from your system and import it into a fresh database. You can use MySQL for this conversion.
Install WordPress into your system, using the old database server, where the Drupal database is kept. You now have Drupal and WordPress running on the same server but in separate database. Don’t forget to give unique names to the databases.
You may need some programming knowledge with MySQL and PHP to work on Drupal. You can enable PHP on Drupal following the path:
/drupal/admin/settings/filters
You need to change the location; else Google will consider it as duplicate content. With slight coding, you can inform Google that the content is being shifted from Drupal to WordPress. After the switch, whenever, you need to post something, just enable ‘Input Format’.
This is the basic procedure of migrating from Drupal to WordPress. Now log in to WordPress site and you will supposedly find all your contents and posts along with the comments on your new WordPress site. If you find all your posts and comments in the migrated database, you can dump the WordPress database and import the archive into a new database on the server. Now a new WordPress should be installed and configured on the server so that you can use the new database properly.
Do you use Drush and Drupal? Then you may want to read this:
What are your favorite/most used commands with Drush, an open source command line utility that we recommend using to build and maintain your Drupal website. Here is our top 9 most used commands on how to use Drush with Drupal, an open source Content Management System (CMS). This is too good of a list to not share with the community.
Drush is by far my favorite tool when it comes to working with Drupal. While grapical tools are often easier to use initially, command-line tools more often give you more power and control, the drush project is an active Drupal project with a major release (3.x) in the works. While it does change some of the basic command names, it organizes and restructures the design to make it easier to extend. The new release also introduces new features/commands, some of which were prior add-ons.
My Favorite/Most Used Commands
Drush provides a number of commands that permit you do perform drupal installation, maintenance, and status operations. Among my most frequently used commands/operations:
1. View the update status of modules
2. Update site modules
3. Clearing caches
4. Download drush modules
5. Enabling modules
6. Disabling modules
7. Download drush to create a new installation
8. Get the list of enabled (disabled) modules
9. Get the list of and status of a specific module
In v2.x, I would do this by:
1. drush -n update
2. drush update
3. drush clear cache
4. drush download m1 m2 m3
5. drush enable m1 m2 m3 (I often use the -y option in order to skip the confirmation)
6. drush disable m1 m2 m3 (I often use the -y option in order to skip the confirmation)
7. drush download (followed by renaming the drupal-N.nn directory to a more meaningful name)
8. drush statusmodule | grep ‘Enabled’ (or ‘Disabled’)
9. drush statusmodule | grep ‘my guess at module name’
Now, with the formal release of v3.x. The revised commands for the above are:
1. drush -n pm-update
2. drush pm-update
3. drush cache-clear all (all, theme, menu, css+js are the available options)
4. drush pm-download m1 m2 m3
5. drush pm-enable m1 m2 m3
6. drush pm-disable m1 m2 m3
7. drush pm-download –drupal-project-rename=my.sitename drupal
8. drush pm-list –type=module –status=enabled
9. drush pm-list –type=module –package=”Package Name” (if you know the exact package name) ordrush pm-list –type=module | grep ‘part of package name or module name’ (if you are not sure of a package or module name)
Your site is ready.
www.creatorshadow.com
Subscribe to:
Posts (Atom)