- Issue created by @rraney
In seeking support at those places I recommend gathering this information:
- Details of the hosting platform. Is the platform set up—even certified—for hosting Drupal?
- Verbose output and stack traces.
- The definition of the "Post-Rollout" program and the expected system state and environment where it executes.
- What, very specifically, did you change about Views that precipitated the problem?
- 🇺🇸United States rraney
OK thanks. The platform is Amazee.io. I don't know about its certification but they are reputable.
I will attach a full log of the deployment. Each spin-up container for staging uses a copy of the production database and git branches for code/config.
Post-Rollout is a set of actions that are configured in the lagoon YML file after:
- All images have been successfully built.
- All containers are updated with the new images.
- All containers are running have passed their readiness checks.
There were some Views that were created probably 10 years ago which have since been migrated multiple times into several versions of Drupal, including 7, 8/9, 10. They were created when RSS feeds were more of a thing. I've been seeing a lot of messages about the feed aggregator module being deprecated. I'm trying to get rid of anything related to it, even though it's been out of our system for a good while now. This includes some feed Views, which I basically just removed in local, then pushed out to a dev branch, then to production. There were no issues when pushing these out last week.
I thought maybe webform was being ignored by Config Ignore, but that's not the case.
- Status changed to Closed: works as designed
3 months ago 8:40pm 9 September 2024 - Status changed to Active
about 1 month ago 4:51pm 13 November 2024 - 🇬🇧United Kingdom rajeevk London
Hi @rraney,
Were you able to find the issue behind it?
We are facing this same issue on one of the machines with a fresh project setup with DDEV. However, the same code works on 6-7 different systems. Same DB, code, and config, but drush command throws error
Route "webform.addons" does not exist.
Thanks When running drush cr in my DDEV environment, I get the error: Route "webform.addons" does not exist (RouteProvider.php line 208). Attempts to enable or list the Webform module also fail. I've tried reinstalling dependencies, clearing Drush cache, and confirming the Webform module is in modules/contrib, but the issue persists. Any guidance on resolving this would be appreciated.
- 🇨🇴Colombia carma03
Confirming the error happened on a fresh webfrom installation on D10.3.10 and PHP 8.3.
The solution on my end was to clear the cache through the Drupal UI instead ofdrush cr
command.
Drush version 13.1.1.0.Hope it helps you @anurag_2711 → .