Jetpack 5.6.1: Contact Form Security Update and Other Improvements

Jetpack 5.6.1 is now available for download and includes some important security updates, bug fixes, and improvements. We recommend that you update your sites to the latest version as soon as possible, particularly if you use the Contact Form feature frequently or on several pages.

These are the three major changes you’ll find in this point release:

  • Extra security has been added to the Contact Form to improve permissions checking when updating a contact form’s settings.
  • We’ve extended the limit on character count to 280 for the Publicize feature when posting to Twitter.
  • Finally, we fixed a bug that disabled “saving” widgets when removing a Widget Visibility rule.

Those are just a few of the updates and bugfixes in this release. If you’re curious, you can find the full changelog here.

A big thank you to everyone who contributed to 5.6.1: Marin Atanasov, Matthew Denton, Rinat K, and George Stephanis.

This entry was posted in Releases and tagged . Bookmark the permalink.

Explore the benefits of Jetpack plans

Compare plans in detail to see how Jetpack can help you design, market, and secure your WordPress site.

Compare plans

Have a question about this article?

Comments are currently closed for this article, but rest assured we're still here to help! Send us a message and we'll get back to you.

Contact us

Comments

  1. craigkeefner says:

    What is the best way to beat spam with the contact form?

    Liked by 1 person

  2. Ajay0777 says:

    Would you please tell me what is jetpack 5. 6.1

    Liked by 1 person

  3. wonky1 says:

    ” you can find the full changelog here”
    No you can’t!

    https://wordpress.org/plugins/jetpack/changelog
    –>
    https://wordpress.org/plugins/jetpack/#changelog
    –>
    no anchor
    (also no changelog anywhere)

    But within WP(.org anyways) admin:
    http://medlem.nobe.ch/wp-admin/plugin-install.php?tab=plugin-information&plugin=jetpack&section=changelog
    Does show the changelog.
    Well not 4.6.1 but at least 4.6(.0).

    Liked by 3 people

    • Adam says:

      The link in the post goes to this URL:

      https://wordpress.org/plugins/jetpack/#developers

      … which shows the changelog for me when I scroll down. Does that not work for you?

      Liked by 2 people

      • wonky1 says:

        The link has been changed. It would have been courteous of OP to comment on that.

        Also, there used to be a section “Changelog” on every plugin page. “Changelog” is self-explanatory, and very informative. (Is it considered too “old-school” now?) I’m very happy that it is still available through the WP dashboard.

        The website developers tab is now named “Development” and consists of 99% changelog, plus a few lines. I also note that the website description now is named “Details”. And again I’m happy that it has kept its descriptive (sic!) name “Description” within the dashboard.

        Isn’t everything “details”, including the devil?

        Liked by 2 people

      • Osk says:

        Hi, OP here. I’ve just seen this message. I changed the link because it was wrong, not because I read this comment. So it’s not like the update lacked courtesy. I’m sorry if there was any inconvenience here.

        Liked by 1 person

      • Adam says:

        We don’t really have any control over the design of the WordPress.org plugin repository pages. That is handled by the Meta Team over at WordPress.org. More information here:

        https://make.wordpress.org/meta/tag/plugin-directory/

        Liked by 2 people

      • wonky1 says:

        @Adam (@Osk below)
        Thanks for the info about the difference between .org and .com, and actually I was aware of there being some kind of difference – but …
        I came here because even in the .org, or rather in my (non-.com) dashboard, the link to the “Plugin Homepage” is the .com one.
        Would you have, then, a changelog (.com) link? I always end up at .org.
        (I’ll be sure to get my grievances to the .org, eh … organization (sic! again), but I find it slightly bewildering, this compartmentalization.)

        @Osk
        It shouldn’t matter if someone spots an error – AND posts about it. Or not. Many could have read and clicked, right? In this case certainly so.
        If you perhaps would implement an “updated”/”changed” date/time for your blog? I think that might be enough (to avoid any need for self-flagellation, if you think an excuse/note of change is that – yes, I think your avoidance is less than good, not offensively so, to be clear).

        Liked by 2 people

  4. Hello – do we need to reinstall Jetpack for this update to take place? In the Installed Plugins page it does say it’s the 5.6.1 version, however, the Jetpack Dashboard still says it’s the 4.9.1 version at the bottom of the page. Thanks!

    Liked by 1 person

  • Enter your email address to follow this blog and receive news and updates from Jetpack!

    Join 103,749 other followers

  • Our most popular posts

  • Browse by topic

  • %d bloggers like this: