Karen Attfield

Hi there,

Adding the pattern attribute looks like it would be a good enhancement to the field-url field! I’ve submitted an enhancement request with this suggestion: https://github.com/Automattic/jetpack/issues/42205

However, you may also have some options available to you if you are comfortable experimenting with some code snippets on your site. I’d recommend a functionality plugin such as what we suggest here:

https://jetpack.com/support/adding-code-snippets/

While we don’t officially provide customization support, if you have some experience of hooking into filters you may have some level of success by hooking into the grunion_contact_form_field_html filter to modify the HTML, specifically the pattern value:

https://developer.jetpack.com/hooks/grunion_contact_form_field_html/

I have come up with a fairly rudimentary example you may be able to experiment with. Bear in mind with this though that the pattern used at our end could change rendering this non-functional. Also, the validation is also only on the front-end here (there is further validation done after the form is submitted, but presuming the inputted URL would otherwise normally pass standard URL validation that should be fine), and assumes the field label is ‘Website’:

add_filter( 'grunion_contact_form_field_html', function( $rendered_field, $field_label, $id ) {
    if ( $field_label === 'Website' ) {
        $rendered_field = str_replace(
            'pattern="(?:(?:[Hh][Tt][Tt][Pp][Ss]?|[Ff][Tt][Pp]):\/\/)?(?:\S+(?::\S*)?@|\d{1,3}(?:\.\d{1,3}){3}|(?:(?:[a-zA-Z\d\u00a1-\uffff]+-?)*[a-zA-Z\d\u00a1-\uffff]+)(?:\.(?:[a-zA-Z\d\u00a1-\uffff]+-?)*[a-zA-Z\d\u00a1-\uffff]+)*(?:\.[a-zA-Z\u00a1-\uffff]{2,6}))(?::\d+)?(?:[^\s]*)?"',
            'pattern="https:\/\/example.com\/.*?"',
            $rendered_field
        );
    }
    return $rendered_field;
}, 10, 3 );

As we don’t generally provide customization support though (our scope of support for reference: https://jetpack.com/support/scope-of-support/), we wouldn’t be able to continue debugging that specific snippet if there are any issues, but hopefully it allows you to experiment with different changes to your form.

As for other attributes, the approach could be similar, but depending on the attribute it may also be something we can request be added within Jetpack itself. If there is anything in particular you would like to see added to any of the Jetpack contact form fields, do let us know.

Hi there,

Those span-sync calls will be coming from Jetpack Sync. For example, when a post is created or updated Jetpack Sync will send this action to WordPress.com so that the information we have on our servers will be aligned with what is on your site.

Looking at the sync activity for the site mentioned in the logs you’ve shared, I do see that virtually all recent sync activity is related to one action, which is update_option calls specifically for the active_plugins options.

Are you aware of any processes running on your site that would result in a high level of activity, specifically related to the list of active plugins on your site?

Other options do include completely disabling Jetpack Sync on your site, though that would mean that functionality that relies on sync would not work, for example Search, Related Posts and more. There is more information on what Sync does here:

• https://jetpack.com/support/what-data-does-jetpack-sync/

If we can determine what activity might be resulting in those calls though, that might not be needed. Do let us know if you have any more information about possible activity on the site that could result on those update_option calls.

Hi @lestado,

We’d love to investigate this further – could you provide some more context about when this issue happens? If I create a new contact and manually edit the name, the newly edited name change saves properly and I can see it showing correctly on the Contacts -> View All page.

If you are editing the contact name via the CRM Contact Edit page, in which locations is the name showing up incorrectly?

Hi @jodzeee

Thanks for sharing your URL, and the screenshot there. That second connection option is there because it is possible to have your site connected to Jetpack, but with a site-only connection. If you connect your WordPress.com account, more Jetpack features are available (features that require user authentication).

In terms of the Jetpack connection on your site, unfortunately it isn’t possible to get notifications when Jetpack is disconnected on your site though this is a feature that may be considered in the future. I do notice that there are quite a lot of active plugins on the site (visible via the Jetpack connection itself), so it is possible that another plugin could be interfering with the connection at times (more likely a security plugin in that case), as Mehdi mentioned. But the best bet here would be to reach out to your host to ask for server error logs from around the times that you notice Jetpack is disconnected. If there is something happening at a hosting level, the logs may pick that up.

Do let us know what you find here and we’ll be happy to troubleshoot further if possible as well.

Hi @ions2020

We’re still seeing those ‘403 forbidden’ error messages from our end, when Jetpack attempts to communicate with the xmlrpc.php file on your site.

From our end we’re unable to see if there is a particular IP address experiencing issues, however what may help here is finding out if there are any other security measures in place at the hosting end (not necessarily specific to Jetpack but just general security features). Do let us know if your host has any information about this.