You don’t have to use header, footer, etc. You can structure your theme however you want. All that is strictly required is a stylesheet and an index.
All files must now live in a theme directory, however. WP no longer looks in the root for anything.
The word I’m using tonight is interesting … got some stuff working, others not, but it’s not that it’s difficult or worse, just different 🙂
WordPress is right now in a snag — the development pace and support is phenomenal (thanks to allusion and rboren) and as consequence, there are a lot more people using the nightly builds then people normally would… I guess the best part is that although the developers may feel overwhelmed, the general consensus is that early and frequent reports only creates a better and more stable product down the ways. I heart WordPress.
I’ll try to give a quick rundown of the recent changes to the default theme. These changes were motivated by a desire to eliminate the complexity of the include hierarchy for the default theme and avoid the upgrade collision problems.
The default theme used to be comprised of files in the blog root and wp-content/. In the root we had index.php, wp-layout.css, wp-comments.php, wp-header.php, wp-footer.php, wp-sidebar.php, and wp-comments-popup.php. Certain files added to wp-content/ would also be used when constructing the default theme. The default theme required special casing in the theme engine since it lived in several different directories rather than within its own theme directory. Default theme files were also subject to overwrite during upgrade since they shipped with WP. To simplify matters, the default theme now lives in wp-content/themes/default. It no longer requires lots of special casing and trapsing through different directories.
To avoid overwrite, a site theme is generated on-the-fly during install/upgrade. If you have old theme files from a previous release in your root, they are copied to a new theme that is named after your blog. A theme header is created and all files are updated to work as a theme. If you are doing a fresh install, the default theme is copied to your site theme directory. This allows you to edit your new site theme without worrying about overwrite during an upgrade. The default theme should not be edited.
Thread Starter
kyte
(@kyte)
Ok, thanks for that explanation, it was as I thought. I have decided to do the existing themes with 1.22 users in mind, and will also rewrite them for 1.5 (since they now break, where they didnt on the alpha, which was still pulling info from the main wp directory). I am assuming that the structures are unlikely to change in the near future so will construct new themes with that in mind.
It does tend to make it a bit of a pain for those still using 1.22 though :-/
I just downloaded the latest and like the way it’s changing…….the only problem is the default theme was zipped up without its “images” directory.
Yeah, SourceForge/CVS is giving me grief. Some of the stuff I committed last night seems to have disappeared. I just finished recommitting everything. Hopefully it will stick this time.
Let me get this straight: if 1.5 will no longer accept templates in the root, will I have to shift every page of mine that is using WP code into the theme directory? My understanding was always that the existing system would continue to work and nobody was going to be forced to use the theme system or rebuild their entire site. Has that changed or am I misreading this thread completely?
?????????? I want to intergate gallery. So I was looking at this hoping it would explain what I need to do but I think I might be more confused.
Thread Starter
kyte
(@kyte)
Anon.. from rboren’s explanation, it seems that the upgrade (assuming you do the upgrade thing) will move your theme, appropriately directoried, into the themes directory, and applied to your site. Ergo: no fuss upgrade. It worked for me:)
Thread Starter
kyte
(@kyte)
Tek… im sure someone will help, but my question was about the changes in how themes are read into one’s site.
Well they are the same lines… I can’t tell where the call for the theme is comming from so I don;t know how to edit the wrapper in gallery.
Thread Starter
kyte
(@kyte)
Welll… the index.php in the theme calls in the header, footer and sidebar, so if you dont want any elements of the index, I would think that you might want to edit that, to include your gallery (via a php include statement perhaps?).
Alternatively you might edit your gallery’s wrapper down to just the display elements and do a php include to get the header, footer and sidebar into that, and place a link via link manager to that page?
Hope I’ve been of some help, I’m new to WP so… caveat emptor <grin>
@anon: I think both are true.
From what I understand from playing with the latest stuff, yes, styles and such are moving to /themes
and this is (for me at least) causing a couple of problems with static pages.
BUT
1 – The upgrade process will take care of all file moving so users have little to worry about
2 – Further upgrades will be easier as those files that most of us customise will be in our /theme directory. As it is right now, upgrading involves taking a lot of care to stop WP overwriting our carefully altered files. This change helps us, not wp.
3 – I will work later on the static page issues I have and post any useful information.
4 – As it is right now, the difference between 1.2.2 files and a 1.3 theme are quite significant. This is to the detriment of all users and designers. This change makes things better for all users.
Any changes that are essential will be ‘one-off’ jobs and good for a long time, so it’s not a huge issue really. And in the end, if such a change is deemed to be too great by a user, then the answer is very very simple – do not upgrade.
This is to the detriment of all users and designers.
Podz, are you sure about this?
