Create Child Theme button
I propose 'Create Child Theme' button in the Appearance/Themes page to quickly create a child theme of the currently active theme (unless it's a child itself). Then one can create a child theme within the WP GUI and customize quickly without needing FTP access.
There are plugins that can do this.
I agree with xopianoi:
If this option is included in the Core, then users won't have to rely on plugin authors to keep their products updated.
Of the current plugins offered, I prefer this one:
because of Where it displays the option, to build a child theme. The downside to the plugin is that it hasn't been updated in over 2 years.
I don't think that the fact that the plugin wasn't updated in 2 years is an issue, a new child theme is just a folder and file creation with minimum data inside it... why should it have been updated in the last 2 years?
As relating to that particular plugin (which I prefer of those that are offered), I was looking at it from a marketing prospective to new WordPress.org users.
If a newbie-type user searches for plugins that easily create a Child Theme, he/she probably will skip over a plugin that is labeled over 2 years old; and choose a recently updated option instead (even if it's not the best plugin).
That said, why not just have the Core provide a wp-admin/themes.php/current theme/child theme/ button instead.
@jnhghy, technically you are correct, not reason for an update for what its doing, no changes really needed. But for the average user might not know if its worth messing with or not. A simple change to show its compatible with the latest version of WP would be nice and thoughtful in this case. But that goes for all plugins.
More specifically to the idea posted here, I think this would be something that would be used by the majority of WP users. And would warrant the addition to the WP Core. And remove the need for a plugin.
@KARTHOST: This is clearly a debate, I don't want to sound like I know how an everage user things but from my point of view, when you say child theme -> you say developer (as this creates only an empty child theme) so if you are a developer you are not the avarage wordpress user, you have some tech knowladge. A lot of wp users doesn't have tech knowladge so this option will not help them at all and even more, it can confuse them. I'm not finding installing a plugin to give developer tools such a bad thing as it keeps thoes features away from non-developers.
Having updated plugins in the repo is a different thing then the main topic of this thread and I don't know what to say about it.
As I said, this is only my opinion, you can disagree but if you do, I'll really like to know your opinion.
RSS feed for this topic
You must log in to post.