Drupal 6 Post Installation Status
It's worth noting before we continue further that it is often beneficial to have several development sites in order to play around with different things without mucking up other work. The process outlined so far in this chapter can be repeated as many times as you like to set up as many development sites as you like—simply create a new database (or, alternatively, provide any new Drupal installation with a table pre x in the Advanced options section) and add the Drupal files to the htdocs directory (ensuring they have a unique name) before browsing the new folder and repeating the installation process.
Whatever you decide, the next step is to click on the your new site link to bring up the default administration page (refer to the following figure):
Quite conveniently, we have everything we need to do laid out in four simple steps and this is more or less the route we will follow in order to get everything up and running too.
Bear in mind that this page will be replaced once you start adding content and modifying the site; it is only a temporary placeholder. The first port of call is the administration section, so click there. At this point it is quite likely that there will be another one of those red error messages urging you to check the status report.
If that is the case, then go ahead and do so—you will no doubt be presented with something that looks similar to the following screenshot (hopefully with less red involved):
This page displays information about the fundamentals of the Drupal installation. Anything showing in red or yellow needs attention. At the moment, the Cron maintenance tasks seems to be in trouble, but with a close inspection of the reasons for the error, you will see that the problem is not that dif cult to solve—the cron has not been run.
To deal with the cron error, click on the run cron manually link. This executes the cron script and we are one down with one to go.
Next, click on the File system settings page link. This will bring up the following dialog that allows you to specify where and how les should be uploaded to and from during the course of the site's normal operation:
Unless you specifically know whether or not the site will require public or private downloads, don't worry about any of these settings for now—files are discussed in more depth in Chapter 4. Choose the Public download method and click on the Save configuration button before going back to the server status report (click on Reports and then Status Report in the main menu) to confirm that the installation now has a clean bill of health.
Before we move ahead to the customization and configuration topics, it is important that we glance over Drupal to get a feel of how everything is organized.
Whatever you decide, the next step is to click on the your new site link to bring up the default administration page (refer to the following figure):
Quite conveniently, we have everything we need to do laid out in four simple steps and this is more or less the route we will follow in order to get everything up and running too.
Bear in mind that this page will be replaced once you start adding content and modifying the site; it is only a temporary placeholder. The first port of call is the administration section, so click there. At this point it is quite likely that there will be another one of those red error messages urging you to check the status report.
If that is the case, then go ahead and do so—you will no doubt be presented with something that looks similar to the following screenshot (hopefully with less red involved):
This page displays information about the fundamentals of the Drupal installation. Anything showing in red or yellow needs attention. At the moment, the Cron maintenance tasks seems to be in trouble, but with a close inspection of the reasons for the error, you will see that the problem is not that dif cult to solve—the cron has not been run.
To deal with the cron error, click on the run cron manually link. This executes the cron script and we are one down with one to go.
Next, click on the File system settings page link. This will bring up the following dialog that allows you to specify where and how les should be uploaded to and from during the course of the site's normal operation:
Unless you specifically know whether or not the site will require public or private downloads, don't worry about any of these settings for now—files are discussed in more depth in Chapter 4. Choose the Public download method and click on the Save configuration button before going back to the server status report (click on Reports and then Status Report in the main menu) to confirm that the installation now has a clean bill of health.
Before we move ahead to the customization and configuration topics, it is important that we glance over Drupal to get a feel of how everything is organized.
No comments for "Drupal 6 Post Installation Status"
Post a Comment