Cutline Theme for WordPress

One Giant Leap for Mankind

Cutline Theme for WordPress random header image

Cutline 1.1 — Running a Killer Website Just Got Easier

February 2nd, 2007 · 239 Comments

Pimped out ride

Ladies and gentlemen, today’s a great day in the history of Cutline, and it really has little to do with the fact that version 1.1 is now on the table (get it here). The most excellent thing about this new release is that I’ve tweaked the theme in such a way that your life might now be easier.

I realize that with past theme updates, you tweakers and hackers out there have had a rough go of things. Adapting modified styles and sifting through stylesheets isn’t anyone’s idea of a good time, so in addition to playing nicely with WordPress 2.1, finding a way for you guys to futureproof design modifications was priority number one.

Thanks to a handy little custom stylesheet solution, your CSS changes will no longer be affected by future versions of the theme. This excellent update stands at the top of the list of this release’s major changes, which you can read about below.

Cutline 1.1 Changelog

In past releases, I tried to modify as little XHTML as possible in order to simplify each update. However, as I’ve learned more and more about site development, I realized that some of my markup just made no sense semantically. Also, I felt like the theme was lacking some key elements that aid in user experience, so I figured now was as good a time as any to add those bells and whistles.

So, here are the changes that you need to know about:

1. Custom stylesheet to segregate user-initiated design changes
For all you theme-tweakers out there, this is huge. I’ve appended the <body> tag with a CSS class called “custom,” and then I’ve added a separate CSS file called custom.css that you can use to implement your modified styles. You can find further instructions inside custom.css.
2. Hacks for IE6 and 7 moved to separate CSS files
Best practices for Web standards call for the use of conditional stylesheets to specify CSS declarations that are browser-specific. Cutline has a reputation for being squeaky clean, and strict adherence to Web standards is a must if that reputation is going to persist.
3. Tagline added to the header
We might as well throw a ticker-tape parade for this one. The crowd roars. I smile. And I know a little more about your site because you’ve got a killer tagline up top.
4. Comments link behavior in the tags area (after a post) changed
I thought the underline behavior looked ugly, especially when Georgia’s (the default font) 3s, 4s, 5s, 7s and 9s, which descend beneath the baseline, intersected with the underline. Okay, so I’m a freak.
5. XHTML elements after each post changed
In previous versions, <h4> tags were used to indicate the end of a post and also to create the whitespace between post listings on the front page. Semantically, this is beyond dumb, and there were also inconsistencies across different browsers in terms of margin rendering. In order to rectify this, the most obvious element to use is a styled <hr /> tag. Instead, however, I elected to use a special clearing <div> element because it will cause less confusion for folks who might choose to change the background color of the theme (because not all browsers handle <hr /> elements the same way).
6. Comment numbers added to each comment, and comment permalinks moved to these numbers
On sites with a lot of comments, I’ve noticed that people often refer to each other by comment number rather than by name. I think this is a natural and effective means of communication, and since it aids in understanding (and therefore user experience), I’ve chosen to include that feature in Cutline. Personally, this is one of my favorite additions to the theme.
7. Comment spacing tweaked
With comments like the ones on this theme, it’s a constant battle to try and achieve perfect spacing. The primary goal is to maximize scannability, but it’s also important to make them as concise as possible so as to keep pages from getting too vertical.
8. Comment submit button now completely wicked
The old comment submit button was a flat piece of garbage. The new one is totally cool.
9. CSS for blogroll adapted to better code in WordPress 2.1
The 2.0.x series of WordPress releases generated some pretty lame XHTML when outputting blogrolls. As a result, theme developers were forced to resort to tricks or bloated CSS in order to have things display properly. In 2.1, the code has gotten a little bit smarter, but it’s still not where I’d like to see it. Either way, it works, and I was able to drop about 1kB of code from the stylesheet.
10. Added an Archives link after the recent post listing in the sidebar
Being able to move easily between different parts of your site is key, and this is oftentimes most evident to the site owner, as he/she is the person most likely to traverse all sections of the site. I caught myself looking in recent posts all the time, only to find that the post I was looking for was buried deeper in the archives. Instead of getting frustrated over the fact that I now had to find the Sitemap or the Archives page, I just added a link in this location to solve the problem.
11. Archives and Sitemap pages updated to reflect template tag changes
If you upgraded to WordPress 2.1 while still using Cutline 1.03, you might have noticed that your Archives and Sitemap pages either behaved strangely or stopped working entirely. This was due to the fact that the template tags I used in those versions to generate category listings are no longer supported in WordPress 2.1. Naturally, I changed the code and brought this bad boy up to spec, so now you’re good to go.
12. Changed the footer entirely
The old footer sucked and was an eyesore. This one doesn’t and isn’t.

Special Upgrade Notes

Cutline 1.1 is only intended for use on blogs running WordPress 2.1 or higher. If you install this version of Cutline on an older version of WordPress, your blogrolls will be totally whack, and your Archives and Sitemap pages will crap out.

Also, if you’re looking for updated versions of the random header image generator files, you can find them here:

Finally, if you had already upgraded to Cutline 1.1 before reading this, please check your files! There’s a good chance that you don’t have the custom CSS solution described above, and trust me — this is one feature that you don’t want to live without!

Do you like this article? Submit it to Blogosphere News!

Tags: Release Notes

