Merge lp://qastaging/~evarlast/serverguide/wordpress into lp://qastaging/~ubuntu-core-doc/serverguide/quantal

i don't think i'm using lp correctly. Is rev 87 showing in this merge req?

Thanks for your very quick reply and re-submit on this. Now it passes the validiate step.
I looked at the compiled html and the pdf.
Myself, I have never installed wordpress before, I followed your procedure. Here are my notes:

Should this part:

"Enable this new WordPress site

cd /etc/apache2/sites-enabled
sudo ln -s ../sites-available/wordpress"

Be this instead:

"Enable this new WordPress site

sudo a2ensite wordpress"

I relaize that "a2ensite" only does what is mentioned, but it is the preferred method (I think).

At the apache restart step, I did reload instead and got:

doug@s15:/etc/apache2/sites-available$ sudo service apache2 reload
 * Reloading web server config apache2
[Sat Feb 23 15:19:58 2013] [warn] The Alias directive in /etc/apache2/sites-enabled/wordpress at line 2 will probably never match because it overlaps an earlier Alias.

Indeed, there is a directory that, I think, will be hit first:

doug@s15:~/wordpress$ ls -l -d /usr/share/wordpress/wp-content
drwxr-xr-x 5 root root 4096 Feb 23 15:07 /usr/share/wordpress/wp-content

For this:

"Your new WordPress can now be configured by visiting http://localhost/blog/wp-admin/install.php. Fill ..."

But this is the serverguide, and I have no GUI and no browser. ??

From another computer, can I browse to:

http://s15.smythies.com/blog/wp-admin/install.php

? No, I get 404 not found error.

The file is there:

doug@s15:~/wordpress$ ls -l /usr/share/wordpress/wp-admin/install.php
-rw-r--r-- 1 root root 10329 Jan 16 2012 /usr/share/wordpress/wp-admin/install.php

Perhaps because of the earlier alias warning. (?)
(note: s15 is a LAN only test computer, not available on WAN)

I do not have a way to try "http://localhost/blog/wp-admin/install.php" to see if it works.
I suspect this might be related to that file config-localhost.php, but am not sure how to prove it.

For files that do not exsist already should "Open" be changed to "Create"?

Should it be spelled out for the user to replace "yourpasswordhere" with their own desired password?

I am trying to use w3m to access the install.php from localhost. It seems to be working, I just have to learn how to use w3m properly.

I forgot to mention, that the test computer is actually 12.04 and not 12.10. I do not have an Ubuntu server 12.10 computer at the moment.

yes, a2ensite should be used. I'll update.

Its not obvious that the instructions and wordpress packaging use a config per virtual host. I'll update the docs to state as much.

Thanks for continued quick work.
I got frustrated trying to continue with w3m on the server itaelf.
So, (after more study) I copied /etc/wordpress/config-localhost.php
to config-s15.smythies.com.php . Then I was able to access and complete the install via http://s15.smythies.com/blog/wp-admin/install.php .
Now it seems to be working, but complaining about no theme and actual blog pages are blank. This could well be because I am hurrying to much and don't know what I'm doing.

Peter M: Could you please comment on the references.
I am wondering about: The link to someone's own web site; The Ubuntu community link.

Here is a reference quote from a "needs fixing" reject of one of my MP's a year ago:

"I do not like the references used here. We should always strive to point users to definitive resources (typically upstream), not the community documentation [1] nor the forums [2]."

Jay: I made a mistake above. There are 62 other links to Ubuntu community pages in the server guide. The issue (if I had bothered to re-read the entire old thread) was with a link I trying to give to an Ubuntu forums thread. Sorry for any confusion.

Yes, I re-confirm my above position on references.

I removed a blog link, should I just remove all of the references link?

I really don't like this policy. It is dishonest. As a publisher of non fiction, I want to cite my references. Blogs and community documentation are my references.

Who set this policy and how can I urge them to reconsider?

Jay, as sole driver for the Server Guide Project, I set this policy.

The "references" you speak of should instead be thought of as "further reading". Official documentation, such as this Guide, should ideally not include links to unofficial documentation.

Understood.

I've been in academic writing for too much lately where one always cites references. From the point of view that this is documentation for a product, it makes sense to not reference community documentation.

The link that has been in debate on this thread no longer works for me. I went back to the earlier version of this wordpress document, and the link no longer worked there either. I took out the whole reference.

I also changed this paragraph:

        <para>Your new <application>WordPress</application> can now be configured by visiting
<ulink url="http://localhost/blog/wp-admin/install.php">http://localhost/blog/wp-admin/install.php</ulink>.
Fill out the Site Title, username, password, and E-mail and click Install WordPress.
        </para>

To:

        <para>Your new <application>WordPress</application> can now be configured by visiting
            <ulink url="http://localhost/blog/wp-admin/install.php">http://localhost/blog/wp-admin/install.php</ulink>.
            (Or <ulink url="http://NAME_OF_YOUR_VIRTUAL_HOST/blog/wp-admin/install.php">http://NAME_OF_YOUR_VIRTUAL_HOST/blog/wp-admin/install.php</ulink>
            if your server has no GUI and you are completing <application>WordPress</application>
            configuration via a web browser running on another computer.) Fill out the Site Title,
            username, password, and E-mail and click Install WordPress.
        </para>

I am not an expert, but the edits to mail.xml look O.K. to me.
/etc/dovecot/conf.d/10-auth.conf already has this line:

auth_mechanisms = plain

So does it need the line 222 edit below also? Adds this:

auth_mechanisms = plain login

?

Changing the "auto_machanisms" code area to:

            <para>
            In order to let <application>Outlook</application> clients use SMTP-AUTH, in the <emphasis>authentication mechanisms</emphasis>
            section of /etc/dovecot/conf.d/10-auth.conf change this line:
            </para>

<programlisting>
auth_mechanisms = plain
</programlisting>

            <para>
            To this:
            </para>

<programlisting>
auth_mechanisms = plain login
</programlisting>

See raring revision 104 for the carry forward edits of the Wordpress section. The main.xml had several things already done on the 13.04 (raring) branch, so will take longer to sort out.