Just a thought

[chris ashdown]

As there seems to so many problems updateing from older versions and all the extra codeing that must be added to the software to overcome these problems

Would it not be better and easier to take the upgrade out of Actinic and run it as a seperate program you ran prior to running the next version of Actinic

That way the upgrade program could do just that and stop interfearing with the main program, You could have a seperate upgrade program for each old version

[jont]

There has been a similar request to separate the content from the design side of things ... rather than going through the upgrader or the hierarchical import routes if the data was held separate to the design this would facilitate an easier upgrade as it could be dropped straight into the default theme with no legacy issues at all with everything blizted back to factory default.

[Darren B]

Hmmm i like the idea

mind i wish v9.0.1 would not upgrade sites on the same version either

[Mike Hughes]

I have to admit I think the actinic structure at the moment is a mess.

Why did they ever decide to put layout and CSS information in the database? All this does is make the database larger than it needs to be and make it impossible to fix a problem in those areas (such as the recent example where someone had a recursive php loop that crashed actinic).

So now there's some formatting and layout in the database and some externally, making it impossible for anyone to know where stuff is held. It also means you have to use actinic to do your editing as that's the only thing that can access the html.

So we end up with a mish mash of stuff that makes it hard to control the content and a bloated and inefficient database. Very poor.

Mike

[Darren B]

(such as the recent example where someone had a recursive php loop that crashed actinic).

Oh yer tell me about it school boy errors that are not forgiven easily,actinic always has to teach you a hard lesson