I was using the theme from the wordpress-theme-twentyfifteen debian package,
which installed to /usr/share/wordpress/wp-content/themes/twentyfifteen,
with a symlink to that created in /var/lib/wordpress/wp-content/themes/.

I had customized colours and added a logo to the theme using the wordpress
admin web interface, which I believe just saves the customizations in the
wordpress database. Upon upgrade from wordpress 4.1 to wordpress 4.7, when I
logged on as the admin, I was prompted to perform a wordpress DB upgrade,
which I accepted. After that, when I went to my wordpress page, it had
reverted to the default look from the twentyfifteen theme. I assume the DB
upgrade failed to preserve the customizations. I was able to redo my colour
and logo changes in the admin web interface.

On Fri, Jun 30, 2017 at 10:46:19PM +0000, Craig Small wrote:
> 
> 
> On Fri, Jun 23, 2017 at 8:39 AM Scott Barker <sc...@mostlylinux.ca> wrote:
> 
>     I had a working install of wordpress 4.1+dfsg-1+deb8u14 on jessie, with
>     customized colours, logos, etc. Upon updating to stretch and wordpress
>     4.7.5+dfsg-2, all theme customizations were lost.
> 
> This sounds like where you had put these themes wasn't quite where we 
> expected.
> They should still be there though.
> Do you know what directory these files were?
> 
> Also, when you mean customization, how were you doing this? Was it adjusting
> the existing theme (that is generally a bad idea) or you had your own themes
> you downloaded elsewhere.
> What do you mean by "lost"? It went back to the default look? The themes 
> failed
> to work? The adjustments to the themes reverted? Or perhaps wordpress just 
> gave
> a blank white screen.
> 
> Generally these sorts of problems are an interaction of WP_CONTENT_DIR defined
> in /etc/wordpress and the home directory defined in apache.
> 
>  - Craig
> 
> 
> 
> 
> 
> --
> Craig Small             https://dropbear.xyz/     csmall at : enc.com.au
> Debian GNU/Linux        https://www.debian.org/   csmall at : debian.org
> Mastodon: @smalls...@social.dropbear.xyz             Twitter: @smallsees  
> GPG fingerprint:      5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5

-- 
Scott Barker

Reply via email to