Error when submitting form

Hello Aicha,

First of all my best wishes for 2018.
I have the following error when submitting forms :

Erreur lors de la soumission du formulaire
Problème à la sauvegarde des données. Duplicate entry '0' for key 'PRIMARY'

You can test it at the following address :
www.swingandsway.be/index.php/contacts/envoyer-un-message

Is there a fix or a way to reset it.

Regards.

Freddy

Hi Freddy,

thanks for your good wishes! And my best wishes for you, too.

Did you make any changes to the form or is it a newly created form, where you get this error from?
Did you make changes to Visforms or the subscription (update, enable a subcription plugin, that was disabled)?
What is your Joomla! version?
What is the Visforms version?
What is the Visforms subscription package version?
Do your other forms still work properly?

The form in question has the id 2. So you could try to delete the tables #__visforms_2 and #__visforms_2_save from your database. Please note, if this form has worked at any time in the past and any sumitted user inputs were already stored, these will of course be deleted then, too.

After you have deleted the tables from the database go to the form configuration of the contact form in the administration of your webseite and just save the form (with the option "save results" enabled). This will recreate the tables in the database. Maybe this will fix the problem.

I'm not sure yet, where the problem comes from and sadly the error message is not very helpful at all.
Therefore it would be helpful to have the answers to my questions from above, even if you can solve the problem by deleting the tables from the database.

Best Regards,
Aicha

- It was an existing form where already 72 forms were submitted.
- Last update to Visforms was made on December 14th. Some forms were submitted in the mean time.
Installed versions :
- Joomla 3.8.3
- Visforms 3.10.3
- Subscription 3.1.1
Other forms still work correctly.

I followed the procedure as you suggested and result was positive.
I did first make a backup of the 2 concerned tables.
I send you the backup by email. As it contains email addresses so consider deleting it after use.
You can observe that the last record (first in the list) has an index of 0 !!!!
So the last message received an index of 0 and probably that the next message was trying to use index 1.
I could restore data in the table by copying INSERT statement and manually forcing index 72 in the last record in place of the 0.

Hope this can help you.
can be an error of MySQL !

Regards

Hi Freddy,

I'm glad to here that the problem could be fixed and you were even able to recover the submissions.
Thanks for providing me with the dump of the tables. I will take a look at it as soon as possible and delete the file afterwards. I let you know, if I can find out something but maybe it is just as you wrote an error of your sql.
Thanks for the additional information as well.

Regards,
Aicha

I had the problem also with other forms. In fact the first time I did use it, it seemed to work correctly, but it created a record with id=0. The second time, it did give the error probably because it tried again to create an index of 0.
After futher analysis, a difference between the newly created table and the previous one was that the Auto_increment attribute was not set. In fact, all the tables of VisForms do not have the auto_increment attribute.
Do I have to set the auto_increment attribute on all the tables?

Thanks and best regards

Hi Freddy,

Yes, all the data tables (including those with _save) should have an auto_increment on the id field.

This is really very strange. When the table is created, the field id is created with a primary key and an auto_increment. So it looks as if either the sql statement that creates the table does not work properly on your system or something else is wrong there.
What I do not quite understand is, that you say, that the form was working fine for a long time and only then the auto incrememt stopped working. And now, when you enforce a new create of the tables the auto_increment is not working (missing?), too.

So this seriously looks like a problem with your mysql.... and as I have not heard of this problem before it really looks to me to be a problem on your mysql. The sudden appearance of the problem could be explained with a change of the mysql on your server, for example.

Regards,
Aicha