URL: http://drupal.org/upgrade/backing-your-site-command-line
1) The instructions show to backup are not clear (second line should be split):
This:
-------
cd drupal_site/
wget http://cvs.drupal.org/viewcvs/*checkout*/drupal/contributions/sandbox/dr... chmod +x drupalsqldump.sh
-------
should be modified into:
-------
cd drupal_site/
wget http://cvs.drupal.org/viewcvs/*checkout*/drupal/contributions/sandbox/dr...
chmod +x drupalsqldump.sh
-------

2) The following text contains escaped greater than signs '>' instead of '>'. In addition, the previous instructions indication the the current directory is already drupal_site, so this part of the path should be removed.
This:
------------
* If you are running a version of Drupal that is 4.6 or newer, then enter the following:

./drupalsqldump.sh drupal_site/sites/default/settings.php > backup/backup.sql
* If you are running a version of Drupal 4.5 or older, run the following:

./drupalsqldump.sh drupal_site/includes/conf.php > backup/backup.sql
------------
should be modified into:
------------
* If you are running a version of Drupal that is 4.6 or newer, then enter the following:

./drupalsqldump.sh sites/default/settings.php > backup/backup.sql
* If you are running a version of Drupal 4.5 or older, run the following:

./drupalsqldump.sh includes/conf.php > backup/backup.sql
------------

3) The instructions should also explain how to recover once something went wrong:
-------
cd drupal_site/
wget http://cvs.drupal.org/viewcvs/*checkout*/drupal/contributions/sandbox/dr...
chmod +x drupalsql.sh
./drupalsql.sh sites/default/settings.php < backup/backup.sql
-------

Comments

pnm’s picture

pnm commented

#1 is done, but #2 and #3 remain.

pnm’s picture

pnm commented

#2 done.

I'm trying to work on #3, but it seems difficult to structure this page without headings, as suggested by the Handbook style guide. There are in there around what are essentially the headings. Should I just insert another of those?

senpai’s picture

senpai commented

PNM said: I'm trying to work on #3, but it seems difficult to structure this page without headings, as suggested by the Handbook style guide.

I'm having much the same trouble with editing certain pages which would normally require some sort of a document structure. Headings are a normal part of written, printed documentation, and to purposefully avoid them is catastrophic to the casual reader.

Out of sheer curiosity, and without pushing any agenda, what is the purpose of avoiding Headings on Handbook pages?
--
Senpai

sepeck’s picture

sepeck commented


Historical. You can read the long threads about the issue from very passionate people about 18 months ago. It has to do with theming, exporting and importing content and misc other ideas.

Now it's about being consistent.

pnm’s picture

pnm commented

Are you suggesting that I just add another to make a heading without making a heading?

stevenpatz’s picture

stevenpatz
he/him
commented

closing out the bold?

senpai’s picture

senpai commented
Status: Active » Fixed

Yes, for now, just use another <strong> tag as a heading.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.