Anyone more clueful than me on this?
Bassman wrote:
AFAIK you can't edit the default template set, you have to clone it and edit the cloned set.
Herko Coomans wrote:
Templates_c gets it's files from the db. It's better to edit the file in the db (using the template editor), then doing it the physical way.
Herko
Mithrandir wrote:
You make sense - so much more the sense in mapping those changes so you are prepared for the new release
Mithrandir wrote:
Good luck with it.
Mithrandir wrote:
Only very few of the fixes have to do with presentation - but it may be a good idea to spend some time until we have a new 2.0.7 release to mark the changes you have made, so you can re-apply them if the files are changed
Mithrandir wrote:
1. When a new upgrade patch is released you just apply the 2.0.5 -> 2.0.6 first, then 2.0.6 -> 2.0.7 and then update the system module. There are no database changes in either versions, so it's just a matter of overwriting old files and update the system module (perhaps a bit more when we get an overview of the vulnerability fix
Mithrandir wrote:
2. One. Connected with the vulnerability fix, which we will hopefully fix properly soon
Mithrandir wrote:
3. There was in the release news item and probably will be again in the new release notes. Mainly it is an implementation of bugfixes and patches from the sourceforge project trackers.
meme wrote:
you just need to upgrade your XOOPS to 2.0.6 now then wait the new release 2.0.7
meme wrote:
just replace the files its easy