Strange behavior deploying new templates

[Greg Kerdemelidis]

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