Problem/Motivation
After enabling the module, I get the error
Route "entity.feeds_feed_type.add_form" does not exist.
Steps to reproduce
- composer require drupal/feeds
- enabling Feeds module via drush or in the admin interface
Proposed resolution
My guess is that the route doesn't exist yet, because the entity is not created at this point.
Because I'm not the maintainer of the module, I don't know if the link in the message is needed or no, so I'll make a patch that includes the relative path instead of the route. Probably not the best solution, but it worked for me as a temporary workaround.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | missing_route-3263626-2.patch | 716 bytes | joco_sp |
Issue fork feeds-3263626
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
Comment #2
joco_sp commentedThe patch
Comment #3
joco_sp commentedComment #4
irinaz commentedI cannot reproduce this bug.
I installed Drupal using DrupalPod from this issue page, which means that module feeds was installed by DrupalPod. I enabled Feeds module via webUI and I was able to add new feed type. I did not see any errors and did not see any messages in report log.
Comment #5
andreyjan commentedI can reproduce this issue both when enabling manually and through config import. version 3.0.0-beta1
Comment #6
megachriz@andreyjan
Can you reproduce the issue on a clean install too? Did you enable multiple modules at the same time or only the Feeds module? If you did enable multiple, which ones did you enable too?
Comment #7
themodularlabI encountered this error via an azure pipeline which is testing a clean install of Drupal, etc. The patch on #2 fixed the issue for me. I'm on Drupal 9.4.5 and using the 3.0.0-beta2 release of Feeds.
Not sure if this is somehow edge case and/or if this patch should be included in a future release, but in the meantime, it does solve the issue. Thanks @joco_sp
Comment #9
megachrizClosed #3310241: Installing module fails on first run as a duplicate. It seems more people are facing this issue.
The patch does look harmless. The only theoretically downside I can think of is if an other module would alter the path for the route.
Anyway, committed it. A broken link in an unlikely edge case is better than having an error on install in some cases.