One year ago in July, I started working on the Shiba Theme. It was then that I decided to focus some of my energy into blogging and I wanted a theme that was flexible and easy to customize. I am also a big fan of fantasy art and anime, so I wanted a highly visual based theme.
Thus the Shiba Theme was born …
Now it is one year later and I hardly know where the time went. But it seems fitting to have a one year anniversary release that is chock full of good stuff!
1. Wide Sidebar Option
Originally, the Shiba Theme has a relatively narrow right sidebar compared to other WordPress themes. Now, you can choose whether you want a wide sidebar (as is seen on this page) or a narrow sidebar (as is seen on the other pages in this blog).
The sidebar width option can be set on a theme by theme basis as well as on a blog wide basis. As usual, the local theme option (if set) will override the blog wide option.
For example, on this page, I have set the theme option to show a wide sidebar which then overrides the regular narrow sidebar on the rest of my blog pages.

In support of wider sidebars, we can also load larger top and bottom sidebar images (320px by 590px). In fact, images now crop to this new larger dimension.

When sidebars are wide the whole image will be used. When sidebars are narrow, only a portion of the image will be used.
Old theme pictures that are narrow (180px by 590px) may still be loaded and used if they are sized beforehand. When used on a wide sidebar configuration, the extra background space will be automatically filled with the proper background color.

2. New Blog-Wide Shiba Theme Options Page
Themes can now be assigned to blog-wide conditions such as is_front_page, is_404, is_post, is_page, etc. The new options page can be found in Shiba Themes >> Theme Options.

You can also set when you want to show post excerpts and when you want to show the entire post content.
3. Shiba Themes Are Now Custom Post Types.
The biggest change in Shiba Theme 2.9 is that theme objects have been converted to custom post type objects. There are many advantages to this including -
- A better interface for managing and editing theme objects. You may now search for theme objects based on their title, as well as perform bulk operations on multiple theme objects at once.
- Theme objects can now be exported and imported using the standard WordPress export/import tool. This means you can easily move your Shiba themes from blog to blog.
- There is now a separate dashboard menu for Shiba Themes. This menu allows you to manage existing themes, add new themes, copy themes, preview themes, and change blog-wide Shiba Theme options.

Note – The Shiba theme interface is now similar to the standard WordPress post and page interface.

Because Shiba Themes are now custom post types, this new release will only work in WordPress 3.0. If you are using an older version of WordPress please download Shiba Theme 2.8.
Hi, I’m also getting some errors when using your theme with WordPress 3.0.1 I have this setup locally on my Windows SP3 machine running XAMPP. I was able to activate the theme, but when I click on the Shiba Themes section, I get the following error messages at the top and lots of warnings in the middle of the page.
Warning: call_user_func_array() expects parameter 1 to be a valid callback, class ‘Shiba_Theme_Manage’ does not have a method ‘_d15806ddc’ in C:\xampp\htdocs\weddingrsvp\wp-includes\plugin.php on line 166
Warning: array_keys() expects parameter 1 to be array, null given in C:\xampp\htdocs\weddingrsvp\wp-includes\classes.php on line 395
Did you make any modifications to the theme templates? It could also be some incompatibility with XAMPP.
hi, nice theme, thanks, but strange, it doesn’t work with 3.0.1. btw, could you put up dog and dragon images for download which are in your http://www.shibashake.com/wordpress-theme/wordpress-blog/?theme=Dog
http://www.shibashake.com/wordpress-theme/wordpress-blog/?theme=Dragon
What errors do you get on 3.0.1? It works fine on my environment so please let me know what bugs you are getting so that I may fix it.
Thanks.