Problem/Motivation

Getting this notice after we upgraded to alpha2

Steps to reproduce

Tricky one because the upgrade was also an upgrade from D9 to D10, with for instance an update from ckeditor4 to ckeditor5. Not sure whether this contributes to this problem. Will try to investigate deeper when I get the chance at which point this is triggered or what the replace is trying to.

Note: i've done the upgrade on my local machine without having the source files for instance ('e.g. uploaded images or files) on my local system, that might be a clue for myself to investigate. In case that triggers the notice, it still might not be a bad idea to fix the notice though.

Proposed resolution

Adding a simple isset() check probably does the trick ?

Remaining tasks

Investigate more, then upload a patch

User interface changes

None

API changes

None

Data model changes

None

Issue fork pathologic-3417156

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

swentel created an issue. See original summary.

swentel’s picture

Issue summary: View changes
swentel’s picture

Issue summary: View changes

Quickly debugging by adding following lines before that check:

  if (!isset($cached_settings['is_file'])) {
    \Drupal::messenger()->addMessage(print_r($parts, TRUE));
  }

And what was checked where simply urls, so no images or files.

e.g.

Array ( [path] => node/312 [is_file] => [qparts] => )

swentel’s picture

Status: Active » Closed (works as designed)

Ok, so for some weird reason, the composer update command did update the info file to alpha2, but not the module file, VERY weird. After removing and requiring again, everything is fine, sorry for the noise!

czigor made their first commit to this issue’s fork.

czigor’s picture

Status: Closed (works as designed) » Active

I get the same warning with composer behaving as it should but with a href="void(0); link to replace.

czigor’s picture

Status: Active » Needs review
abu-zakham’s picture

I get the same warning, and the PR resolved the issue

fabiansierra5191’s picture

Status: Needs review » Reviewed & tested by the community

Looks like the patch fix the warning. thanks!