Re: [rt-users] Custom fields validation on moving between two inactive states, after upgrade
the file share/html/Ticket/Modify.html changed in such a way that my "Default" callback was actually breaking custom field validation Not so simple: I removed all the "local" directory, including plugins, stopped apache, cleaned mason obj, and mandatory CF are still not validating. Maybe it's something in 4.0.9. Being an outdated version, I will not annoy you anymore about that. Regards, Bergonz -- RT Training - Dallas May 20-21 http://bestpractical.com/training
Re: [rt-users] Custom fields validation on moving between two inactive states, after upgrade
I recently upgraded from 4.0.9 to 4.2.3 and some users tell me that the behaviour of mandatory custom field changed. I recovered the old installation and DB from backups and the mistery is solved: from 4.0.9 to 4.2.3, the file share/html/Ticket/Modify.html changed in such a way that my "Default" callback was actually breaking custom field validation in 4.0.9, and is not any more breaking it in 4.2.3. Best regards, Bergonz -- RT Training - Dallas May 20-21 http://bestpractical.com/training
[rt-users] Custom fields validation on moving between two inactive states, after upgrade
I recently upgraded from 4.0.9 to 4.2.3 and some users tell me that the behaviour of mandatory custom field changed. We have two "inactive" states: the usual "new" and "to be done". They say that moving a ticket from "new" to "to be done" did not require filling the mandatory CFs in 4.0.9 and does require filling them in 4.2.3. Before I recover 4.0.9 from backups and make a test installation, does anybody know if I missed something from the release notes? I tried to read them all, but I did not see anything about this. Thanks in advance, Bergonz -- Ing. Michele Bergonzoni - Laboratori Guglielmo Marconi S.p.a. Phone:+39-051-6781926 e-mail: berg...@labs.it alt.advanced.networks.design.configure.operate -- RT Training - Dallas May 20-21 http://bestpractical.com/training
