Contact Form: avoid conflicts when using the old version of the Contact Form feature

This is a follow-up to #33050.

Right now, the contact form feature is loaded from the Contact Form package by default:
https://github.com/Automattic/jetpack/blob/0173104f84c1c325fdfeeef6afc664a3baea9390/projects/plugins/jetpack/modules/contact-form.php#L23-L36

Some site owners may decide to continue to load the contact form feature from the old codebase instead:

```php
add_filter( 'jetpack_contact_form_use_package', '__return_false' );
```

When you do so, you run into issues with how the blocks are registered, as discussed in  p1696362451002639-slack-CDD9LQRSN

Related Epic: #32401 

**********

Related Epic: the old form code will eventually be removed in #30551

	/**
	* Whether to load the newer Jetpack Forms package.
	*
	* @use add_filter( 'jetpack_contact_form_use_package', '__return_true' );
	* @module contact-form
	*
	* @since 11.8
	*
	* @param bool $load_contact_form_package Load Jetpack Forms package. Default to false.
	*/
	if ( apply_filters( 'jetpack_contact_form_use_package', true ) ) {
	Jetpack_Forms::load_contact_form();
	return true; // Not returning true will cause the module to become deactivated.
	}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Contact Form: avoid conflicts when using the old version of the Contact Form feature #33464

jeherve
openedon Oct 4, 2023

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Contact Form: avoid conflicts when using the old version of the Contact Form feature #33464

Description

jeherveopenedon Oct 4, 2023

Metadata