Package: wordpress
Version: 2.0.3-1
Severity: minor

I used the default apache.conf as my configuration, and have several
blogs setup (three) on different hostnames.  Noticed tonight that if the
"www" part was dropped the url returns an error that is either a 404, or a
php error that it cannot find a configuration file.  (One blog had the
document root pointed to a specific directory)

The first problem is actual the first part of the total problem.  I
solved it by changing the default "VirtualDocumentRoot /srv/www/%0"
given in the example apache.conf file so that the "%0" has the full path
(otherwise you are relying on the client to provide that name in the
Host: field of the HTTP request).

The second part, needs "UseCanonicalName    Off" changed to
"UseCanonicalName    On".  Then the /etc/wordpress/wp-config.php line 6
needs to use SERVER_NAME instead of HTTP_HOST.

This is minor, and I'm not sure that way I fixed it would be
the right way for the package. My fix could lead to users
needing to login in twice (assuming I understand UseCanonicalName
correctly in the Apache2 docs).  Someone with a little more apache and
php knowledge could probably figure out a better way.  I'm willing to
test any changes and if I find a better way to fix this I'll post back
to the bug.

p.s. My email address given will work, but there might be a week or so down
time at the end of August 2006 due the server moving.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (400, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.32
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages wordpress depends on:
ii  apache2-mpm-prefork [htt 2.0.54-5        traditional model for Apache2
ii  libapache2-mod-php4      4:4.3.10-16     server-side, HTML-embedded scripti
ii  mysql-client-4.1 [virtua 4.1.11a-4sarge5 mysql database client binaries
ii  php4                     4:4.3.10-16     server-side, HTML-embedded scripti
ii  php4-mysql               4:4.3.10-16     MySQL module for php4

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to