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

[Melissa Oveson]

I'm not saying that it is a bad goal or that's creating the page-*.php is wrong. I'm saying if you have a script that generates that, that is plugin functionality.

> On Jan 21, 2014, at 2:38 PM, emin ozlem <eminozlem at gmail.com> wrote:
> 
> Well normally you'd have to create a page-*.php file inside your theme folder. So it would get lost anyway, you cant switch page-*.php templates between themes.
> 
> My main goal is to save the user the trouble of creating page-*.php template file, typing in the template name & the query params.  Plus, if the template markup changes, the user wont have to update all of their page-*.php files accordingly, manually. I cant see any downsides compared to the default behaviour in this, if you do please do tell.
> 
> 
> 2014/1/21 Melissa Oveson <missybunnie at gmail.com>
>> I think that a custom page creater sounds like plugin territory. It's something that would be more beneficial if it didn't get lost when you moved to a new theme.  Having a possible custom post type formatted in your theme might be okay if you aren't defining the custom type (I.e. Woo commerce layout in theme but not incorporating any of the plugin functions)
>> 
>>> On Jan 21, 2014, at 1: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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20140121/5b0cd978/attachment-0001.html>