Can't create form : Unknown column 'allow_edit_submissions' in 'field list'

[wargreen]

Please use the 👍 reaction to show that you are affected by the same issue. Please don't comment if you have no relevant information to add!

Describe the bug
Impossible to create a new form after upgrade to NC 31

To Reproduce
Not sure

Expected behavior
No error when creating form

Screenshots
If applicable, add screenshots to help explain your problem.

Nextcloud (please complete the following information):

• Nextcloud-Version: 31.0.8 / 31.0.9
• Forms-Version: 5.2.1

Desktop (please complete the following information):

• OS: Debian SID
• Browser: firefox
• Version: 143.0.3 (64 bits)

Browser log

POST https://cloud.*****.**/ocs/v2.php/apps/forms/api/v3/forms 500
<?xml version="1.0"?>
<ocs>
 <meta>
  <status>failure</status>
  <statuscode>996</statuscode>
  <message>Internal Server Error
</message>
 </meta>
 <data/>
</ocs>

** Nextcloud log**

[no app in context] Erreur: An exception occurred while executing a query: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'allow_edit_submissions' in 'field list'
	POST /ocs/v2.php/apps/forms/api/v3/forms

    "message": "An exception occurred while executing a query: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'allow_edit_submissions' in 'field list'",
    "exception": {
      "query": "INSERT INTO `*PREFIX*forms_v2_forms` (`owner_id`, `hash`, `title`, `description`, `access_enum`, `submit_multiple`, `allow_edit_submissions`, `show_expiration`, `expires`, `is_anonymous`, `created`, `last_updated`) VALUES(:dcValue1, :dcValue2, :dcValue3, :dcValue4, :dcValue5, :dcValue6, :dcValue7, :dcValue8, :dcValue9, :dcValue10, :dcValue11, :dcValue12)"
    },

Additional context
Add any other context about the problem here.

[Chartman123]

@wargreen it looks like some DB migration to the latest scheme didn't run during your latest Forms updates... Did you see any error messages while updating Forms/Nextcloud?

[wargreen]

No issue at all nor errors when upgrading...

[Chartman123]

@wargreen could you please run occ upgrade and see if this runs the migration steps?

https://docs.nextcloud.com/server/stable/admin_manual/occ_command.html#command-line-upgrade

[wargreen]

sudo -u www-data php occ upgrade
No upgrade required.

Yesterday, after seen this issue, i've upgraded from 31.0.8 to 31.0.9 for see if the upgrade fix that. And no luck !

[Chartman123]

could you please use this command and look at the output?

NC_debug=true sudo -u www-data php occ migrations:status forms

If there are 'pending' migrations or 'Next version' doesn't state that your at the latest migration step, please run this afterwards:

NC_debug=true sudo -u www-data php occ migrations:migrate forms

[wargreen]

I got :

  Command "migrations:status" is not defined.  
                                               
  Did you mean one of these?                   
      encryption:status                        
      migrations:preview                       
      twofactorauth:state     

[Chartman123]

NC_debug=true sudo -E -u www-data php occ migrations:migrate forms

Sorry I forgot the -E flag...

[wargreen]

The output is empty

[Chartman123]

Did you only run the command in my last post or did you add the -E parameter to the first command as well? The second one normally doesn't show no output if there's no error. Could you try to create a new form again?

[sbaecker]

Old form data does not have this attribute, therefore the code fails trying to access this attribute. The attached patch sets default (false) if this attribute does not exist. Use at your own risk...

forms.patch

[Chartman123]

@sbaecker this wouldn't help in this case here. We're talking about creating a new form in the latest Forms app version. FormsMigrator.php only comes into action when a user exports/imports his/her user data.

[sbaecker]

Forms app didn't want to start on our site (NC 31.0.5), neither with old forms nor for creation of new ones. No explicit import or exports involved. Logfile showed problems with that same attribute, but not within the database - correct.

I checked migrations according to your suggestions - all were up to date.

Maybe topic starter will head into same trouble as we did, once his migrations are fixed.