Problem/Motivation

It looks like this module uses hard coded paths because I am using following module rename_admin_paths and it is not possible to load content/taxonomy with this module due to following issue :

it says :
page not found > /admin/entity_reference_tree/json/node/*?token=ah6VuHAc8JmyFSY...

it is possible to configure paths generated by the route as described in rename?

When I disable rename admin path it works fine.

Comments

coaston created an issue. See original summary.

coaston’s picture

Version: 3.x-dev » 2.2.0
mingsong’s picture

Category: Bug report » Support request
Status: Active » Closed (works as designed)

This is not a bug as it works as designed.

I am not familiar with rename admin paths module, but all routes created by Entity Reference Tree Widget module are defined in

https://git.drupalcode.org/project/entity_reference_tree/-/blob/2.2.0/en...

Nothing hardcoded and you should raise your question about your custom path to rename_admin_paths module. There is nothing to do with a custom path here, as this module doesn't provide this functionality.

coaston’s picture

Status: Closed (works as designed) » Active

First of all, thank you for your answer. However you are not right I guess.

Rename admin module has following description :

If another module is no longer functional after this module is enabled this usually means that the other module uses hard coded paths instead of paths generated by the router with a route name. This is not something that can and should by fixed by this module.

The same question was raised for a different module here 3349859 and maitanier was able to provide quick fix, even they are using the same approach with /admin but fix here :wrong-url looks quite easy.

Hence I am asking you to double check and possible do the similiar path here to make this module compatible.

Thank you for your understaning.

mingsong’s picture

Status: Active » Closed (works as designed)
coaston’s picture

Well, looks like you gave up, but still thanks for your time.
Not sure how to explain it more that this needs to be fixed in this module to make it compatible. So far it works with all contributed modules, except this one, so this is also trigger that any config is not right there.

Now I need to decide whenewer to disable this awesome module ,or another admin one, which is also awesome.

However, good work - this module is powerful!

mingsong’s picture

Thanks @coaston, you are right.

It would be better if the URL could reflect any changes to the route.

I will release a new version to deliver this new feature soon.

mingsong’s picture

Category: Support request » Feature request
Status: Closed (works as designed) » Fixed
mingsong’s picture

Status: Fixed » Closed (fixed)

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