I don't always remove the contents of the Tomcat/work directory, but I have in some cases. We tried renaming and deploying it as a new template, and assigning it to the page in question - even renaming the fields and container lists. I have had some problems removing a template definition from the system - it seems to leave the field definitions in the database.
So, when you initially deploy the template, is that the point where the database structures to support it are created? It all gets a bit messy when you have a new version of a template with extra content management facilities and existing content in a page. What is the recommended procedure for this situation? Create a new template, deploy, copy the content into the new template, delete original? Only thing is renaming the new page's URL key to what the old one was called complains about a "duplicate page URL key - already exists"!! Many Thanks Serge! Regards, -Greg -----Original Message----- From: Serge Huber [mailto:[EMAIL PROTECTED] Sent: Friday, 20 August 2004 1:43 a.m. To: [EMAIL PROTECTED] Subject: Re: Strange behavior deploying new templates Are you removing the contents of Tomcat/work when installing the new templates ? Also how are you deploying the templates ? Greg Kerdemelidis wrote: > Hello all, > > We've been experiencing some strange (show-stopper) behavior deploying > new templates to an existing Jahia installation. The installation in > question has been through a fair amount of reworking, namely, new > templates deployed and the SQL datastore (mysql) overwritten with > snapshots from another server. The theory is that with the templates, > bigtext content, and appropriate tables in the database, the > installation should mirror the server we took the snapshot from. Is > this correct? > > The problem is that we put a new template into the server, and after > adding 3 entries into the first container (list) the fourth fails > every time with differing exceptions - sometimes a ClassCastException > casting to SmallText, other times a duplicate key exception. Doing a > clean installation of Jahia and carefully re-creating the content > seems to have solved the problem and the template works fine. So, how > would a duplicate key exception come about? I know that there were > some old bigtext content files that weren't related to anything in > that installation - it was legacy data from a previous build - would > this affect the system at all? > > I can supply more details (like the template) if you like, although > the specifics don't seem relevant to this particular situation - once > Jahia is tangled up it doesn't matter what template you put in - it > fails with random errors. > > Any ideas? > > Cheers, > > -Greg >
