• Resolved shoofar

    (@shoofar)


    I built a form and it is pretty long form with many fields, though not one of them is fillable, they are mostly a “choose option fields”

    Though my form, when submit button was pressed – was returning error “something went wrong” and not allowing the form to get processed or stored in DB.

    After many many days of testing and switching each field through every combination I turned my attention to “behavior TAB” and FINALLY found the error creating option.

    I found that the problem was created by Akismet protection turned on in the form.

    When I turn it off – the form works properly, when the protection is turned on it fails the form without showing what is wrong – no info in logs either.

    Can you think of some way to have a testing field that would show what is not working or more elaborate error message than “something went wrong”.

    Maybe some button allowing to have step-by-setp to get the troubleshooting easier?

    It took me like good few months to figure it out.

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Kris – WPMU DEV Support

    (@wpmudevsupport13)

    Hi @shoofar

    I hope you are doing well today.

    In your post, you linked to a page where a form exists only with sliders. I have made a test on my lab site with selects fields and all of them are set up as Required, which allows to set up custom error messages that should help in which field there is an error (no matter if Akismet was enabled or not).

    To have a better view on your issue, please export your form into Google Drive and share a link in your next reply. Also, “mostly a choose option fields” sounds like there are different fields that possibly take action here and we will need to review that.

    Kind Regards,
    Kris

    Thread Starter shoofar

    (@shoofar)

    Hi Kris,

    See this form is working fine now as it has Akismet protection turned off.

    When I would change that (Akismet protection to “on”) it would give error “something went wrong” when trying to submit. And it would not redirect user anywhere.

    There is no need to setup individual error message to those sliders as they are always “filled corretly” – that issue was reported by me in a different post – so I think that untill it is updated there is no need to bother with “sliders” set to required.

    There are only 2 more invisible fields that do calculations and form redirects user to 4 different pages depending on the combinations of those 2 invisible fields. In tests I have them visible to check corectness of calculations. But the issue is similar no matter if I turn them visible or not.

    Whenever akismet is active it will make the form report error “something went wrong”

    When I turn aksimet off it will work correctly. No more changes have to be done.

    But if you want to check it more thoroughly – here is the link for exported form:

    https://drive.google.com/file/d/1ZdGjJZutEam7KPrKKVCOI1Ix5sI2Zjvc/view?usp=sharing

    You can just try to turn akismet protection on or off and see if it makes it fail.

    Maybe Akismet is tripped because there is no other field that could be filled with random data (like a text field) only “choose from options” fields and this trips up the Akismet? – just a random thought.

    • This reply was modified 5 months, 3 weeks ago by shoofar.
    • This reply was modified 5 months, 3 weeks ago by shoofar.
    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    Hi @shoofar

    I tested in my system with the given form export but I’m not able to replicate the issue when checked.

    Just to be sure whether the error is from the Akismet side or Forminator could you please make sure to add a custom Fail message under “Enable Akismet spam protection” as shown in the screenshot:

    View post on imgur.com

    The above would give a better idea of where exactly it’s failing, ie if the custom error message shows up then it has to be from the spam protection feature in Aksimet that’s getting triggered.

    Maybe Akismet is tripped because there is no other field that could be filled with random data (like a text field) only “choose from options” fields and this trips up the Akismet? – just a random thought.

    Unfortunately, there isn’t any way to determine what are the factors that are triggered on Akismet’s side without replicating the issue. Could you check how it behaves if you add a new field? Do you get the same error?

    I’m also bringing this forward with our developers attention to check if here are any other factors that would cause such issue.

    Will keep you posted once we get further feedback.

    Kind Regards,

    Nithin

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    Hi @shoofar,

    Since we haven’t heard from you for a while. I’ll mark this thread as resolved for now. Please feel free to open a new thread if you have new queries.

    Kind Regards
    Nithin

    Thread Starter shoofar

    (@shoofar)

    Hi sorry for not responding – busy week.

    Thank you for your involvment.

    Yeah, I get it that this might be a problem to determine how akismet works internally without working there and knowing all the details.

    So I suppose it might be a warning for other people having strange errors while submitting a form.

    Trying to disable akismet protection to check if it is the case.

    Especially when you know that your form doesn’t allow any “free text areas” and only uses “choose” fields.

    Plugin Support Nebu John – WPMU DEV Support

    (@wpmudevsupport14)

    Hi @shoofar,

    Please update us here with the test result so that we’ll be able to assist you further.

    If you need any clarification, please do let us know. We are happy to assist.

    Kind Regards,
    Nebu John

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.