Problem/Motivation

Place the block into a region. After that, you'll see many errors about "Warning: Undefined array key tags" e.c.

Steps to reproduce

Place the block into a region and save.

Proposed resolution

Add defensive coding to prevent "Undefined array key".

Remaining tasks

Resolve all warnings.

User interface changes

None.

API changes

None.

Data model changes

None.

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:

Comments

just-me created an issue. See original summary.

just-me’s picture

Status: Active » Reviewed & tested by the community

Hello,

I've resolved all warnings.
It was tested on Drupal 11 and 10.

I have only one issue with the PHPStan for a new Drupal version. The issue is that in Drupal 13, the function `node_type_get_names()` would be removed, which is used actively in the project.
But the `node_type_get_names()` should be fine for 10-12 Drupal.

just-me’s picture

Issue summary: View changes

just-me’s picture

Assigned: just-me » Unassigned
Status: Reviewed & tested by the community » Needs review
konot’s picture

Status: Needs review » Reviewed & tested by the community

I have reviewed changes and tested them. Everything looks good.

I think it is ready to be merged. Thanks for coping with that!

  • loon committed ab9e1881 on 8.x-1.x authored by just-me
    Issue #3560306: Resolved all warning errors in the CustomSearchBlock.php...
loon’s picture

Status: Reviewed & tested by the community » Fixed

Merged. Thanks all

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.