[theme-reviewers] Theme Updates Logic

[Edward Caissie]

You can also make the Child-Theme version extremely high ... add 1000 or
something similar to the base version, such as version 1.0 would be 1001.0;
I have seen very few cases were this method does not work to protect the
Child-Theme.

Also, I see it as the responsibility of the Child-Theme author to insure
there are not conflicts with repository hosted themes. Although Shelter and
Multi are live in Extend, before I named them I checked to make sure their
names were not currently in use elsewhere. This is not to mention the
discussion that was had some time ago about naming conventions for
Child-Themes that included the Parent-Theme name, part of the reason being
for examples such as this ... not that I really supported the argument but
it does hold up well.


Cais.


On Sun, Oct 30, 2011 at 5:35 PM, Emil Uzelac <emil at themeid.com> wrote:

> We can't add something to check Theme name and author's name, or that's
> something over our heads? And as I said this isn't for us ;)
>
> *----*
> *Emil Uzelac* | ThemeID | T: 224-444-0006 | Twitter: @EmilUzelac | E:
> emil at themeid.com | http://themeid.com
> Make everything as simple as possible, but not simpler. - Albert Einstein
>
>
>
> On Sun, Oct 30, 2011 at 4:25 PM, Otto <otto at ottodestruct.com> wrote:
>
>> PREFIX.
>>
>> Seriously. There is no magic bullet that will fix this sort of thing.
>> Any solution you think of I can come up with a reasonable counter to.
>>
>> Always, always, prefix stuff. All stuff. Always.
>>
>> My preferred method for custom stuff is to use the domain name.
>> "Ottopress.com Theme" and similar.
>>
>> -Otto
>>
>>
>>
>> On Sun, Oct 30, 2011 at 4:16 PM, Emil Uzelac <emil at themeid.com> wrote:
>> > Hey Guys,
>> > Is there a way of re-adjusting Theme updates features to check for more
>> than
>> > just Theme names? And this is what I mean.
>> http://cl.ly/022X2A1L2t2U2S371k00
>> > I created a Child Theme for a client and called it "Simply", now since
>> there
>> > is a Theme with the same name in repository and the version is higher
>> than
>> > 1.0 the update comes up. Yes, simple prefix will do the trick, but many
>> > others out there will not know that and you know that once they click
>> the
>> > "Update Themes" the original will be wiped out. I strongly believe that
>> we
>> > should find some kind of logic to protect same name Themes and look
>> outside
>> > of the "box" as well. Maybe to match author's name as well?
>> > What do you think?
>> > P.S. Also (not really for Theme Reviewers, but...):
>> >
>> > Themes
>> >
>> > The following themes have new versions available. Check the ones you
>> want to
>> > update and then click “Update Themes”.
>> >
>> > (Please Note: Any customizations you have made to theme files will be
>> lost.
>> > Please consider using child themes for modifications.)
>> >
>> > That note is bit misleading as well, because this is indeed a Child
>> Theme.
>> >
>> > Emil
>> > ----
>> > Emil Uzelac | ThemeID | T: 224-444-0006 | Twitter: @EmilUzelac | E:
>> > emil at themeid.com | http://themeid.com
>> > Make everything as simple as possible, but not simpler. - Albert
>> Einstein
>> >
>> > _______________________________________________
>> > theme-reviewers mailing list
>> > theme-reviewers at lists.wordpress.org
>> > http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>> >
>> >
>> _______________________________________________
>> theme-reviewers mailing list
>> theme-reviewers at lists.wordpress.org
>> http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>>
>
>
> _______________________________________________
> 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/20111030/e9065489/attachment-0001.htm>