From Bas Toeter
What we found safe to do when you have small changes to a form is this:
1) upload your new xsd form definition
2) un-publish the form. Do that by setting the fields 'sitestate' and
'globalstate' to 0 in table 'metaobj_form_def'
3) hook your form to it's new definition by revising it and selecting
the uploaded xsd
4) restore the published state for the form, either in the database or
by clicking the publish buttons.
We did this to remove required fields from forms. So we added
minOccurs="0" to the xsd elements that did not have that yet.
I think adding non required fields would be save to do since the
existing xml would still be valid. You could probably also enlarge text
fields without a problem. When you want to remove fields things may
start to get risky. You may have to go through the created forms and
change so they would be valid under the new xsd.
In any case I would first test whatever change you are planning to do.
If you do break something you can always stick the old xsd back in.
Simon Rousseau
I've encounter this problem once, and for my part I solve it by this procedure...
- Go into my MySql server
- Found the table "metaobj_form_def"
- Set the globalState to 0 = unpublish for the specific form
- After that, you can proceed by the SAKAI interface to delete the form.
Note: In my case nobody have used the form, and if your users do, you probably
need to find the table responsible of storing users data and delete it content for the form
before destroying the form.
Sincerely,
