Drupla 11 compatibility

I filed two PRs for Drupal 11 support:

• PR !4: Minimum fixes necessary for Drupal 11 support
• https://git.drupalcode.org/project/content_browser/-/merge_requests/5: Fixes all deprecation notices to prepare for Drupal 12 support, but requires dropping support for versions below Drupal 10.3

I'd suggest using the second PR but a new branch should be created to drop the 8.x- prefix. For people just wanting to get onto Drupal 11, either version should work.

Any news?

This module has one maintainer; we should probably contact them to see if they plan to work on it.

I have some doubts about a positive answer; the last commit was in 2022.

If so, a new maintainer would need to be found.

I have applied the MR !4 But it does not work for me.

I have used : drupal 11 PHP version: 8.4

Not able to install module.

We sent him an email, let's wait

The current maintainer is not working with Drupal anymore, so it is possible that we will not get any response.

We uninstalled the module and replaced the configuration.

Steps to it:

• Create a new content display with the same configuration as content_browser display, we called it entity_browser.
• On views, replace content browser field, by a render field using the new entity_browser display.
• Replace any custom styling or twig from content_browser to entity_browser, example node--content-browser.html.twig => node--entity-browser.html.twig
• Once it is replaced, uninstall the module and check if any configuration needs to be recovered (it should not, as we removed all dependencies of content_browser from views and node display)

When the module is uninstalled it will remove the views with the content_browser field, and the entity_browsers with those views, so it is important to replace the field before uninstall it, also it will remove the content_browser display, that's why we created a new one with the same config.

@eduardo morales alberti @quicksketch, @fabsgugu maybe you'd like to take over maintainership?

Hi,

We already removed the module content_browser and replaced it with custom configuration based on the module on our projects, so we do not need to maintain it. Explanation on comment: https://www.drupal.org/project/content_browser/issues/3503979#comment-16... 📌 Drupla 11 compatibility Needs work

As a recommendation, it can be added a documentation to remove the dependency from the module and mark it as abandoned to be able to uninstall it without losing the functionality.

Or instead, if we want to keep the module maintained, use some kind of recipe to install the configuration to avoid the direct dependency.
The problem with the second option is that there is CSS and JavaScript.