Problem/Motivation

I recently ran into a problem where this module was throwing errors because a view had legacy config for this module, before the changes introduced in #3350578: Cannot use with a Search API Index view.

Proposed resolution

This module should provide two remedies:
1. An update hook to ensure configuration matches the new structure
2. Provide a graceful fallback if $this->options['bundle'] is a string instead of a bundle. This is accessed many places in the code, so using a helper function seems advisable, and will allow for more efficient updates over time

Issue fork add_content_by_bundle-3605225

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

mandclu created an issue. See original summary.

mandclu opened merge request !17

  • mandclu committed a319dd72 on 2.0.x 
    fix: #3605225 Problem with legacy config

By: mandclu
mandclu’s picture

mandclu commented
Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.