On Thu, Aug 21, 2014 at 07:16:32PM -0400, Brenda J. Butler wrote:
/var/lib/wordpress/wp-content/themes/business-pro/
/var/lib/wordpress/wp-content/themes/business-pro/index.php
Did you use the setup-mysql script or config it yourself?
Should be going into /srv/www/wp-content/example.com/themes
Craig,
Thanks for looking into this.
I had the impression from reading the README.Debian that the setup-mysql
script was optional (as long as you took similar steps to do the setup
yourself).
For instance, the README.Debian uses the word beware when saying
it will put the wp-content in
After sending that last email, I tried activating the theme, removing the
link from /var/lib/wordpress/wp-content/themes/business-pro and then
visiting the site. The page was blank.
So I thought right, I didn't update the apache config to point to the new
wp-contents directory. I looked in the
One last update - I must have failed to
a) switch the theme
b) restart apache after changing apache config
Now I tried again - switch the theme and restart apache - the main blog
page is blank (with no link from
/var/lib/wordpress/wp-contents/themes/business-pro to
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
I got my original config-mdowney.php file by copying
/usr/share/wordpress/wp-config-sample.php to /etc/wordpress/wp-config.php
(as instructed in wp-config-sample.php and in README.Debian) and editing
the first few variables - there is no mention of WP_CONTENT_DIR in there
so never knew to set it.
On a fresh new install of wordpress (Installed: 3.6.1+dfsg-1~deb7u4)
on my Debian wheezy machine, I added a new theme that I downloaded
from the interwebs. I unpacked it into /var/lib/wordpress/wp-content/themes
and some example new paths are:
/var/lib/wordpress/wp-content/themes/business-pro/
7 matches
Mail list logo
