I've built a new theme for WordPress 3. It is called Twenty Ten Weaver, and is a child theme of the new standard Twenty Ten theme. It lets you tweak colors and layout in the admin page.
If anyone who is using WP3 would like to try it, check it out at http://wpweaver.info/themes/twenty-ten-weaver/
This theme will not work on WP 2
Nice, I've been searching the net for more child themes for twenty ten. I've been working on my own, not nearly as complete as yours though.
I've just released an update version of this child theme with even more features. Let's you tweak Twenty Ten about as much as possible without extending the theme with new PHP code.
I really like it. I found the default header image height way too tall. I previously had to edit functions.php to change the height but your theme makes it easier.
The one problem I found is that if you switch sub-themes, your font choice and other options are lost. It should either propagate to the new sub-theme or at least save them for each sub-theme.
I also want to know if it will be possible to hide sidebar on a post by post basis. The default lets you hide it for pages but not posts.
It really is difficult to track what got changed - you can save your changes so far in a saved theme, but changes don't propagate from subtheme to subtheme. Sorry.
There is no equivalent of the single column page for posts. Would be fairly hard to do for the single post page.
It CAN be done, but only by using one of the plugins such as blog-in-blog to put an individual post (or posts from same category) onto a page. Then you could make that page single column.
But don't think it can be done by clicking or viewing the automatic single post page you get from the archive widget, for example. Someone could write a special theme to do that, but it would be very specialized.
Posted 1 year ago #
I hope I'm allowed to post questions about your theme here.
I've been trying to get the plugin called "Calendar" by Keiran O'brian to work properly on the site, but somehow the 2010 theme and the 2010 weaver theme both make it look really bad. Somehow the CSS from the calendar plugin is ignored by 2010(Weaver).
Is there a way to fix this? My site with the plugin is here:
http://www.harmoniestmichael.nl/jaarprogramma
The plugin as it should look:
http://www.kieranoshea.com/calendar
I'd love to continue to use your theme, but if I can't fix the calendar, I'll sadly be forced to find a different theme... (and customizing a theme takes a lot of time)
Thanks!
This will fix the issue:
#content tr td {padding: 1px 1px;}
Add that to the < HEAD > section of Advanced Options between the < style > and < /style > tags.
This might break how other tables look on your pages, so I am trying to figure out a more specific solution other than #content, but for now this will work. I don't think I like how Twenty Ten styles tables, and may decide to add an alternative for Weaver.
Posted 1 year ago #
I use the Twentyten theme and ran into 2010-Weaver and Twentyten-Weaver by accident when looking for instructions on creating a child theme for Twentyten. They look so much more versatile and easy for a novice designer like myself. However, what are suggestions/benefits for choosing the 2010-Weaver or Twentyten-Weaver child theme?
Thank you. So Humor Me
Posted 1 year ago #
Thanks wpweaver! It worked!
It's somehow not still exactly how the calendar looks on the developer's page, but at least it looks a lot better now, with equal spacing.
Great job!
Posted 1 year ago #
Hi,
I am useing your theme and it works great only one question.
I like to use some WordPress functions in the header to set a different background picture on every page.
Only the php code doesn't work it just appears in de html as coded.
Is there a way to do use php code through the advanced options header section?
Hope you can help.
Greetings,
Boudewijn
Posted 1 year ago #
Same issue as Boudewijn
I've created a custom function to manage date-controlled backgrounds on a blog by blog basis within multisite, but can't get it to hook properly to wp_head() - keeps returning a fatal error for undefined functions against any WP functions in the function script - even basic ones such as get_bloginfo() that already appear above the stylesheet in the TwentyTen head zone.
Really frustrated that I cannot figure this out and would appreciate any pointers.
Gaz
The Site Header Insert Code section of the Advanced Options supports shortcodes from essentially any plugin. There is a PHP shortcode plugin. That is how to get PHP into the Header section of a page. However, this is past the < /HEAD > tag. There is not a way to get PHP or the output of some PHP logic inserted into the < HEAD > section using Weaver.
I haven't looked, but there is likely to be another plugin that let you use PHP to emit HTML in the < HEAD > section - could be done, so I imagine it has. I'm pretty sure there can be multiple themes + plugins that hook wp_head().
Another approach is to write a plugin. They can be really simple - perhaps a lot easier than trying to mess with a theme's code.
Posted 1 year ago #
wpweaver - lookup (google) css generated with php
That's what I'm trying to do.
The issue is that with a correctly working child-theme functions file assembling the style sheet from default style.css (child version) plus a functional stylesheet.php - all the WordPress functions (including the most basic such as get_bloginfo() ) are returning fatal errors, despite that identical function being called earlier in the <head> before the default stylesheet direct call, and significantly before wp_head()
I don't want to have to load up header.php with acres of code the way you had to - I want it held outside in a stylesheet.php which the PHP functions do allow as do the CSS functions - it seems WordPress do not.
The problem appears to be somewhere in wp_head() or maybe in ms-functions() or ms-template() - knocking out access to WP functions when using php generated stylesheets.
I did read a note on a plugin in the repository that they had been forced to remove a key functionality because WP does not allow plugins that modify or extend core function functionality, nor that change or extend core theme files - starting to think they've encoded enforcement of that somewhere.
Sorry about not getting back - guess I should subscribe to the feed on this topic...
I don't exactly understand everything you've said - it can be very hard to do without actually seeing code. If you'd like to contact me via my website (wpweaver.info), perhaps I could take a look at what you're doing. I thought you were just working on a custom Weaver theme, but if you're doing an interesting plugin, perhaps a quick glance at the code might trigger something. Sometimes just another set of eyes can see an issue.
Posted 1 year ago #
I got the Twenty ten weaver and it's great! thanks!
Posted 1 year ago #
@wpweaver
OK, it's a lot simpler idea than I think it takes to explain it ...
Let's say you have an annual calendar with events such as Valentines, Easter etc. and you want to change background images based on the current date.
Option 1 is bung in a div and a normal function to grab an image on a template by template basis = heavy to maintain.
Option 2 is to have a function that generates the image URL by date-based rules, then uses that string variable as part of a css created by the function. That css then comes after the normal style.css and so replaces the defaults where applicable.
But trying to run it in the header results in the errors described earlier because the function relies on WP functions that are not called until wp_get_header(). Catch-22 is you need that css to run before get_header, because you need it to apply to the header too.
Still going round in code circles with it ... thinking of relocating to a corn field and making circles there instead ;-) lol.
Still a little hard to grasp. The only thing I can think of, and it still might be too late in the generation cycle for your needs is to include some PHP code in after the < /head > by including it in the Header code section (but before the nav menu). That section allows WP shortcodes (mostly to include slideshows), but that shortcode can be for a PHP execution plugin.
Other than that, I don't really have more suggestions.
I just made my own Twenty Ten child theme and wrote up a series of 5 tutorials so that anyone who wants to make their own child themes can follow along. The theme is called Oh One Oh Two, and though it may not be the sexiest theme ever, it is a Twenty Ten child , and I documented how I created it.
The theme was released GPL and people can download it and see just how it fits together at http://0102.atlwpusers.com
Posted 1 year ago #
@Weaver updated Weaver theme to 1.3.1 today on several sites I am using it on and all of them crashed to show blank white pages. 2010 Weaver doesn't even show up in installed themes, then fails when I try to install it saying that the folder already exists. Had to download to save the them via FTP, then delete the folder altogether and then re-install it into my themes. Now I get a warning when trying to preview, so there is something Majorly wrong with the update. I am sticking with 1.2.3 until you get this issue fixed!
This is a WordPress.org server issue. They have the proper theme files, but there seems to be some server issue that is delivering the wrong set of files. It doesn't have anything to do with the theme, just the WordPress.org server. The update is also available at http://wpweaver.info/download/.
Posted 1 year ago #
WPweaver, would really like some help. I've recently installed 2010 weaver (I'm new to WP). After picking a theme (WHITE) and making changes in the main and advanced options- neither in the preview, or on my blog page do the changes come up. I've saved and saved, I've cleared cache and history. I can make changes by going in and playing with the style.css file in the editor, but frankly find it too confusing with the "child" and "parent" to figure out what's going on. I finally got so fed up that I deleted in entirety 2010 weaver from my site (via ftp) and reinstalled- only to find all the settings remained from before! So just to make sure I wasn't going nuts, I picked SILVER and saved- guess what? It still looks exactly the same- hasn't changed to silver, but still looks like the botched white one I was working on previously. What am I doing wrong?
Many thanks, I'm reasonably competent with CSS and HTML and very incompetent with functions- happy to hire someone to get me set up, as I've got way way too much time into this for nothing but frustration in return.
Posted 1 year ago #
@bestodyssey
I had a quick look and the settings are held in three serilized wp-option entries, so you have a couple of ways, test this on a local install if you can.
1. change the theme while you do this, if you can run the database, run the wp-options table and delete three lines, ttw_options, ttw_myoptions and ttw_adminoptions, that should clear all values.
2. without running tables, add the code below to the functions.php of any other theme, lets use the "twenty ten" theme, de-activate the WP Weaver theme and activate the "twenty ten", this should delete the WP Weaver options.
delete_option('ttw_options');
delete_option('ttw_myoptions');
delete_option('ttw_adminoptions');When you reactivate WP Weaver it will be a clean install.
HTH
David
There also is a plugin available that will perform this action without needing any coding. Send an e-mail via the http://wpweaver.info about/contact page to request a copy.
This looks awesome.. thanks..
Posted 1 year ago #
I have built my own child theme for TwentyTen using your very helpful tutorials. But, now TwentyTen has been updated! So my customized loop.php and single.php files are out of date. I don't know how important it is to search for and make the corrections/updates in the new loop.php and single.php files for TwentyTen, but it seems to me that all the advertising about how wonderful a child theme is because it doesn't break on updates is phony. The new TwenetyTen has updated css and lots of other stuff that doesn't get updated in my theme.
Does anyone know of a simple way to deal with this?
Please post a new topic.
This topic has been closed to new replies.
