template_default

[mewcat]

Oh I see, thanks for the insight. I don't remember doing this when I upgraded from 1.3.8a to 1.3.9a though. IIRC, I just copied the new template_default files to the same directory on the server without changing my custom template (unless directed by the changelog). Everything works fine, I just hope I didn't leave open any security holes by doing that.

[Design75]

That is why I did a complete remake of my site when I upgraded from 38 to 39

[gjh42]

The fewer changed files in your template, the more likely it is that you won't actually have to compare and merge them.
You need to compare the changelogs against the files in all of your custom template folders; only files that appear in both places need to be merged.

Also, a few of the changed files are mostly housekeeping or code optimization, and will still work with the old version. I wouldn't rely on this, though, unless you know exactly what you are doing.

[acedweb]

template_default does not have anything to do with the custom template.

This is why it is called default, because the files there don't matter if you change your site template or not.

This means that if the update asks you to change in there, you change in there.

Besides, its a system update, why would it want to change your custom template anyway?

[Design75]

template_default does not have anything to do with the custom template.

This is why it is called default, because the files there don't matter if you change your site template or not.

This means that if the update asks you to change in there, you change in there.

Besides, its a system update, why would it want to change your custom template anyway?

not true

[acedweb]

not true

rtfm :)

[wingc3]

Ok just to simplify things here! Based on the responses, it is better to update both our current template and also the template_default folder?

But would also require comparing the files of our current template with the changelog files right?