not resolvedIt's been announced that WordPress 2.3 will be released on tomorrow, Monday Sept 24. http://wordpress.org/development/2007/09/preparing-for-23/
The upgrade will include "new features that (hopefully) will make you want to upgrade right away."
Has the Cutline theme been tested with WP 2.3?
Robert
I'm using WordPress 2.3 with Cutline and everything works fine for me.
It seems from reading one of the WP codexs and looking at cutlines files... it will need a little upgrade (code added) to index.php and single.php for the new 2.3 tagging system to work right.
Otherwise cutline should be fine.
Here's a link to add tagging to your current theme.
http://richgilchrest.com/how-to-add-wordpress-23-tags-to-your-current-theme/
Thanks for the help!
These are code lines that everyone can use that'll scale with all of the current WordPress versions -- and allowing for the theme to be compatible with 2.3. You must include the PHP IF statements as I have them here (though I'm sure there are probably ways to alter the output, other than what I have here).
This will provide generic 2.3 Tag Cloud support for Cutline, however -- without breaking the theme if 2.3 does not exist.:
Sidebar PHP, add into your sidebar.php file through Dashboard > Presenation > Edit Theme.
`// Cutline Tag Cloud for WordPress 2.3 (Sidebar)
<?php if ( function_exists('wp_tag_cloud') ) : ?>
<!-- WordPress 2.3 Tag Cloud -->
<li class="widget">
<h2>Tag Cloud</h2>
<p><?php wp_tag_cloud('smallest=8&largest=22&number=10'); ?></p>
<?php endif; ?>`
General code to include in areas other than the Sidebar.:
`// Cutline Tag Cloud for WordPress 2.3 (Layout)
<!-- WordPress 2.3 Tag Cloud -->
<?php if ( function_exists('wp_tag_cloud') ) : ?>
<p><?php wp_tag_cloud('smallest=8&largest=22&number=10'); ?></p>
<?php endif; ?>`
If anyone has other ways of implementing Tag Clouds into Cutline, can you please share? I'm not sure exactly how specific Tag Clouds can be with 2.3 -- and whether they can be specific to each post.
If this is the case, it would be interesting to see the variations that could be incorporated into the theme. [ie: Tag Cloud: 'tags', below Categories: 'categories' -- where it currently displays Tags: 'categories' for each post in Singlepost.php.]
Note!
This code was written for inclusion into the 2-column version of Cutline. I continue to use the 2-column version over the 3-column version, and am unfamiliar with whether the classes and layout have changed in any significant ways between the two.
If the classes are still the same for both versions of Cutline, then this should hopefully come of use to everyone. If there are any significant differences, please modify these suggestions and post here so that others might benefit! (Or make an official, well-rounded implementation to the main site?)
Additional tips:
Anytime I include a new plug-in to my theme using the PHP function code, generally provided by a plug-in author -- I will wrap the entire output that I desire in the following IF statement.
`// Replace FUNCTION with plug-in's function name
<?php if ( function_exists('FUNCTION') ) : ?>
Code to display (along with function provided by the author).
<?php endif; ?>`
(Minus the back-ticks, of course.)
I've found that this is good practice -- as if you ever Deactivate a plug-in through the Admin panel, then the site will continue to operate minus the plug-in and without error. Unfortunately, most plug-in authors only provide users with the necessary function to include into a theme -- without consideration of what might occur if the plug-in is deactivated!
If you also want your site layout to be 'scalable' in the event that you do Deactivate a plug-in -- it is also good practice to wrap the PHP IF statement I outline above around all the output you've included. Meaning, that if you've wrapped the plug-in's function with a <div>
This will ensure -- that even though you've Deactivated your plug-in, you have not broken the lay-out of your Web site by retaining the elements you added to accomodate the plug-in. Those elements will no longer display if the plug-in is not found -- and thus, your site will only display what is intended.
You must log in to post.