• Resolved cpoakl

    (@cpoakl)


    Hello,
    Thank you for providing this plugin.

    In AltCha options, when setting the captcha integration with Contact Form 7, I am not satifisfied with where the AltCha box is positioned (after the “Send” button, whereas I would like it to be positioned before).
    So instead of crafting custom CSS rules that would break sooner or later, I disabled it and thought about setting instead custom HTML to captcha and add the [altcha] shortcode in the form editing screen just before the CF7 shortcode for the “Send” button. But in this case, Altcha’s shortcode is displayed on the frontend as text (instead of expected rendered HTML). Is there a way to change this behavior in Altcha ?

    More complex, I also have another form displayed as 3 separate screens (one for each step, using the plugin “Multi Step for Contact Form 7 Lite”). Could I imagine to put an AltCha shortcode before the Next Button of the first screen, so it wouldn’t go to the second step if the captcha is not verified ?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Daniel

    (@danielregeci)

    Hi, in the latest version 1.6.0 the widget renders above the submit button by default (as long you keep the standard html for the button); the rendering of the shortcode is fixed as well and it works with multi step forms. When using the [altcha] shortcode, select “Shortcode” in the Altcha plugin settings for CF7.

    Preventing navigation to the next step doesn’t seem to work with Multi Step for Contact Form 7 Lite I don’t think it can be fixed, but you can put the widget to the last step using the shortcode.

    Thread Starter cpoakl

    (@cpoakl)

    Thank you, I confirm the CF7 shortcode issue is fixed with 1.6.0.
    And thank you for checking the multi step point.

    However I am afraid something broke the altcha widget on other places – at least on the login page. The altcha box is not shown anymore (although it is there in the HTML), so I can’t verify and can’t log in anymore.
    Following error message is displayed (which seems unrelated to login page):

    Error : Cannot submit your message.

    When reverting to 1.5.0, it works as intended.

    Plugin Author Daniel

    (@danielregeci)

    Ah, thank you for reporting. Fixed in the version 1.6.1

    Thread Starter cpoakl

    (@cpoakl)

    Thank you for fixing it. Issue now fully resolved!

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