WordPress.org

Ready to get started?Download WordPress

Forums

How to create a 1.3 theme/template (17 posts)

  1. hisyam
    Member
    Posted 9 years ago #

    isn't this thread and http://wordpress.org/support/6/13666 the same?

  2. Root
    Member
    Posted 9 years ago #

    It is true that Odyssey Alpha One shipped with a hacked 1.2 index file. But it makes no difference to the end user at all. By the time we get into Beta we will be using the 1.3 file but it is not necessarily as straightforward as it sounds. eg Will it change between now and then ? A theme builder who wants to develop separate headers etc needs a 1.3 index. But a user who just wants a wide range of style sheets can use Odyssey.
    Plus although you are right to contrast the differences people with heavily customised 1.2 index files needed to know the adjustments necessary to that file in order to achieve the same result. So we started there.

  3. Root
    Member
    Posted 9 years ago #

    I know. Isnt it brilliant ?

  4. lstelie
    Member
    Posted 9 years ago #

    Isnt it brilliant ?
    Clearly it is !!
    This 1.3 is trully great !!!!

  5. carmige
    Member
    Posted 9 years ago #

    Thanks sooo much for sharing. This is great!

  6. Anonymous
    Unregistered
    Posted 9 years ago #

    Root, you working on splitting gemini into the multiple files? :)

  7. Root
    Member
    Posted 9 years ago #

    Yes I am. There are three ways to go. Edit the index. Edit the subsidiary files. Or
    go further than WP and create an extra file(s). (my preferred solution). I must admit that I am not really in a hurry. The only people who need it are theme developers most of whom presumably would want to do their own editing but I am not sure. The Odyssey theme pack is a resource for style sheet designers.
    There might be a need for a different and extra 1.3 Gemini as well. I am also working on building some extra styling hooks into Gemini 3 in the menu area for fancy rollovers. It is tricky and requires the CSS for a nested menu.
    We should remember that it is not out of the question that the devs could reverse themselves on any aspect of this. It can be messy having an Alpha on release but it is really working well in terms of getting feedback and understanding from the community while at least in theory there is scope to change. That represents open source dev at its best and I have to say I think it is a really positive thing.

  8. basketball
    Member
    Posted 9 years ago #

    Thank you for the help Istelie, I found it very useful. Didn't find a single search result using the wordpress search function. Came upon this thread through google

  9. adsworth
    Member
    Posted 9 years ago #

    Hi,
    here is what I gathered playing around with the CVS version of 1.3 from the 24th of October. The index.php files needs to be there.The wp-footer.php, wp-header.php and wp-sidebar.php are called from the index.php, so they are not necesserally needed. I also found that the wp-comments.php actually needs to be called comments.php. To sum it up a new template needs a style.css, index.php and a comments.php to work, anything else is up to the template developer.
    Can anybody confirm this?
    A friend told me about wordpress (I didn't find it on google searching for php blog)
    and I'm very impressed, it's fun and easy to play around with. I really liked the installer. Template development in 1.3 is also cool.
    Regards
    Adi

  10. Root
    Member
    Posted 9 years ago #

    I do not wish to discourage any one from taking part in an emerging dialogue about themes - it is still evolving in 1.3 and several of us are beginning to get our heads around it. There are dangers in bits of info being published piecemeal by folks new to it. A theme may consist of a single style sheet. It may consist of a style sheet plus alternative index file. And it may consist of alternative footers, comments and headers. The above post is inaccurate in this regard and may be disregarded. IMHO.

  11. razorwriter
    Member
    Posted 9 years ago #

    I don't get this - I upgraded my blog to the latest alpha and it still is pointing to wp-layout.css rather than styles.css in the main directory... I can see the header PHP file is calling <?php bloginfo('stylesheet_url'); ?> however...
    I've also created a directory inside wp-content/ ... the thing is, it doesn't show up in my admin interface as a theme... What am I missing? Do I need to put that theme comment header shown above in my wp-styles.css to get it to call my theme director?
    Don't get it so far...

  12. Ryan Boren
    WordPress Dev
    Posted 9 years ago #

    The default theme still uses wp-layout.css for backward compatibility purposes. Your theme directory should exist under wp-content/themes/. A style.css must exist in your theme directory for your theme to be recognized as a theme. The theme header is optional but recommended. If you are putting your theme directory directly in wp-content/, that is the problem. Put it in wp-content/themes/.

  13. razorwriter
    Member
    Posted 9 years ago #

    Never mind that, I figured out I had to make a Themes directory inside of wp-content before makeing a directory containing the theme itself!
    In the case of the new seperation-of-files in 1.3, what are all the template files I need to copy from the main directory to my theme directory, since I want to start with the default ones?

  14. razorwriter
    Member
    Posted 9 years ago #

    to clarify: the only thing different from the default theme in my 1.3 is the CSS file ... I want to use the same basic PHP files, but have my own theme named in the admin interface!

  15. Ryan Boren
    WordPress Dev
    Posted 9 years ago #

    If you want to use the default templates, add a theme comment header to your style.css that includes the following line:
    Template: default
    That tells the theme to use the default templates. All your theme needs to provide in that case is style.css.

  16. trevorturk
    Member
    Posted 9 years ago #

    small question: why isn't the /wp-content/themes/ directory there (and empty) by default? having the folder in there would save this little bit of confusion.

  17. razorwriter
    Member
    Posted 9 years ago #

    Thanks, boren. Makes sense.
    I think trevor has a point. What he says makes sense to me. Of course, having actual documentation is the only thing that will really get rid of confusion!
    BTW boren, since your blog is kinda political, you might want to check out my friend's at politicalpundit.com...

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.