239 responses so far ↓

  • 1 Jeroen Sangers // Feb 2, 2007 at 12:53 pm

    Sometimes being fast is not OK. I just finished adapting the first 1.1 CutLine for my Spanish site, and now I read that you already made an update. Back to work!

  • 2 Rod // Feb 2, 2007 at 3:38 pm

    Merci, thank you,wunderbar… upgraded and the change over was painless.

  • 3 GfxDizayn » CutLine 1.1 // Feb 2, 2007 at 4:27 pm

    […] CutLine 1.1, wordpress 2.1 ile uyumlu bir temadır. Buradan indirebilirsiniz. Gerekli eklentiler: Random header generator […]

  • 4 Clarke // Feb 2, 2007 at 4:29 pm

    Chris,

    Thanks for this and all of your hard work on this as it is a great theme. I plan to upgrade my site this weekend.

  • 5 Vicharak // Feb 2, 2007 at 7:49 pm

    I am glad to have voted for your theme, which I have been using since the start of my blog. I have now moved to a midphase hosted site. However, I have a, rather two, problems:

    1. I want to add javascript code snippets on the side bar. However, neither your widgets nor sidebar.php allow inclusion of the same. What is the way around? Please help. I am not much of an expert on coding though I could built my blog on my own.
    2. When I want to put a new php plugin snippet like “quotes” on the sidebar, it is displayed at the bottom (after all widgeted items have been displayed). How can I customise their display,i.e., decide the display order as I wish?

    Please help.

  • 6 Rick Beckman // Feb 2, 2007 at 9:08 pm

    I’m trying to replace the title & description lines with a clickable image masthead, but I am having difficulties. Replacing the H1 (and its link tag) with the image works fine and is clickable, per your tips in the CSS, but the description line is just pushed down lower.

    Is there any simple and accessible way around this? Thanks.

  • 7 Rick Beckman // Feb 2, 2007 at 9:15 pm

    Also, the “Visit the archives for more!” sidebar link has a URL that does not end in a slash; the default archives link in the header does. Best practice would probably be for the links to both have a slash. ‘Tis an easy fix, but I thought I’d mention it.

  • 8 RB // Feb 2, 2007 at 9:21 pm

    Um, completely broken…

  • 9 Neil McIntyre // Feb 3, 2007 at 2:51 am

    Hey Rich, check out what I’ve done. I think that’s what you’re describing.

    I put a clickable image for the title over top the random image header by changing the header image to CSS background image and made the title a transparent png. I had to use ‘float:right’ to make it sit close to where I wanted - but my original plan was thwarted by IE’s shoddy CSS positioning support and my limited knowledge.

  • 10 Neil McIntyre // Feb 3, 2007 at 2:52 am

    Forgot to mention - Chris, thanks for this theme! It’s great. I’m going to upgrade to 1.1 this weekend as well.

  • 11 Alistair // Feb 3, 2007 at 6:28 am

    LOL, just when I got the last version looking fine :)

    Can you tell me if there is a way to take the tagline out of the header ? Is it just a case of removing the CSS and will this have eny effect on the way search engines view the site?

    ps. I removed the title by using display:none; for the h1 tag

    Alistair

  • 12 Chris // Feb 3, 2007 at 9:57 am

    Vicharak — Both of your problems are really the result of your use of WordPress Widgets. By using the widgets (and not controlling the sidebar entirely on your own), you’re sacrificing editorial control over the way content is presented there.

    Your first problem appears to stem from the fact that you can’t use JavaScript within the body of a widget. I have no experience with this, though, because I don’t use widgets and generally try to avoid them at all costs.

    Your second problem might be solvable through the Sidebar Widgets options panel, where you can customize the display order of your widgets.

  • 13 Chris // Feb 3, 2007 at 10:04 am

    Rick — The <h3> tag in the header was a complete oversight on my part. All you need to do is edit the CSS for the #masthead h3 element by adding this definition:

    display: none;

    This will prevent the contents of the <h3> tag from displaying. Other users need to be aware, though, that you only want to add this if you’re replacing the header text with an image!

    Also, regarding your tip on the Archives link — thanks! I need watchdogs out there to keep me on the straight and narrow. I’ll make the change this afternoon, and I’ll also add in some commented code to assist users like yourself who want to use an image in the header instead of the default text.

  • 14 Chris // Feb 3, 2007 at 10:06 am

    Neil — Solutions like yours are way too smart for IE. There are simpler ways to do what you’ve described, and perhaps it would’ve been more obvious if I’d set the code up better the first time through!

  • 15 Chris // Feb 3, 2007 at 10:08 am

    Alistair — Although I hinted at it in my last comment to Rick, the tagline in the header is specifically controlled through the following CSS declaration:

    #masthead h3

    By changing the definitions there, you’ll be able to manipulate the tagline in the header however you please.

  • 16 Eddie Corbano // Feb 3, 2007 at 11:11 am

    Chris,

    first thank you for that great theme and the update.

    My problem now is, that I’ve made severe changes to the theme, so that updating to 1.1 seems unfeasible for me. However, there seem not to be any problems yet, since upgrading to WP 2.1.

    What would you recommend me to do? I admit that I’m overchallenged with this…

    Eddie

  • 17 Jack // Feb 3, 2007 at 7:10 pm

    have tried to use Cutline, but the fonts have gone too large. no idea why this is. can you help at all?

    Jack

  • 18 vicharak // Feb 3, 2007 at 7:52 pm

    ‘Thanks a lot for your quick response. While, I will check on sidebar-options as suggested by you, where do I put my javascript code snippets? I tried to incorporate one of them in the sidebar.php without any success.
    Could you tell me as to how it is done?

  • 19 Jack // Feb 3, 2007 at 7:53 pm

    Having installed Cutline, the most recent post comes out fine, but all the others have too large a font size. Any insights on what is causing this would be appreciated. Lovely design, I wish I could get it to work,
    Jack

  • 20 Michael // Feb 3, 2007 at 7:57 pm

    Hi Chris,
    I am one of the last group of users you mentioned who “already upgraded to Cutline 1.1 before reading this”. I am wondering if adding some code to the body tag referencing custom.css is the only change I need to make? Or would I be better off just starting over with my tweaks on the new version again? Or lastly, is there a “laundry list” of changes I can manually follow. Thanks for the fabulous theme!

  • 21 vicharak // Feb 3, 2007 at 8:56 pm

    With reference to your reply, where could I find ’sidebar options’ panel?

  • 22 Chris // Feb 3, 2007 at 9:49 pm

    Vicharak — If you have the WordPress Widgets plugin enabled, you can find the Sidebar Options within the Presentation tab on your WordPress Dashboard.

    Jack — The podcasting plugin that you’re using is auto-generating some strange, substandard code, and based on my observations, this is what’s causing the problem.

    I suggest trying a two step process here:

    1. Disable the current plugin and see if that fixes the display on your front page.
    2. Try using the Podpress plugin instead. I’ve seen it on tons of sites, and I’m pretty sure it’s the best podcasting plugin for WordPress.

    Michael — Although you’ve already made some tweaks, I’d recommend that you simply start over and segregate your changes in the custom.css file. This way, you’ll be ready for any future theme updates, and you’ll also be able to track your changes.

    I know it’s a bit of a pain, but this truly is the smartest, most secure way of doing things. If I had known about this five months ago, I’d have been evangelizing it like I was Billy Graham.

  • 23 Chris // Feb 3, 2007 at 10:07 pm

    Eddie — You did a great job with the design on your site, and I only wish that I implemented the custom stylesheet solution sooner in order to save you what I know looks to be a monumental hassle.

    Fortunately, you aren’t currently using any aspects of WordPress 2.1 that “break” Cutline 1.03. However, as your site expands and grows (as it appears to be poised to do), you will likely find yourself handcuffed by limited functionality.

    As someone who personally experienced problems as a result of poor site planning, I highly recommend that you take every responsible step that you can while your site is still young. Although it looks like a big hill to climb right now, it doesn’t even begin to compare to rebuilding a site that has hundreds of entries in its archives.

    The good news is that you’ve already accomplished a redesign once. The better news is that if you do it again while utilizing custom.css, you’re going to learn quite a bit about CSS development, and I’m betting you’ll also be able to produce more refined results.

  • 24 Updating this site - stay tuned. // Feb 4, 2007 at 1:04 am

    […] Mostly done. The Cutline theme for Wordpress made the cut. It took me a while to figure out some of the features but I think […]

  • 25 Michael // Feb 4, 2007 at 2:50 am

    Hi Chris,
    Just wanted to let you know I took your advice and I am much happier because of it! Great update with the custom.css file! /cheers

  • 26 Alistair // Feb 4, 2007 at 4:48 am

    Hiya,

    Hmmm for some reason the custom sheet just doesnt work for me. I put

    .custom h1 {display:none; font-size: 3.6em; letter-spacing: -0.03em; }

    in the sheet and did not modify the style sheet and it did not work…so I had to go back and change the original style sheet again.

    Any ideas ?

    Alistair

  • 27 Chris // Feb 4, 2007 at 2:35 pm

    Alistair — In the original style.css file, the <h1> tag in the header is actually defined by the specific pointer:

    #masthead h1

    In order to override that style, you’ll need to point to this element in your custom.css file:

    .custom #masthead h1

    Because of CSS specificity, elements pinpointed with IDs (#) take precedence over those pinpointed with classes (.).

  • 28 Jack // Feb 4, 2007 at 3:25 pm

    Thanks, Chris. Problem solved. Am delighted with how the theme works - now I just have to get some nice bicycle images for the random header…

  • 29 Clarke // Feb 4, 2007 at 11:35 pm

    I upgraded to 1.1 today and it works great. I especially like the custom stylesheet option.

  • 30 Mark // Feb 5, 2007 at 8:13 am

    Chris, you are the best! Just upgraded to 1.1 and added my very few mods into custom.css and voila! Now I’ll be able to do a bit more since I understand CSS, but php and MySQL are kicking my rear.

    Everything looks good, except for the random headers. Sorry if I missed it, but do I have to switch to the updated random headers file? I’m assuming something was changed in the code somewhere and I need to, but have to head out the door…

    Thanks again so much!

  • 31 Chris // Feb 5, 2007 at 8:31 am

    Mark — If you want to implement random headers with Cutline 1.1 or newer, you’ll need to snag one of the files from here.

    Once you’ve got the new header.php file, check to make sure that you won’t be overwriting any changes you’ve made to your current header.php file. If everything looks good, upload the new one to you server, and you’ll have random headers!

    For more info on how these work, check out the original post on the topic.

  • 32 CutLine 1.1 en español — El Canasto // Feb 5, 2007 at 12:01 pm

    […] el tema de WordPress diseñado por Chris Pearson, ha sido actualizado a versión 1.1. El Canasto utiliza una versión adaptada de este tema, y por que la versión 1.1 tiene algunas […]

  • 33 Mark // Feb 5, 2007 at 2:27 pm

    Thanks Chris, will do.

  • 34 Sirthinks // Feb 5, 2007 at 5:14 pm

    You da man!! This theme rocks my socks!!

    One questions though, Is it possible to disable your Tags and use Jerome’s instead? for some reason I can’t find the tag coding anywhere. Am I just blind, or is my Firefox SEARCH stupid?

    Again… This is one awesome awesome theme!!

  • 35 Sheila // Feb 5, 2007 at 8:01 pm

    Bee-yoo-ti-ful, Chris!

    And I know you’re patient with newbie questions, so here goes.

    I want to add Categories to the Sidebar.

    (1) Do I use your new custom.css code for that? (I’m guessing not, and that instead I should edit Sidebar.php.)

    (2) Since you can’t edit Sidbar.php inside the WP Dashboard, do I copy it into, say, a Notepad file, and then upload the edited file to my WP themes Cutline 1.1 directory?

    (3) To get the actual code that will display the categories — i.e. the stuff that comes after Categories — should I just find a site that has them showing and copy it?

    Many thanks!

    Sheila

  • 36 Todd // Feb 5, 2007 at 11:25 pm

    I just upgraded. You rock!

  • 37 Sirthinks // Feb 6, 2007 at 1:09 am

    @Sheila: You can edit sidebar.php in the WP dashboard….. at least I can… you could also get the custom categories widget from http://tech.windsofstorm.net/wordpress/category-widget/
    if you are using the widget-plugin from Automatics.

    Now my question? Does anyone have the latest release of comments-quicktags? There is no link to the download from the author’s page.

    If anyone has a copy, stop by my site and leave me a message either in the guestbook or on the comments page!

    Thanks…. John

  • 38 Aldian Prakoso // Feb 6, 2007 at 6:42 am

    Hi Chris,

    My wife and I are using one same blog. I just wonder if it’s possible to add “Posted by” in the post title? If it is, would you please let me know how?

    Cheers,

    Aldian

  • 39 Sheila // Feb 6, 2007 at 10:39 am

    Hi John,

    In my Dashboard, I have a message under each of the files, including Sidebar, that says: “If this file were writable you could edit it.” (Which I take to mean: This file is NOT writable.)

    Do you know if there’s a setting somewhere I need to change?

    Also, Chris, I believe that you have mentioned that you don’t like using Widgets because they muck up good themes. True?

    Grazie,
    Sheila

  • 40 Sirthinks // Feb 6, 2007 at 11:59 am

    Sheila:

    You will need to use your FTP software and chmod the files attributes to 644 in your themes’ directory.

    Widgets can muck up themes. In some cases you can tweak them to make them work. The widget I told you about will make a list of your categories that will match your theme, or alternatively you can tell it to make a drop-down type list.

  • 41 Sirthinks // Feb 6, 2007 at 12:00 pm

    Sheila:

    the alternative is to get your attributes right on your files and then edit your sidebar.php

  • 42 Mark Mathson // Feb 6, 2007 at 12:42 pm

    Awesome! This is perfect, I look forward to customizing my blog with the custom.css. Excellent idea.

    I know this is a simple question, however, I need to ask it. How can I add my blog title to the title of posts and pages? Similar to how this test site http://cutline.tubetorial.com does it? For example: ‘About | Mark Mathson’ rather than just ‘About’ being in the title.

    Thanks much, and I am happy to have found the Cutline theme.

  • 43 Sirthinks // Feb 6, 2007 at 1:07 pm

    @Mark

    go into your headers.php file and find the line

    /href=”/about/”>about –> /

    Change it to

    /href=”/about/”>about mark methson —>/

    Hope this helps

  • 44 Sirthinks // Feb 6, 2007 at 1:21 pm

    oooops

    Can someone tell me what I need to use to stop code snippets from converting to their html form when trying to put them in comments? LoL

    Mark, for now, go to http://cutline.tubetorial.com/how-to-add-navigation-links/ and scroll down a little ways…..

    You will need to find the line in header.php that looks like the one on the above page.

    Simply change the FINAL ‘about’ to ‘about mark mathson’

  • 45 Eddie Corbano // Feb 6, 2007 at 4:17 pm

    Chris,

    thx for your kind words and encouragement. I already got to work!

    But how do I know, that I don’t “overedit” your critical adjustments to WP 2.1? Since I made changes to almost every file.

    Eddie

  • 46 Carrie // Feb 6, 2007 at 6:34 pm

    Hi

    I was wondering if some one could tell me specifically how to change the font size in the side bar. Whether the sidebar is using the widget or it is empty and using Chris’s sidebar it uses a very large font.

    Is there a faq on the sidebar etc.

    I understand the principle - and would appreciate your help.

  • 47 Erick Erickson // Feb 6, 2007 at 7:08 pm

    Chris,
    Any way to get AJAX implemented under Cutline (I’m a novice). Some of the bells and whistles things I can do with AJAX on other sites keep regular readers coming back to my blog.

    Thanks, and I’m a big fan of Pressrow too, which I use on my personal site.

  • 48 Kunal // Feb 6, 2007 at 11:26 pm

    Chris is amazing, of course. But you guys are awesome as well!

    I love how everyone is helping everyone out! HOpefully I can get to a point where I can help someone new to fix a bug.

    However, at this time, IM the new guy on the block. And I need YOUR help:

    I just installed wordpress, and Chris’ theme (so I have the latest version of both). I’m trying to install the sitemap - I have the sitemap.php up, and I went thru the activation page: 1. write->write page 2. just put a title 3. on the right side, under “page slug” I put “sitemap”, 4. on page template, chose “sitemap”

    And then, I published. Now, in my dashboard, I can view this page, and the sitemap shows up fine

    But when I goto my page www.stockshaker.com/sitemap, it goes to an error.

    This is the same for my “About” page, also an error.

    Do I have to activate something else?

    Much appreciated gang!

  • 49 Kunal // Feb 6, 2007 at 11:31 pm

    holy smokes! My achieve tab doesn’t work either!!!!

  • 50 Kunal // Feb 6, 2007 at 11:46 pm

    Hey guys, I figured it out. If anyone was having the same problem, its because of the permalinks. You have to mod it. Chris has already created a post to this, and you can find it here:
    http://cutline.tubetorial.com/why-dont-my-archives-and-about-links-work/

  • 51 Steve // Feb 6, 2007 at 11:48 pm

    Thanks for the awesome theme. I had an idea for your header rotation. I noted the rotation occurs primarily on different pages; On another site I used a rotate.php script for the main page, and thought why not here too? So for the Cutline theme I placed your header images in a “header” folder within the image folder, then changed the image source in your header file to” /images/headers/rotate.php ” in place of each header_1.jpg, header_2.jpg, etc. Then drop the rotate.php script in the new headers folder, and your done! This way it serves up your images and rotates them randomly on every page, for any visit, and you could probably use dozens of different images. The script is from Automatic… can’t remember where I found it, but works great! Thanks again for the terrific Cutline theme.

  • 52 My Blog is Updated, But its Still Cold as Hell Outside! // Feb 7, 2007 at 12:50 am

    […] I finished updating my blog to Cutline Version 1.1 and so far everything seems to be working great after a few minor problems.  I do have to mention […]

  • 53 Scott // Feb 7, 2007 at 7:52 am

    I just installed Cutline and also had a problem with the Archives link. I’d activate it in the Theme Preferences, but it wouldn’t show up on Manage Pages. I looked in the database with phpMyAdmin, and the post was in the wp_posts table with a post_type of static. When I changed post_type to draft, it showed up under Manage Pages and I was able to publish it. But I’m sure it’s supposed to be easier than that. :-)

  • 54 Scott // Feb 7, 2007 at 8:00 am

    (I meant post_status was static, not post_type… sorry!)

  • 55 Shulvy // Feb 7, 2007 at 3:49 pm

    Hey Chris, I am just starting on this adventure of using wordpress and cutline (started yesterday). For some reason my site looks exactly like it should when opened in firefox but when opened in IE the side bar does not stay on the side. What can be done to fix this problem?

  • 56 Paul // Feb 8, 2007 at 4:48 am

    So pleased I found cutline at the beginning of my next project…tis a thing of beauty indeed.

  • 57 Chip Kruthoffer // Feb 8, 2007 at 2:54 pm

    Trying to make the post author show and following the advice here:

    http://cutline.tubetorial.com/professional-posting-with-cutline/

    but it isn’t working. Is this a change or am I just missing something?

  • 58 Wet Paint at MarloElaine // Feb 8, 2007 at 7:19 pm

    […] of 2006. It was about time for me to freshen up the look and functionality of the site. I chose the Cutline 1.1 theme because of it’s clean look and easy to update stylesheets. I wanted a fast loading site […]

  • 59 Aldian Prakoso // Feb 8, 2007 at 7:56 pm

    Hi Chip,

    I found out how to make the post author shown. Go to index.php then delete between “by “.
    I’m using 1.07, hopefully it’s the same with 1.1.

  • 60 Aldian Prakoso // Feb 8, 2007 at 7:59 pm

    Oops, sorry. It didn’t show up again. Delete “” between “by … the_author()…”

  • 61 Chip Kruthoffer // Feb 8, 2007 at 9:48 pm

    Thanks, but I have:

    ” rel=”bookmark” title=”Permanent Link to “>

    and still no authors showing?

  • 62 Chip Kruthoffer // Feb 8, 2007 at 9:49 pm

    Sorry, that would show all the code:

    >

  • 63 Chip Kruthoffer // Feb 8, 2007 at 9:49 pm

    bah, code won’t show! Sorry. Still looking for a fix :-(

  • 64 Chip Kruthoffer // Feb 9, 2007 at 9:47 am

    I’m a moron, I found it. I was just missing a “>”

    Sorry to bother everyone. Thanks for the theme, Chris.

  • 65 Adam // Feb 9, 2007 at 2:28 pm

    Hey Chris,

    Just a quick note of thanks for all of your hard work.

    I recently launched www.BadSlacks.com using a somewhat stripped down version of Cutline and it’s been working great.

    Thanks again, -Adam

  • 66 Vince // Feb 9, 2007 at 4:29 pm

    Love this theme & WP 2.1 :] but i got a question ;> is there an easy way to add a background image (only to the left & right of the blog..) i added a bg-image body tag but then i have to add a white bg to the header,footer,content,sidebar etc. and even then some parts aren’t covered

  • 67 Chris // Feb 9, 2007 at 9:07 pm

    Vince — The only way to accomplish this reliably is to wrap the <div class="container"> element with another <div>. You’d need to apply horizontal padding (say, 30px per side) to the new <div>, which would bring your overall layout width to 830px.

    Once you’ve done that, you can apply a background image (or color, or whatever) to the body element, and you’ll start to see the results you’re after.

  • 68 Tallawang // Feb 9, 2007 at 11:44 pm

    A very newbie - I have uploaded Cutline 1.1 but WP tells me it is missing a Stylesheet. I appear to have Style.css and custom.css in my Cutline 1.1 folder and am using Firefox 2.0.0.1.

    Any suggestions would be much appreciated
    CC

  • 69 V // Feb 10, 2007 at 8:27 pm

    Great theme, I just have one (or a few) questions. How do you add an edit button next to post titles or something that shows when you’re logged in as admin? Something like K2. And where in the CSS in the section about bulletpoints? Because I really want to change the bullet point image into something else.

  • 70 Sucharith // Feb 12, 2007 at 3:11 am

    Hi,

    Thanks a ton for the fix Chris. Can you please let me know how to write a CSS code. If possible can you educate us with a video on some basic rules and how to use the Custom CSS feature.

    I would also like to congratulate you on such an achievement.

    Thanks

    Sucharith

  • 71 Gahlok // Feb 14, 2007 at 3:08 pm

    the custom css isn’t really working out for me, sometimes I change things that get changed, and other times things don’t change. For example, I’m trying to change the font used in the blog, from Georgia to Lucida Grande.

    So I edit the body tag with this

    .custom body { background: #fff; color: #333; text-align: center;
    font: 62.5% ‘Lucida Grande’, LucidaGrande, Lucida, Helvetica, Arial, sans-serif;
    }

    but it doesn’t work. It seems that the .entry p has something to do, but body is in a higher level ? Also when I change .entry p not everything changes…

    So complicated T.T

  • 72 George // Feb 14, 2007 at 3:15 pm

    btw great theme. how do i make the background color white where the comments and sidebar is only? also, how do i put the sidebar on the other side and quite possibly make the width of it smaller if i need to?

    here’s the visual aid:
    http://www.okayrobot.com/blog

  • 73 George // Feb 14, 2007 at 3:17 pm

    i meant posts not comments. whoops!

  • 74 Matthew // Feb 15, 2007 at 5:33 pm

    I’ve used Cutlines on five blogs now and every time you update it just gets better.

    Blog number 6 is going up now with Cutlines 1.1 and Wordpress 2.1 - this should be good.

  • 75 Matthew // Feb 15, 2007 at 6:08 pm

    Archives not working!
    I’ve done everything.

    Permalink is done. Cutline Options done. When I click manage pages and I only have the About Page. No Archive page.

    ?

  • 76 Graham // Feb 15, 2007 at 6:25 pm

    Hay there Chris i cant wait to get going with cutline 1.1 but I dont know what I’m doing wrong . Ive loaded the cutline theme onto WP via DW8 but when I look at the presentation section in WP I get ‘template and style missing ‘ I realise there is something to do with custom.css but Ive only recently started to work with WP and i’m not clear what its asking me . does it mean i have to load an older cutline first ?
    or something?

  • 77 Robert Richard // Feb 15, 2007 at 8:35 pm

    Hello,

    I have permanently adopted Cutline for reason that I am assured that updates will be provided in crucial moments such as migration WP to 2.1, which is hard to find within the WP community. This said, I have partially translated Cutline to French, this said, which file can find the location to translate: [Read more →]? I am doing a hard translation for now, and hope to research the possibility of doing it with the .po and .mo.

    Thanks for your support.

  • 78 Sirthinks // Feb 15, 2007 at 9:54 pm

    @ Robert Richard:

    archive.php and index.php

  • 79 Matthew // Feb 16, 2007 at 5:06 am

    Sorted out my Archives. In phpMyAdmin I saw that the archive entry in the wp_post table was set to “post” in the post_type field. I changed it to “page” and voilà!

  • 80 Fredric // Feb 17, 2007 at 8:20 am

    Slowly migrating our site to wordpress and will be using the cutline as a base theme.

    Can’t get the archives and sitemap working. I changed the permalink structure. I modified the post_type for ‘archives’. Should I change it to ‘publish’ in post_status as well? Do I also need to create a sitemap page through the WP dashboard?

    Thanks again for the theme.

  • 81 Fredric // Feb 17, 2007 at 8:27 am

    Don’t know what I did. Didn’t change any files. Went into the ‘About’ page via the WP dashboard, clicked the ‘Archives’ from the preview at the bottom and it worked.

  • 82 Misguided // Feb 18, 2007 at 12:12 am

    Hi, Thanks for the excellent theme and updates.

    I customized the theme using your random header and also changed the top menu. It now links to specific categories.

    My question is this:

    How can I get more posts displayed in category view.

    Wordpress seems to display the same number of posts in category, and frontpage views. I would like it if more posts are displayed in category view.

    Thanks

  • 83 Charlie // Feb 18, 2007 at 1:58 pm

    Super duper! You are possibly the most patient and hepful dev I have come across. And I use a Mac, so I’ve met lots of good ‘uns!

    Your CSS is very very easy to read and modify. In fact, apart from one or 2 tweaks to php files, I have changed the template a lot. Ahh, CSS, how we love you.

    Anyhow. No questions. Just a thankyou. And you can look at the site if you like.

  • 84 George // Feb 19, 2007 at 2:16 pm

    btw great theme. how do i make the background color white where the posts and sidebar is only? also, how do i put the sidebar on the other side and quite possibly make the width of it smaller if i need to?

    here’s the visual aid:
    http://www.okayrobot.com/blog

  • 85 Jay // Feb 19, 2007 at 8:33 pm

    Any easy way to convert Cutline to a 3-column format with main column in the middle and sidebars at left and right?

  • 86 ade // Feb 20, 2007 at 4:53 am

    Just finished modding it. Cutline’’s awesome!

  • 87 raf // Feb 20, 2007 at 2:43 pm

    hi…
    apart cutline, do you have any other theme?

    pressrow is not more in progress?

    any other?

    i loved the style of pressrow… the caracthers… ;)

    however, cutline is wonderful!

  • 88 Lisa Sabin-Wilson // Feb 21, 2007 at 2:13 am

    Good think I checked here before completing my chapter including Cutline! heh - guess I shoulda put Cutline in my Bloglines. Can you just hold off until after August now, ok? :p

  • 89 Lisa Sabin-Wilson // Feb 21, 2007 at 2:13 am

    OH - and killer updates, too. Kudos!

  • 90 george // Feb 21, 2007 at 11:57 pm

    SOMEONE PLEASE HELP!!!!!!!

    btw great theme. how do i make the background color white where the posts and sidebar is only? also, how do i put the sidebar on the other side and quite possibly make the width of it smaller if i need to?

    here’s the visual aid:
    http://www.okayrobot.com/blog

  • 91 boooda // Feb 22, 2007 at 9:06 am

    Chris:
    Love Cutline 1.1 and have it installed on WP 2.1.1
    A wee problem:

    I have this annoying extra thing that shows up on my “more” tags . See the extra (->) in the sample here.

    –>Keep reading →

    How to fix this, please?
    Many thanks.

  • 92 Jim // Feb 22, 2007 at 2:12 pm

    Chris,

    Like most people here, just wanted to say thank you for all your hard work. Of all the themes out there, yours just seems to be the cleanest and best - not only for looks, but also for the code - there’s just something about it that seems rock solid.

    Which brings me to my question - is there anyway you could incorporate an option to have a separate front page, like say the GridLock theme?

    In other words, I want to keep my site the way it is, but it would be great if when you click on Front Page, you could get a page with the most recent article, a featured article, and maybe the most popular?

    I could try doing it myself, but I know if you do it - it will be rock solid!

    Thanks again for a great theme.

  • 93 Wendy // Feb 22, 2007 at 2:36 pm

    Love the themes! I am using PressRow and cannot get the number of posts on the front page to be higher than 3, even though I have gone into Options-Reading and changed that number. Help! Is there code I need to add somewhere?

  • 94 marlyse // Feb 22, 2007 at 2:42 pm

    Any idea why all titles go… cryptic? This is in Safari, latest OSX version. I am stumped. See a screenshot - this is a screenshot from your site. But the same happens if I install and use it out of the box.

  • 95 Chris // Feb 22, 2007 at 2:50 pm

    Marlyse — Somehow, the Helvetica font has become corrupted on your system and is being replaced with characters from another language.

    I’m not sure about an accurate fix for that issue, but that is most certainly the problem.

  • 96 Jesse // Feb 22, 2007 at 4:48 pm

    Hey Chris, awesome theme. Is there a way to move the sidebar to the left?

  • 97 Patrick // Feb 22, 2007 at 10:39 pm

    I have been poking around looking at the css (something I don’t know much about) and can’t seem to balance padding the left margin of the content box so that there is a few pixles of space between the posts and the colored body background…with out messing up the sidebar…any help

  • 98 Matt // Feb 23, 2007 at 8:19 am

    I just installed cutline at gatorhost. I am able to create a page and it is published. but when i click on it from the live site i get a 404 error.

    Anyone know how I can fix this?

  • 99 Rod // Feb 23, 2007 at 8:52 am

    Hi. I have used your expertise and because of your hard work it has prompted me to learn more about css and the modification of mt site. I do have a ? though. I would like to change the area outside of the content? container? entry area?… I am not sure where to look in the css. I know how to change the general background color. In the Personified page the gray area around the middle part is exactly the part I would like to change on my site. Any help of course is appreciated.

  • 100 Chris // Feb 23, 2007 at 8:55 am

    Matt — Just looking through your site, I believe that you probably just need to adjust the Post Slug for the article that you’re talking about.

    Every link appeared to be active with the exception of the Sitemap, which you may or may not have taken the steps to activate. If the problem lies with a different link, please let me know.

    Jesse — Try assigning a float: right property to #content, and also change the padding definition of #content to padding: 0 0 0 40px. This should flip the two columns.

  • 101 Matt // Feb 23, 2007 at 9:14 am

    Its fixed but now i have another prob. I fixed by changing the Permalink option to Date and Name based. After which the About worked, but the “Services” page didnt. I than went into Presentation>Options>Header and changed added the code to recognize the “Services” page. But even now when i add a new page, Cutline does not recognize it unless i add the code manually. Any way I can make this work automatically?

    Thanks Chris!

  • 102 Chris // Feb 23, 2007 at 9:27 am

    Matt — That kind of behavior is in place by design. As far as site building is concerned, having the navigation bar automatically link up every page you create would be a disaster for some folks.

    In your case, it’s clear that you would prefer to only use pages in this capacity, so you may be able to employ the wp_list_pages() function in order to achieve the result you’re after.

    Try checking out the WordPress Codex for more help on this topic.

  • 103 Matt // Feb 23, 2007 at 9:36 am

    ic! I actually prefer the way it works now. A little more work but hey, i can create unlimited pages and not have it link on the horizontal navigation! awesome! by the way, i just found Cutline a week ago and I was lucky enough to have it as my 1st theme :)

  • 104 Matt // Feb 23, 2007 at 10:48 am

    Check out this cool Plugin for flickr. this is not the rss.

    http://tantannoodles.com/toolkit/photo-album/

  • 105 Jesse // Feb 23, 2007 at 10:49 am

    Thanks Chris, that worked perfectly.

  • 106 Matt // Feb 23, 2007 at 10:17 pm

    Am i smoking something? earlier today I had an advanced toolbar when posting. Now it reverted back to the old style.
    http://i16.tinypic.com/48rnfjq.jpg

    Did i screw up code or is this a simple fix?

  • 107 Chris // Feb 23, 2007 at 10:21 pm

    Matt — You’ve turned off the Rich Visual Text Editor, which is something that I actually recommend if you’re comfortable with simple bits of XHTML like lists, sub-headlines, blockquotes, and the like.

    You can turn the editor back on under the Users tab (I think).

  • 108 Matt // Feb 23, 2007 at 10:25 pm

    Damn you are fast! I am not too great with html but i learn fast. I want the links to open in a _blank but dont know the code. the editor help.

    Curious, why do you recommend turning rich vis editor off?

    Enjoy your weekend.

  • 109 Chris // Feb 23, 2007 at 10:49 pm

    Matt — Personally, I don’t like to use the Rich Visual Text Editor because I’ve found that it is quirky with regard to the resulting markup.

    Oftentimes, you’ll see extra line breaks (<br />), empty paragraphs, or other random weirdness in the markup, and based on my own experience, you can avoid these inconsistencies by using the regular old text editor.

  • 110 Matt // Feb 23, 2007 at 11:52 pm

    Last question for a while.

    I built a contact form thru phpformGenerator.
    http://keywordmgmt.com/phpform/use/Contact/form1.html

    How do i frame this into a new page called contact?

  • 111 Matt // Feb 24, 2007 at 12:42 am

    Nevermind the last ?

    I found a pretty good form program which also has a web based sql database for me to check all the form data. www.formlogix.com

  • 112 Nico // Feb 24, 2007 at 11:09 am

    Hi, your theme is great! Now is running in my blog (i did some change).
    Thanks!

  • 113 Matt // Feb 24, 2007 at 1:05 pm

    Chris, I have a screen shot for you with my question. How do I put in a page title into cutline without it appearing in the body of the post?

    ie my about page http://www.keywordmgmt.com/about/

    vs your about page
    http://i16.tinypic.com/2vskzk1.jpg

  • 114 Matt // Feb 24, 2007 at 1:23 pm

    lol. I simply deleted this line of code.

    And i will just add my own heading to the page when i write the post. tell me if there is a better way.

  • 115 Djubba // Feb 25, 2007 at 1:45 pm

    Yo Chris, just wanted to get in on the act, by stating my Thx for the Cutline theme. I’ve been using it in WP.com for some time… and more recently have dropped my website on my host and converting to the latest Vesrion of your fantastic theme, purely because the Archive/Sitemap. Thx heaps, and all the best with your endeavours and future projects. Cutline + WP = a great partnership… here’s hoping my Host doesn’t crack under the “rush” of traffic ;-)

  • 116 Aylwin’s DevSite » Blog Archive » Cutline v1.1 optimized for WPG2 // Feb 25, 2007 at 3:41 pm

    […] requested, I’ve optimized Cutline 1.1. Apparently, it only works with Wordpress 2.1.x so please take note. You can see it working on my […]

  • 117 Wordpress 2.1.1 and Cutline 1.1 // Feb 26, 2007 at 6:31 pm

    […] went quite well, nothing broke significantly. I also updated to the latest version of the excellent Cutline theme. I also used the opportunity to clean up my list of plugins (many I had enabled for testing, […]

  • 118 Epat // Feb 27, 2007 at 2:20 pm

    nice themes ;-)

  • 119 Naples Real Estate // Feb 27, 2007 at 2:28 pm

    Thanks for the fantastic theme! I use this on my real estate blog and love it.

    Thanks again!

  • 120 Kevin G. // Feb 27, 2007 at 7:11 pm

    Hey Chris,

    Just upgraded to WP 2.1.1, and upgraded to Cutline 1.1 as well. I had been using the older version of WP along with Cutline, and a slightly modified header.php file.

    Now since I’ve upgraded, I did hack the header.php file once again, just to display a static header across all pages, and also to link this header image back to the main blog page.

    Ever since the upgrade, I seem to be having some 404 issues with any “static” pages within WP. This includes the Archives, About, Site Map pages. I’m guessing this could be a .htaccess issue, but my other rewrites seem to be working when you click a link for a previous post.

    Any suggestions to get these links working again?

  • 121 marlyse // Feb 28, 2007 at 12:56 am

    Chris - thanks for your tip, you nailed it, there was a problem with my fonts - basically what happened is that some cryllic helvetica became part of my helvetica collection and the moment I turn these off, all is good.

  • 122 GEORGE // Feb 28, 2007 at 12:13 pm

    SOMEONE HELP ME PLEASE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

    btw great theme. how do i make the background color white where the posts and sidebar is only? also, how do i put the sidebar on the other side and quite possibly make the width of it smaller if i need to?

    here’s the visual aid:
    http://www.okayrobot.com/blog

  • 123 Jack // Feb 28, 2007 at 2:47 pm

    I can’t get my archives page to create itself. I’ve repeatedly tried ticking the box on the Cutline Options page, but nothing happens.

    Should I manually create an archive page? If so, what code should it contain?

    Thanks!

  • 124 Jack // Feb 28, 2007 at 4:11 pm

    Disregard previous. I solved the problem by selecting the Template: archives in the Page edit panel.

    All running well!

  • 125 Cliff // Feb 28, 2007 at 11:43 pm

    Chris - I have the same problem as Gahlok describes above. Some things work with the custom.css, and others do not. Specifically I am trying to change the background and some font colors, so I tried this first.

    .custom body { background: #000; color: #fff; }

    .custom a:hover { color: #000; }

    The body and font color does not change, the hover color does change. I am not sure what to do to fix this…any suggestions?

  • 126 Fredric // Mar 1, 2007 at 6:05 am

    Great theme! Thanks again!

    We’re up and live on ybpguide.com.

  • 127 Ecohuman // Mar 1, 2007 at 1:16 pm

    how DO you add a background image, exactly?

    i’ve got a horizontally gradated image all ready to go, but i can’t seem to make it work–how (and where) do i add the HTML to make it work?

    thanks!

  • 128 madzzoni // Mar 1, 2007 at 5:09 pm

    Hello Chris… Thanks for this nice theme :-) Cutline 1.1 is just great and very easy to customize to one’s needs - i made a danish translation of the original for the DK audience… hope it’s OK that i use one of your graphics for download section.

    Keep Up The Good Work ;-)

    //madzzoni

    http://www.madzzoni.dk/cutline/

  • 129 Chris // Mar 1, 2007 at 7:54 pm

    Madzzoni — That’s fine by me. Thanks for extending the reach of the theme!

  • 130 Vinod V // Mar 2, 2007 at 12:43 am

    Hi,

    Great theme. I use a moderately modified version on my new site - http://heavenlypeas.com.

    Kevin G - I think your problem is the permalinks. Try re-generating them using Wordpress Options -> Permalinks -> Update Permalink structure.

    I have put a few tutorials on my site - enabling Livesearch on Cutline, Ajax Commenting on Cutline etc. on my site. Check them out.

    /vv

  • 131 Chris // Mar 2, 2007 at 12:56 am

    Vinod — I’ll second you on that, and I’d also like to add what a great job you d