Search Exclude crashes Jetpack plugin

It’s possible that other plugins from you will have same issues. Can you please review those as well.

Regards.

Hi – this happened to me so I’ve deactivated Search Exclude and joining this thread to be notified when the issue is resolved

Yes, I’ve seen the same thing – blank Jetpack Settings page. When Search Exclude is enabled it also causes messages such as this at the top of pages in Edit mode:

The “jetpack-publicize” plugin has encountered an error and cannot be rendered.

I had the same things as @nirvanagold

@alisonn I don’t know if you use any SEO plugin, but I’ve just been configuring The SEO Framework. It produces config options at the bottom of each page (in edit mode) and among these is the option to exclude the page from site search results. This seems to be working fine, so I’ve uninstalled Search Exclude. (With The SEO Framework you can tweak titles and descriptions, exclude pages from search engines, and also redirect pages, so I’ve been able to deactivate the Redirection plugin too.)

@nirvanagold Thanks very much – I use Redirection as well. I’ll look into that.

I am aware of at least 12 sites where we had to request the admins to deactivate Search Exclude because of this issue. Can we please have an update on this?

This was something that had come up with another plugin by QuadLayers a couple of years ago. We had discussed it in this thread.

@quadlayers Is this something you could review for your different plugins, and see if you could switch to using Jetpack’s Autoloader package alongside the latest version of each package. I believe it would solve some of the problems we’re discussing here.

Thank you!

Hello @jeherve

Thank you for reaching out.

We’ve received some user reports regarding these issues and have updated all our plugins and dependencies accordingly. All reported issues were addressed and resolved with the latest updates.

Could you please let us know the specific plugin versions causing conflicts?

Our plugins rely on the classmap Composer autoloader. Changing the autoloader method poses a significant risk, as it could result in breaking changes and impact functionality.

Best regards,

Could you please let us know the specific plugin versions causing conflicts?

I’ll let @alisonn and @nirvanagold confirm since they commented above, but I would expect this to happen with the latest version of the Search Exclude plugin, as well as the latest version of the WP Menu Icons plugin as outlined in this thread.

In short, there are 2 ways to fix the issue, both outlined in this thread:

1. Update the automattic/jetpack-assets package to the latest version in all of your plugins.
2. Switch to using the Jetpack Autoloader in all your plugins relying on Jetpack packages to avoid any such issues in the future.

Our plugins rely on the classmap Composer autoloader. Changing the autoloader method poses a significant risk, as it could result in breaking changes and impact functionality.

If you run into breakage when switching to the Jetpack Autoloader package, do not hesitate to reach out in the Jetpack GitHub repository to let us know about the problems. We’ll see how we can help!

Could you please let us know the specific plugin versions causing conflicts?

I first reported the issue on 12 November, so the current version then

Thank you for releasing an update to fix the issue in production.

However, continuing with your current approach of loading the assets package directly via the composer autoloader will soon create the same problem. Moving forward, that jetpack-assets package will be updated and developed regularly, and we will end up dealing with the same issues again, making all of the QuadLayers plugins technically incompatible with Jetpack.

Thus, we request you to please use the?recommended method?of using the package. FYI, jetpack-autoloader is a drop-in replacement for the composer autoloader. So, there shouldn’t be any issues. If you still face any problems, feel free to reach out as mentioned by my colleague @jeherve.

If there is a public repo where we can help implement it, we will be glad to do so.

Hi @manzoorwanijk and @jeherve,

We’re beginning to explore the implementation of the Jetpack Autoloader. Do you have any documentation or tips you’d recommend to get us started?

Do you have any documentation or tips you’d recommend to get us started?

You can see the usage here.