[theme-reviewers] How do the theme updates work?

[Emil Uzelac]

FYI: http://ottopress.com/2013/language-packs-101-prepwork


On Sat, Oct 19, 2013 at 4:38 PM, Edward Caissie <edward.caissie at gmail.com>wrote:

>
> On Sat, Oct 19, 2013 at 10:13 AM, Otto <otto at ottodestruct.com> wrote:
>
>> As it turns out, it was extremely easy to test, and I was right. The
>> random file (I made an aaa.txt file) was removed when I updated the
>> theme.
>>
>> No bugs here. It works the way I thought it did. Upgrading themes
>> removes the whole theme directory before unpacking the new theme.
>> Files added to a theme will be removed too.
>>
>
> I'll admit to not testing it recently as I have always found it to act as
> I described earlier but after re-testing I see that it does indeed behave
> the same as plugin updates. I'm happy for the consistency. Although this
> does pose a concern as one was formerly able to create custom
> page-templates for a theme and load them directly into the theme folder.
> This now forces end-users to either create a Child-Theme to accomplish this
> or FTP the custom page templates after every theme update neither of which
> seems very UX friendly for what was essentially a simple idea.
>
> I know this wasn't the case in the past but as I'm waiting to board a
> plane at SFO I'll have to look into this later, as I expect this behavior
> to break one of my plugins that relied on the theme update process to not
> be a destructive one.
>
>
> Edward Caissie
> aka Cais.
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20131023/6ee84716/attachment-0001.html>