And another update ...
I looked in my /etc/apache/sites-available and /etc/apache/sites-enabled.
in enabled:
lrwxrwxrwx 1 root root 28 Aug 21 17:59 101-mdowney ->
../sites-available/mdowney-1
So the newly generated config file was not being used.
I edited mdowney-1 to have
# Alias /wp-content /var/lib/wordpress/wp-content
Alias /wp-content /srv/www/wp-content
and restarted. In this case, with no link from
/var/lib/wordpress/wp-content/themes/business-pro to
/srv/www/wp-content/themes/business-pro, the blog does not use the theme,
and although the theme does show up in the themes page, it is blank. IE,
there is a blank square as placeholder for the business-pro theme, and it
has the right name and the activate etc links.
When I put the link back in /var/lib/wordpress/wp-content/themes, then the
blank square fills in with the business-pro image.
I activated the business-pro theme (funny, I thought I had left it
activated last time), and it activates. But, now the built-in themes
twenty-twelve and twenty-thirteen have blank placeholders (!)
Of course those links in /var/lib/wordpress/wp-content/themes are pointing
to /usr/share/wordpress area, not /srv/www area:
root@rhino:/var/lib/wordpress/wp-content/themes# ls -la
total 8
drwxr-xr-x 2 root root 4096 Aug 23 14:03 .
drwxr-xr-x 7 root root 4096 Aug 21 16:24 ..
lrwxrwxrwx 1 root root 39 Aug 23 13:53 business-pro ->
/srv/www/wp-content/themes/business-pro
lrwxrwxrwx 1 root root 48 Aug 21 16:41 index.php ->
/usr/share/wordpress/wp-content/themes/index.php
lrwxrwxrwx 1 root root 53 Aug 21 16:41 twentythirteen ->
/usr/share/wordpress/wp-content/themes/twentythirteen
lrwxrwxrwx 1 root root 51 Aug 21 16:41 twentytwelve ->
/usr/share/wordpress/wp-content/themes/twentytwelve
So then I removed the sites-enabled/101-mdowney link and put in
sites-enabled/100-mdowney -> ../sites-available/mdowney and restarted apache.
Got this error on apache2ctl -t:
bjb@rhino:/etc/apache2/sites-enabled$ sudo apache2ctl -t
Syntax error on line 11 of /etc/apache2/sites-enabled/100-mdowney:
Invalid command 'VirtualDocumentRoot', perhaps misspelled or defined by a
module not included in the server configuration
Action '-t' failed.
The Apache error log may have more information.
Overall, I find having an extra directory /srv/www/wp-content even more
confusing than just sticking to /var/lib/wordpress/wp-content. If there
is some global variable I can set in /etc/wordpress/config-mdowney.php,
I'll just do that and stop there.
So now I have apache config:
<VirtualHost *:80>
ServerName mdowney
DocumentRoot /usr/share/wordpress/
DirectoryIndex index.php index.html
ErrorLog /var/log/apache2/mdowney-1-error.log
TransferLog /var/log/apache2/mdowney-1-access.log
# wp-content in /var/lib/wordpress/wp-content
Alias /wp-content /var/lib/wordpress/wp-content
# Alias /wp-content /srv/www/wp-content
<Directory /usr/share/wordpress>
Options FollowSymLinks
Order allow,deny
Allow from all
</Directory>
<Directory /var/lib/wordpress/wp-content>
# <Directory /srv/www/wp-content>
Options FollowSymLinks
Order allow,deny
Allow from all
</Directory>
</VirtualHost>
I have the following /etc/wordpress/config-mdowney.php
<?php
# Created by setup-mysql
define('DB_NAME', 'mdowney');
define('DB_USER', 'mdowney');
define('DB_PASSWORD', 'tswT7GQq');
define('DB_HOST', 'localhost');
define('SECRET_KEY', '3TSASjfu0UjAbKu5Q1j4EH9m8zpUaRg88w1oSD8wDP');
# define('WP_CONTENT_DIR', '/srv/www/wp-content/mdowney');
define('WP_CONTENT_DIR', '/var/lib/wordpress/wp-content');
?>
and I have the theme dropped into /var/lib/wordpress/wp-content/themes,
also I moved aside /srv/www/wp-content to another name to avoid
contamination, restarted apache2.
It works. The main blog page comes up with the right theme, and the
wp-admin themes page shows all the themes, thumbnails included.
I think the thing missing from my original config was the
define('WP_CONTENT_DIR', '/var/lib/wordpress/wp-content')
directive.
I do note the good practice of putting mdowney's wp-content in its own
directory ("/srv/www/wpcontent/mdowney") and next time I have to set up
wordpress, I'll try again with the /srv/www arrangement.
Thanks for your help, and I'll be happy to try stuff out if you need me to.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
