using older version of cutline

[mzimmers]

Hi, all –

I've been using an older version of Cutline (directory name is cutline-3-column-split-11) for over a year now. I notice that it is no longer listed in the themes section of the WordPress support area.

Should I be concerned? I had to make some changes to it to get it to work the way I wanted it, and I'm reluctant to try to remaster those changes on a newer version. Any suggestions?

Thanks.

http://www.scopedin.com

[sofimi]

Should you be concerned? the WordPress theme directory has its own reasons for removing themes. I'm not sure why Cutline was removed from it, but I will try to check why.

Using the newer Cutline version is definitely recommended on our part since it supports the latest WordPress features, but if your installation isn't updated either, I guess that wouldn't matter now would it? But I have to mention the security concerns of leaving your blog unupdated.

But if your WP installation is updated (or you want it to) but you don't want to get the new theme version, just integrate the support for new features, there are several guides on that. Try searching adding WP 2.7 & 2.8 features to your theme or blog.

Hi, all –

I've been using an older version of Cutline (directory name is cutline-3-column-split-11) for over a year now. I notice that it is no longer listed in the themes section of the WordPress support area.

Should I be concerned? I had to make some changes to it to get it to work the way I wanted it, and I'm reluctant to try to remaster those changes on a newer version. Any suggestions?

Thanks.

http://www.scopedin.com

[mzimmers]

Thanks for the reply.

I do not enjoy getting "out-of-rev" with software, so I suppose I should bite the bullet and cut over. This was my first exercise with WP, and with css and PHP for that matter, so my memory may be magnifying the complexity of my changes.

I suppose I could introduce *both* versions of Cutline into my WP system, and move between them until I get the new one working the way I need it. Any pitfalls with that idea?

This has been a concern of mine for some time, so I guess it's time for me to face the music. You know of any good file diff tools that run on browsers out there?

mz

[sofimi]

Yeah it depends on whether you're more comfortable with getting the old version updated or customizing the new version with your previous modifications. If you ask me it might be better to just add the support for new features in the later versions of WP since you might not need all of them anyway, and it looks like you're pretty comfortable with code. At that rate you might not need Cutline updates.

Sorry but I'm not very familiar with diff tools so I can't help you out with that part.

Thanks for the reply.

I do not enjoy getting "out-of-rev" with software, so I suppose I should bite the bullet and cut over. This was my first exercise with WP, and with css and PHP for that matter, so my memory may be magnifying the complexity of my changes.

I suppose I could introduce *both* versions of Cutline into my WP system, and move between them until I get the new one working the way I need it. Any pitfalls with that idea?

This has been a concern of mine for some time, so I guess it's time for me to face the music. You know of any good file diff tools that run on browsers out there?

mz

[mzimmers]

...so, I started taking a look at 2.2. No custom.css? This could pose a problem.

[sofimi]

You can always create a new custom.css file and save it in the same folder. By default the file is blank anyway.

...so, I started taking a look at 2.2. No custom.css? This could pose a problem.

[mzimmers]

OK...so in the same folder that the style.css file is in? I seem to recall some versions that had a "custom" subfolder.

[sofimi]

But if you're using 2.2 then it's the only version that should matter, right?

How exactly is it posing as a problem to you, by the way?

[mzimmers]

No, I'm not yet using 2.2. I'm considering upgrading to it, but I want to assess the effort involved, since I did some editing to the stock theme.

And, if all I have to do is create the custom.css file, as you say, then...there's no problem after all!

Thanks for the response.

[sofimi]

I think if you did edits you'll have to look at the PHP files as more of an issue than the CSS. Good luck with your upgrade!

No, I'm not yet using 2.2. I'm considering upgrading to it, but I want to assess the effort involved, since I did some editing to the stock theme.

And, if all I have to do is create the custom.css file, as you say, then...there's no problem after all!

Thanks for the response.