• Resolved llocally

    (@llocally)


    Hi, I found 2 threads on this and both are marked as resolved, yet I saw no satiosfactory answer, as they are resolved, by WordPress community rules I have to pen a new thread.

    http://wordpress.org/support/topic/jetpack-contact-form-not-working-with-do_shortcode
    http://wordpress.org/support/topic/jetpack-contact-form-not-working-in-do_shortcode

    Ok, hers the detail

    I have a multi-site, for sites that don’t use JetPack I give them Grunion Contact form (I’know that it isn’t being updated but that isn’t the issue, right now teh Grunion Code is exactly the same as the JetPack code)

    In my contact form template I have a do_shortcode call to the contact form shortcode (both Grunion and JetPack shortcode syntax is the same)

    When Grunion is enabled and JetPack disable the call to the shortcode operates perfectly.

    When JetPack is activated the form is displayed BUT the ‘send’ does not function (symptoms as above)

    So it looks the way JetPack is implemented (sequencing?) the code is causing this issue.

    In my book, if you have a shortcode, and you have a function to execute a shortcode, then if using that function causes an execution issue its a bug. What do you think?

    http://wordpress.org/plugins/jetpack/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    That’s indeed a known issue with the Contact Form module. We’ll get this fixed in a future Jetpack release. You can add yourself in cc of this ticket to follow our progress on this:
    http://plugins.trac.wordpress.org/ticket/1762

    In the meantime, you can use the solution I’ve outlined here:
    http://wordpress.org/support/topic/jetpack-contact-form-not-working-with-do_shortcode?replies=7#post-4055831

    I wouldn’t recommend using the old Grunion plugin, though; although the shortcodes are the same, we’ve made numerous updates to the Contact Form in Jetpack, and these updates and bug fixes are not part of the Grunion plugin.

    Thread Starter llocally

    (@llocally)

    Its a real shame the code lines have diverged.

    Only a few months ago Grunion and JetPack were using the same version 2.3.

    But now JetPack is on version 2.4.

    I have looked at your work around and whilst it may work, it isn’t a great solution is it.

    As I run a multi-site, retrospectively going back through all the sites and installing JetPack is a significant task as each one would need to be manually activated with a WordPress.com account, as nothing works on JetPack when not linked to a WordPress.com account.

    I chose grunion as I use (and pay good money for) Akismet and that is built into Grunion.

    Of course now Contact Form 7 supports Akismet too, I could migrate teh sites that don’t use JetPack to thta, but I do find the Grunion / JetPack form builder far more user friendly.

    Is there any technical reason that the Grunion code (as in jetpack/modules/contact-form ) can also be used as a stand alone plugin?

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    I chose grunion as I use (and pay good money for) Akismet and that is built into Grunion.

    Jetpack Contact Forms also come with Akismet support.

    As I run a multi-site, retrospectively going back through all the sites and installing JetPack is a significant task as each one would need to be manually activated with a WordPress.com account, as nothing works on JetPack when not linked to a WordPress.com account.

    If you do not want to connect Jetpack to WordPress.com, you can enable the Development mode in your network:
    http://jetpack.me/support/development-mode/

    You will then be able to use the Contact Form module without connecting Jetpack to WordPress.com.

    Is there any technical reason that the Grunion code (as in jetpack/modules/contact-form ) can also be used as a stand alone plugin?

    As you mentioned earlier, the plugin was a standalone plugin before, so it could still work as a standalone plugin today. If you don’t want to install Jetpack at all, you could extract the Contact Form module and create your own plugin.

    Thread Starter llocally

    (@llocally)

    Thank you for your very helpful comments (I was aware that JetPAck works with Askimet – my post wasn’t so clear)

    I was unaware of development mode, thats a very useful bit of information.

    I guess if I extract 2.4 contact form it probably will still have the do_shortcode bug. Maybe I should insert the 2.3 Grunsion into JetPack as a temporary solution, now there is an idea!

    I have added myself to the cc on the trac.

    Once again thank you for your response and help. I’ll merk this thread as resolved.

    Plugin Contributor Ian Dunn

    (@iandunn)

    There’s a patch for this now at https://github.com/Automattic/jetpack/issues/102

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    The problem was fixed in this commit. We’ll include the fix in the next Jetpack release.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘JetPack contact form not working in do_shortcode’ is closed to new replies.