Disclaimer. This is a brief post comprised almost entirely of bullet points.
Briefly:
- All themes, excluding the Sandbox, have been updated.
- These theme updates are available as release candidates on their respective project homes on Google Code:
- These releases should work with both WordPress 2.0.x and 2.1.
- Please download and test them. Then let me know what I screwed up.
- I will call them finished when I’ve found enough bugs to satisfy me.
- I’m going to update the Sandbox. Promise.
That is all. Thank you for your time.
28 Comments
YAY!… commencing download.
thanks, scott, plaintxtblog is working like a charm.
I’m very happy with plaintxtblog v3!
Everything works perfect in ‘blogtxt v 3.0′ theme.
By the way – thanks for adding option to resize images automatically in the posts and positioning blog in the center of browsers window.
thanks!
Scott:
There’s only one problem I see with veryplaintxt v.3: italics have to be hand-coded. Otherwise if button clicked, they appear as bold.
LJ
Hey LJ: Actually that’s on purpose. Read the readme.html that came with the theme files.
This is more of a user-end issue. Because I consider
<i>italics</i>to be different than<em>emphasis</em>. The latter relates to the content, whereas the other is for presentation. If you want text to appear in italics, use<i>; to emphasize text, use<em>.Now if you want emphasized text to appear in italics, that’s another issue all together.
Scott, I’m hammering away at a Sandbox skin to reskin my site and blog, and could really do with the latest code to see what’s going on. Any chance I can get at it?
Hey Stephen: The changes to the Sandbox won’t be sweeping by any measure. Some small changes here and there and mainly it will be cleaning up the markup. So your skin shouldn’t be affected by the updates.
And, frankly, I haven’t gotten around to making them yet. I will, though, and very soon.
i love the new screenshots for the first 3
Any ideas for the screenshots for plaintxtBlog and Simplr? I kinda drew blank on those two and reverted to using actual screenshots. Yawn.
actually, i think simplr works as it is quite well. dunno what to think about PTB. i’ll kick it around tomorrow or something.
Actual screenshots may bore you but the reason the WordPress themes page uses them is to help the user. A pretty picture of something else is anything but helpful.
I agree in principle to Andy’s statement. But if the image represents the essence of the theme, well, there’s something to that as well.
If someone finds a theme they like, downloads it, and then uploads it, I doubt they’ll get to the Presentation screen and decide not to use it upon seeing an image that isn’t a literal representation of the theme. But then again, they might.
Hi I’m trying out Barthelme v.3 and think it is great. However I can’t seem to get page list to recognise the page order I’ve coded? I’ve looked at the php code in sidebar.php and changed it, to ’sort_column=menu_order’, which I thought would sort it, but it did not. I’m using your sidebar / widgets so I tried disabling the widgets and that sorted my problem (with my code change), but obviously I’d like to use widgets. I’ve looked at the code in functions.php and I can’t work out the problem (I’ve a very basic understanding). Any ideas? I’m using WP2.1
Seamus: I just sent you an email. You’ll just need to find a widget that displays pages by page order. Check out widgets.wordpress.com as a good starting point.
agreed with what scott says.
i understand that on shared hosting environments (wp.com) those screenshots aren’t helpful persay, when the user’s already taken the time to download the theme, a descriptive, branded image is more useful than a minutely scaled screenshot. [c.f. the usability arguments against snap preview].
a selectively cropped image can tell you something about the textural qualities of the theme, the element styling (lists, links, menus, etc.). a scaled screenshot can give you a blurry guess at the relative color palette of the theme.
(relative, because scaled and compressed images will distort the actual colors).
p.s.-
andy, i see that all your wp.com themes in svn include bg, text, and link colors as variables. putting those variables onto the theme switching page would be far more valuable than normalizing screenshots.
Scott: many thanks. I’m now using Navey Road’s widget called folding pages and it now works great. Thanks for the quick bit of advice – it takes ages to find something that’s not there!
BTW I really like this pre-view function you’ve got for posting – if possible could you give me a reference for it?
Thanks again..
Hey Seamus: Glad that you got it sorted out.
The plugin I use for the comments is called Live Comment Preview. It works pretty well, but I can’t speak for its WP 2.1-compatibility. Yet.
Thanks Scott I’ll give it a try and hopefully report back.
Scott: Well back sooner than I thought Live Comment Preview seems to work fine with Barthelme v.3 under WP 2.1 with no adjustments.
I have a few errors but not to the point where i couldnt fix them.
Hey Scott,
Once uploaded, both blogtxt and simplr say they’re missing their stylesheets. I’m on 2.0. Any ideas?
Thanks!
Never mind; I’m an idiot. It’s beautiful!
Scott, thank you thank you thank you. I have been wanting an easy-to-use three column template ever since I started using Wordpress a year and a half ago. This is the first one I’ve found that actually works. And I’m amazed at the amount of thought you’ve put into this–the little things, like noting default settings, as well as the big ones, which alas are far too technical for my simple little mind to grasp.
I do have one question; perhaps you can guide me through this if you have the time. When I click on the categories or the archives, it displays a truncated version of the post. How can I change it so the whole thing displays?
Thanks again,
zia
Hey Zia: You’re welcome you’re welcome you’re welcome. Glad you like the theme.
As for the excerpts appearing on archive pages, you just need to replace
the_content()withthe_excerpt()in the following files:archive.phpcategory.phpsearch.phpAnd possible some others I’ve forgotten.
That should do the trick. Let us know how it goes Oh! and if you do do this, please be good to the hAtom microformat and delete the class
entry-summarythat appears in thedivdirectly abovethe_content()call, as leaving it would be unsemantic—if that’s even a word.Hey scott, don’t know if you are busy at work with Sandbox 1.0 but just wanted to relate a hack I’ve been putting in recently.
I’ve been adding a tag to the body class of single posts and pages with “id#” where # is the WordPress post ID. I’m not sure if you have adressed this in you next release but it allows for total control of stylesheets for a specific post. On a recent project I needed to have the header be enlarged on just the first page. By adding this tage you could concevably have a custom stylesheet control over any part of a specific page.
I know there is a post specific page number tag farther down, but for some purposes, like the one mentioned above, it just didn’t work.
I thought you might be interested. I assume it should probably be an “id” tag, but I am not great with php. Thanks for the great work. I am in love with Sandbox.
Ben: Actually that’s one of the improvements we’re putting in. There will be a couple other new
bodyclasses. Off the top of my head,.protectedis one new one.