WordPress.org

1. sholarpk
   Member
   Posted 1 year ago #

   WP v3.x Docs doesn't describe in detail what files and file content must be present for WP Dashboard to recognize a theme (broken or not) as a candidate to be activated. This is VERY BASIC INFORMATION, and it's why I'm presently stumped at Square 1 in crafting a new theme from scratch by following this tutorial:
   http://themeshaper.com/wordpress-theme-template-directory-structure-tutorial/

2. sholarpk
   Member
   Posted 1 year ago #

   If WP Dashboard is not going to intelligent enough to fail properly when the proper minimal set of themes child folder files and file contents aren't recognized, then please provide copies of such a set of files with the WP package out of the box! Don't allow this poorly handled failure mode to stop the very new user dead in his/her tracks!

3. Rev. Voodoo
   Volunteer Moderator
   Posted 1 year ago #

   What part of

   style.css is the one and only required file in a child theme.

   from: http://codex.wordpress.org/Child_Themes#The_required_style.css_file

   Isn't explicit enough for you?

   style.css, with a header....is all you need to activate a child theme. It needs to be in a folder. If you want to upload it through the wp interface, then than folder needs to be zipped.

   http://go.rvoodoo.com/WPchild
   is an article I wrote about child themes, not sure if it will help you any. It's about as in depth as I am able to be with my limited writing style

   Why should extra files be included with Wp because someone doesn't do their research? Wp can't be everything to everyone out of the box. It's software. Code. You need to learn it if you want it to do your bidding. Otherwise a managed blog environment like wordpress.com may be better suited

4. sholarpk
   Member
   Posted 1 year ago #

   The problem is, what it says is inaccurate compared to what I see WP actually doing. A styles.css containing only a comment, plus a set of completely empty *.php files results in that stub "theme" not being recognized as such by WP Dashboard. What am I supposed to think of this SILENT failure mode? (Not my definition of quality.)

   If the WP community actively discourages development of themes from scratch, then the status quo in the WP release (i.e., providing no "minimal" set of theme file for beginning development from scratch) is the way to go. Otherwise, the installed WP package should include a set of minimal files ready for theme development from scratch, like every other development-ready software product in the world.

   You don't want to know my opinion of WP's docs. I used to make a living writing software product documentation.

5. esmi
   Theme Diva & Forum Moderator
   Posted 1 year ago #

   A styles.css containing only a comment, plus a set of completely empty *.php files results in that stub "theme" not being recognized as such by WP Dashboard.

   I've produced perfectly effective starter child themes that contain only a style.css file and an empty functions.php file without the slightest problem.

6. Ipstenu
   Half-Elf Support Rogue & Mod
   Posted 1 year ago #

   I suspect you did something wrong, then.

   /*
   Theme Name:     Twenty Ten Child
   Theme URI:      http: //example.com/
   Description:    Child theme for the Twenty Ten theme
   Author:         Your name here
   Author URI:     http: //example.com/about/
   Template:       twentyten
   Version:        0.1.0
   */

   See the line for Template:? Make sure that points to a VALID template name :) AND make sure the Theme Name is original.

Topic Closed

This topic has been closed to new replies.