Problem with Submitting new Instances of form and saving Edits

Hi
I have only been using Viforms Subscription for two weeks and so the problem is probably my lack of experience.

I have set up a multi-page form with many fields in an article, which gives it a great appearance and it has been working well as I develop it.

I now have 2 problems.

Problem 1. When logged in as a user with records stored in the database, I cannot raise a new instance of the form and instead get a screen with links to edit* the existing records:

You have already submitted this form. Please use the link below in order to change your data.

Edit data - recordset id is 3

Edit data - recordset id is 9

Edit data - recordset id is 10

I have tried a lot of cache settings and disabled caching entirely. The plugin for maximum submissions was disabled when the problem started and I have even enabled it with a '0' setting. I have installed Breezing Forms old Cache Control plugin configured with the article numbers. The problem is still there.

Problem 2. I cannot edit forms in the front end.  I can click on the edit link and make changes, but when I try to submit them I get the error message "The record set is not checked out exclusively. Therefore your changes cannot be saved."

* I also get this problem and message with problem 1.

I must be doing something wrong, but I need help with, maybe with my settings, to solve this please.

Nick

Hi,
1: You have at some point enabled the option ""Display edit link instead of form"  on the Form configuration tab "Basic". There is an article in the documentation about this feature; www.vi-solutions.de/en/documentations/vf...-instead-of-the-form
2: See: www.vi-solutions.de/en/documentations/vf...ck-in-of-record-sets
Regards,
Aicha

Thanks for the reply. That fixed problem 1 straight away.

I had seen the link (2.) and set the time right down to 1 minute. but problem 2 is still there.

Hi,
I think, I did not read your first post completely carefully.
Usually the message is "the record set is check out" and it would appear, when you try to open a record set for editing.
But you get a different message "is not checked out" at a different time (when you try to save your changes).

If I read your message correctly, now, you had already set the "check in " option in the Visforms configuration before your first post here?
And you had set it to 1 minute?

This is actually a bad configuration.
1 minute is much to short.

Your error message indicates, that, while one user has opened the record set for editing, another user was able to open it, too, for editing.
This is possible, because you set the low value for "auto check in" of 1 minute.
If the first user, then tries to save the data (submit the edit form), the record set is already checked in by another user.
This is the reason for your error message.

Please set the value to a higher value, i.e. 10 or 20 minutes, and try again.

Regards,
Aicha
 

Hi

Thanks for looking into this again. I have tried Frontend Edit Auto Checkin Times of 10 and 20 and 30 min, but it has made no difference I am afraid. I get the same error message.

I have logged the test user * user out, checked everything in (nothing checked out), cleared the cache, logged the user back in again and tried with just the Administrator plus the client user logged in.

* That user is member of my Clients user group. The group has the viewing access level to see the records and these permissions for the form:

Action Select New Setting Calculated Setting
Delete Not Allowed (Inherited)
Create Allowed
Edit Allowed (Inherited)
Edit State Not Allowed (Inherited)
Edit Own Allowed (Inherited)
Delete Data Not Allowed (Inherited)
Export Form Data Allowed
Export Form Data in Frontend (CSV) Allowed
Create PDF file in frontend Allowed (Inherited)
Create PDF file from own data in frontend Allowed
Edit Data State Not Allowed
Edit Data in Frontend Allowed
Edit own data in Frontend Allowed

Hi,
the permission settings are correct.
Visforms is used by thousands of people, every known problem is fixed immediately.
As nobody has ever reported such a problem before, I actually think, that the problem is cause by a bad configuration or an incompatibility with some other extension installed on the website in the first place.
This can only be fixed, by checking into the individual configuration of your website. If you need help with that, we can provide paid support.
I'm sorry for your trouble.
Regards,
Aicha