I have a page with a view that lists products. Each product has an "add" button which is just a cred form with no fields. I've set the cred form to use AJAX. Sometimes there are multiple products in the list, and each has its own "add" button. For some reason only the 1st "add" button works. The other "add" buttons don't do anything.
Here's a link to a page that shows the multiple "add" buttons. hidden link
You do have to be signed in to see the cred form work, so please go ahead and create a new account on this site.
Can you please help me fix the issue with the multiple cred forms not working when AJAX is enabled?
I created an account and saw that the first button succeeds in adding an item to the submittal list whereas as the next buttons don't, but for me to understand what's happening I really need to see how this is set up.
Can I get admin access to the site?
I will mark your next reply as private so that I can get log-in credentials from you—you may want to create a temporary admin user for me to use that you can later delete (or update the user I just created with email address nigel.a@onthegosystems.com. And be sure to have a current backup of your site, even though I don't intend to make any changes.
Can you confirm what custom code if any is used on this page with these forms, and where I can find it?
As an aside, please note that your form to register users is affected by a current issue with User registration forms that have notifications and are submitted via ajax. I get an error message to say the email address has already been registered (I ended up creating two accounts because of this). We don't currently have a fix, and you should disable ajax on that user form for the time being.
I could see the issue on your site, and I reproduced it on a local test site.
I found an internal ticket where something similar is already being investigated by the developers, so I've added information about your case to that ticket, and I'll update you when I have some feedback to share.
Reviewing this it seems like the issue has been fixed (it doesn't happen with the current version), although it is not clear from the internal tickets when exactly.
Could you update then check again and let me know if you still see the problem after updating.
