new versions

[0273302733 +]

There seems to be a lot of talk of updated versions of 68c. I only bought v4.0.4 developer three weeks ago and it sounds as if it's out of date already. If I and my client are happy with what we've got, can we run this version indefinitely or will we have to update it at some point?
Wal.

[Lhotch +]

You can but keep in mind that often times critical bugs are fixed and failure to update, at least the files that changed, could result in a compromised site or broken functionality.

[Eric Barnes +]

Just as Larry mentioned you are under no obligation to upgrade at any point. However the only reason for upgrades is to fix bugs and make improvements. It is up to you if you wish to keep your site current.

With that in mind upgrades are released for a reason and it is highly recommended to stay current.

[outthere +]

When you upgrade to a new version how can you keep from having to edit all the settings in the pages that you have spent time on? Can you just replace the layout.tpl for example?

Thanks,
Brent

P.S. One other thing I was curious about. If I had the developer version would that make it easier for me (very little website design experience) edit the code? Like could I load them in dreamweaver for example and make it more of a wysiwyg ?

[Eric Barnes +]

When you perform an upgrade you only have to replace the files in the changelog and upload the setup folder.

I would say most of the time there is not many template changes if any. Plus you can create your own template folder and then not even have to worry about overwriting any changes.

[0273302733 +]

Yea, I have the developer version and I've made many changes to all sorts of files - templates, language file, individual files too such as placing rentable ad boxes on the home page. It would be a major headache to do it all again.
Regards,
Wal.

[jonahcoyote]

Unless I'm in the developer dark, with most systems, don't you typically have to go through a file comparison procedure when upgrading?

I use a Mac and my 68C upgrade routine involves:

1. Making an entire file and database backup.

2. Download new version.

3. Open up File Merge (part of the OSX Developer Tools - but there are plenty of other great alternatives out there for Mac and PC) and go through each file listed in the changelog, comparing my latest backup files with the new version files that have changed.

In most cases, as suzkaw stated, the template files haven't changed. When they have changed, I try and pick out the particular bug fixes and keep all my template changes in tact. Once you've worked with 68C for a while you should be accustomed to the changes you've made and be able to tell what's important and whats not. It's not an exact science, but does anybody have a better method?

At any rate, the last thing you want to do (unless you haven't customized 68C at all) is a blind overwrite with a new version. If you do go this route and you notice significant things missing, thats what the backup is for. Just copy your backup files back and start over by doing some file comparisons.

- Jonah

[Mike-N-Tosh +]

Hmm, never thought of using Filemerge. I've been using BBedit. Does Filemerge highlight the differences and allow you to simply click to add differences on an individual basis?

Thanks,
-Mike

[jonahcoyote]

Precisely, it is very nice!