Image Block conflict when using Jetpack and Unsplash

[postphotos]

Bug Description

Both Unsplash and Jetpack override the default Image Block experience.

Here's what Jetpack's integration looks like:

And Unsplash's:

We need to make sure these play nicely together.

Expected Behaviour

Steps to reproduce

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Screenshots

Additional context

• WordPress version:
• Plugin version:
• Gutenberg plugin version (if applicable):
• PHP version:
• OS:
• Browser: [e.g. chrome, safari]
• Device: [e.g. iPhone6]

---

Do not alter or remove anything below. The following sections will be managed by moderators only.

Acceptance criteria

Implementation brief

QA testing instructions

Demo

Changelog entry

[derekherman]

@postphotos Did you test that they don't work together?

[postphotos]

Correct @derekherman - this is screenshots from a test site.

Something about the way we're interacting with the image block is overriding the Media Library to show a menu (with Pexels and Google Photos.) When Jetpack is activated, it should continue to show their integration. Deactivating Unsplash restores this.

I think it's probably a bug with Jetpack and not Unsplash... but filing here for someone to investigate.

[ravichdev]

This a tricky one because of the way plugins can filter the MediaUpload component. Due to an earlier featured image issue with AMP/Unsplash plugin we bumped the priority of our filter to 20, Jetpack plugin is using the same filter to add the Button dropdown but with a lower priority of 11 and we end up overriding their changes. I've pushed up a fix and opened a PR for now. Will also open an issue in the Jetpack repo to increase their priority to something like 100

[ravichdev]

Issue #16668 opened in the Jetpack repo to increase the priority. cc @postphotos