template_default

[wingc3]

I notice that in the change logs of version 1.3.9 a,b,c,d,e,f,g it shows the changed files in /includes/templates/template_default/etc.

Now do we rename the template_default folder to the current template we are using? Or should we just leave /template_default as is when updating the changelog files under this folder?

[mewcat]

I am almost positive that the changelog is referring to the files that are actually in the /includes/templates/template_default directory on your server. You should change the files in that actual directory, not the ones in your custom template.

[Design75]

no, if you customized a file you should also compare it to the customized ones, since they overrule the ones in the template_default directory

[mewcat]

no, if you customized a file you should also compare it to the customized ones, since they overrule the ones in the template_default directory

I'm pretty sure the changelog was referring strictly to the files in that template_default directory. If those changes were meant to be applied to the active (and assumed to be custom) template, wouldn't you have to manually parse the files and adapt the code changes on your own?

[Design75]

Yes you will have to compare the files and find out what to change.

[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