Wenn downloading the latest dev release and enabling it with drush en context on a multilingual site, I'll get the following error message:

Error: Call to a member function getPath() on null in /var/www/lakedrops/web/core/modules/config_translation/src/ConfigNamesMapper.php on line 233

This error gets thrown all the time, even if just flushing cache with drush. As soon as I disable the module again the error disappears. I wasn't able to look into that yet but would hope that someone may have an idea what could be causing this.

CommentFileSizeAuthor
#6 context-Resolve_multilingual_exception-2802253-6.patch1.04 KBreplicaobscura

Comments

jurgenhaas created an issue. See original summary.

rutiolma’s picture

rutiolma
Location 🇵🇹
commented
Version: 8.x-0.x-dev » 8.x-1.x-dev
Priority: Normal » Major

Same problem here.

znak’s picture

znak commented
Assigned: Unassigned » znak
replicaobscura’s picture

replicaobscura
she/her
Primary language English
Location West Virginia
commented

Same error here.

I wonder if the issue is that Context's routes are all defined in the context_ui submodule, but config_translation is likely trying to determine one or more of the routes.

Just a hunch based on a similar issue I've seen before--I'm investigating this a bit more now.

replicaobscura’s picture

replicaobscura
she/her
Primary language English
Location West Virginia
commented

In ConfigNamesMapper.php, the getBaseRouteName() method should be getting the base route name for the entity type, and I believe it's unable to without any routes being defined in the base module (unless you have context_ui enabled, but if it's a required module than having it be separate doesn't really make sense, so perhaps moving some of the routes up to the parent module is needed).

replicaobscura’s picture

replicaobscura
she/her
Primary language English
Location West Virginia
commented
Status: Active » Needs review
StatusFileSize
new context-Resolve_multilingual_exception-2802253-6.patch1.04 KB

Here's a patch that seems to fix the issue for me by moving only the entity.context.edit_form route up to the main context module instead of leaving it in context_ui.

Is this the right way to go? If so, should any other routes be promoted to the parent module?

replicaobscura’s picture

replicaobscura
she/her
Primary language English
Location West Virginia
commented

Note that this issue also exists on alpha1, and this patch does seem to resolve the issue on alpha1 as well, if anyone's running into this but worried about updating to a dev version.

utement’s picture

utement commented
Status: Needs review » Reviewed & tested by the community

Patch produces warning:

warning: 1 line adds whitespace errors.

but it does apply correctly. Patcs solves issue.

Ready for commit.

dietr_ch’s picture

dietr_ch commented

+1, patch works.

  • boshtian committed 79051b4 on 8.x-1.x authored by bmcclure 
    Issue #2802253 by bmcclure, utement, dietr_ch: Error on multilingual...
boshtian’s picture

boshtian commented
Status: Reviewed & tested by the community » Fixed
boshtian’s picture

boshtian commented
Status: Fixed » Closed (fixed)