[theme-reviewers] Option to create child theme from theme option

[Melissa Oveson]

+1 to Chip's answer

> On Jan 21, 2014, at 3:58 PM, Chip Bennett <chip at chipbennett.net> wrote:
> 
> You're conflating two different things here - the second being completely different from the first - and then trying to apply what I said about the first to the second. That doesn't work.
> 
> Of *course* a Theme can have appropriate uses of custom queries. But those custom queries would be known, not arbitrary: querying a certain category term, or post_format term, or whatever, to display in some known, Theme-defined way. Themes do that all the time, and doing so is perfectly fine.
> 
> That's entirely different from what you were talking about before: custom page template that allows the user to define *arbitrary* custom queries, displayed in an *arbitrary* way. That's Plugin territory. Why? Because the *user* is defining the query/relationship/manner of display of the content. The output of that effort is something that a user would reasonably want to retain when switching Themes (and nothing about that output is in any way specific to the Theme).
> 
> 
>> On Tue, Jan 21, 2014 at 4:56 PM, emin ozlem <eminozlem at gmail.com> wrote:
>> I think "custom page template" could be out of option but "custom query" should definitely not qualify as PT. For example if you have a slider, widget or anything like that in your theme you'd definitely want to use a custom query to display certain posts in there.
>> For example your theme has a custom "portfolio" styled display, and you'd want to show posts from "portfolio" category, or a selected category, cant you do that ? I havent checked all the themes, but i am pretty sure there must be themes doing that kind of thing.
>> 
>> I dont know why are theme guidelines are so restrictive. I get the ones that involve "added functionality","modifiyng / adding content" ; since those would cause the loss off those functionalities or contents and would cripple number of plugins. But as for "displaying" of existing content differently, it should be more open.
>> 
>> 
>> 2014/1/21 Chip Bennett <chip at chipbennett.net>
>>> A custom page/custom query creator is *definitely* Plugin territory.
>>> 
>>> 
>>> On Tue, Jan 21, 2014 at 3:47 PM, emin ozlem <eminozlem at gmail.com> wrote:
>>>>  I think this shouldnt fall into plugin territory since there would be no content loss upon deactiivation. If we are to exclude every "functionality" from themes, what are the purpose of themes, just picking colors ?
>>>> 
>>>> For example I was preparing a "custom page creator", you would choose from select boxes as such;
>>>> I want to create a page that displays "posts | custom_p_type" from "cat1-cat2" ordered by"ID | date" etc... you get the idea.
>>>> 
>>>> Creating page-templates are a pain for the average user. This "functionality" i am planning not only makes it easier; but also prevents data loss. Because the creator wont create new page-* files but instead it will use the default page.php file and get the query parameters from an option.
>>>> 
>>>> Would that too also fall into plugin territory ?
>>>> 
>>>> 
>>>> 2014/1/21 Emil Uzelac <emil at uzelac.me>
>>>>> This seems like plugin-territory to me.
>>>>> 
>>>>> 
>>>>>> On Tue, Jan 21, 2014 at 1:29 PM, Faishal Saiyed <saiyedfaishal at gmail.com> wrote:
>>>>>> Hi,
>>>>>> 
>>>>>> I am reviewing one theme and they give one section call "One-Click Child Themes" in theme option. using that setting i can create child theme by providing name. 
>>>>>> 
>>>>>> I will create that name directory in wp-content theme directory and create 3 files
>>>>>> 1. style.css
>>>>>> 2. screenshoot.png
>>>>>> 3. function.php
>>>>>> 
>>>>>> I feel like it is not part of presentation , it is a part of functionality. 
>>>>>> 
>>>>>> But i want other theme-reviewers suggestion on same.
>>>>>> 
>>>>>> 
>>>>>> -- 
>>>>>> Faishal Saiyed 
>>>>>> Web: about.me
>>>>>> 
>>>>>> _______________________________________________
>>>>>> 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
>>> 
>>> 
>>> _______________________________________________
>>> 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/20140121/38d9471a/attachment.html>