Web2.0* 1.5 Available

Click to view larger imageI can happily announce that Web2.0* version 1.5 is now available for download.

Here’s a summary of the improvements, fixes, etc:

  1. Options Page
    This took up most of the development time. It meant that all the stylesheets had to be edited, along with creating the actual options available (of which there are 41!) Click the thumbnail to view a cropped screenshot.
    - Font options
    - Colour options
    - Change layout from fluid to fixed
  2. Bugs
    - Images that are taller than the content will no longer cause the layout of the post meta data and comments to wig-out.
  3. Miscellaneous
    - I’ve removed support for Lightbox as it was causing the CSS to be invalid.
    - All the public viewable icons have been replaced with png. This is to aid transparency when the theme’s background colours are changed. For visitors how might still be using Internet Explorer 6 I’ve used transparent gifs - this may look odd if the theme’s background colour is changed to a dark colour. I may try and sort out a fix for this at a later date.
    - I would still like to get the theme i18n compliant, but am not willing to commit to a time-scale. If there is anyone out there who would like to help with this then please do get in touch.

On a final note - This is the final major release of Web2.0* - I will only be updating the theme with fixes as and when bugs are found and reported. Please do not request personal enhancements, etc. My free-time is very limited and I need to concentrate on my paying free-lance work. Thank you for your understanding and more importantly your continued support - it is much appreciated.

18 Comments
Feel free to contribute.

Neil…thank you so much for your hard work. It’s really appreciated. I wasn’t surprised with pulling Lightbox support but I was surprised to see you change from fluid width to fixed width. I thought fluid width was a strong differentiator for the theme. Not sure if I’ll upgrade right away.

Yes, thabk you for your hard work. Not sure what John P is talking about re: fixed width. I’m showing 90% as a body width and that’s fluid to me. Mind you, it *can* be set to px…

The CSS editor is also appreciated.

I was just reading Neil’s description above but I do see how wp-container’s style hasn’t changed from 90%.

Hi guys,

Thanks for the comments - always appreciated.

John, the theme now provides you with the ability to set the width - whether you wish it to be 100% or 700px - it’s now up to you. By default it is still 90%.

I should have read through the CSS before I commented. D’oh.

John, to get the Subscribe To Comments plugin to display neatly simply add the following to the style.css file:

.subscribe-to-comments input#subscribe,
.subscribe-to-comments label {
margin: 0 !important;
padding: 0 !important;
width: auto !important;
}
.subscribe-to-comments label {
display: inline !important;
float: none !important;
}

This will be included in the next minor release.

Just amazing. Thank you, Neil.

I did upgrade to 1.5. It seems like most, if not all, of the IE 6 rendering problems I had to workaround in the footer (due to the fact I customized my footer with 3 lines of text) are fixed with this release.

While it’s a “major” release, all of my custom templates simply copied over from 1.2.5 without a problem. Mods I made to index.php and single.php were not a problem either. I had a separate section in the style.css for custom styling which just needed to be copied to the new style.css. Once I figured out where I had to put my header background image CSS call (in style.php), I took 1.5 live. I needed about an hour to do the upgrade due to me keeping 1.2.5 side by side through the transition.

Thank you again, Neil!!!

Not a problem at all. Glad to hear it’s going well.

Hey Neil! Great update. But I just stuck to the 1.2.5 and I just got the functions.php file and uploaded it. I guess it will be too hard for me to strip the new update because I have put so many additions there like gravatars, comment editing functions and an image header which features random images. You may check my site anytime you like to check out my developments.

Thanks buddy!

Whoops, sorry. Typo errors on some words. Guess I wasn’t attentive enough to review my post.

Hi Neil,
Here just to say thank you.
You’ve created a fantastic theme!

cheers,
T

Thanks in advance for your work.
I am using your theme, I like so much.
I want to contribute with my spanish translation, you can see in my blog:
http://blog.lebrijo.com/?p=44&language=en
or directly:
http://blog.lebrijo.com/wp-content/uploads/web-20-100.es.zip
best regards,

Hi, Neil. Thanks very much for the fine them.

I’m using version 1.5 on my site and can’t seem to figure out how to make titles appear the way I’d like them to.

For instance, a friend wrote an album review titled, “Review of Autumn of the Seraphs.” If I type in the title as “Review of Autumn of the Seraphs,” “of” and “the” are both capitalized. This happens with all titles. I would prefer this didn’t happen.

any ideas/suggestions?

Search, in ’style.css’, for:

text-transform: capitalize;

and replace it with:

/*text-transform: capitalize;*/

That will comment out the capitalization of the post headers.

Neil, I couldn’t thank you enough. We’re hoping to launch our second issue soon and this will be the touch that makes everything perfect.

You are both great and excellent. However, your greatness and excellence are dwarfed by your magnificence and splendor.

If I had a picture of you, I would put it on my wall and show friends. The caption: “Neil: Kind of Everything.”

Thank you.

*King of Everything

Thanks for the kind words Clifton!

Hi again, Neil.

I thought I would press my luck with another question regarding entry titles: can I use italics in my titles?

It would be great to be able to display “Review of Moby Dick” rather than “Review of Moby Dick.”

This is easy in HTML, but seems impossible in WordPress.

Thanks!

Have your say





Fields in bold are required. Email addresses are never published or distributed.

Some HTML code is allowed:
<b> <strong> <i> <em> <del> <code> <blockquote> <a href="URI">
URIs must be fully qualified (eg: http://www.domainname.com) and all tags must be properly closed.

Line breaks and paragraphs are automatically converted.

Please keep comments relevant. Off-topic, offensive or inappropriate comments may be edited or removed.