liampower → credited john cook → .
liampower → credited john cook → .
liampower → credited john cook → .
As a side note, I noticed this bug because I have /web as a symlink to /docroot after changing host providers.
I had problems applying the diff / patch using cweagans/composer-patches, with a segment being rejected in components.info.yml. This was due to versioning information added by the packaging script on Drupal.org. I manually added the two line change before testing. I don't see this being a problem once the issue has been merged.
I tested with just the patch to make sure that the duplicates are reported by default. As expected, the errors appeared in the watchdog log.
Then I tried again after adding $settings['components_ignore_duplicate_templates'] = TRUE; to my settings.php. After I cleared the cache and refreshed the same page, the errors are no longer logged.
Moving to RTBC.
I've tested the patch in #58 🐛 Blockmode "Auto" will not work in Drupal 8 with core's domready library Needs work and it works as expected.
I've check the patch and it doesn't appear that @dmsmidt's points in #43 🐛 Blockmode "Auto" will not work in Drupal 8 with core's domready library Needs work have been addressed. This will need to be done before this can proceed further.
I've tested
patch 2
✨
Select/Options formats in views as exposed filter
Needs work
/
MR 3
✨
Select/Options formats in views as exposed filter
Needs work
and the exposed component can be limited as desired. In my case the configuration looks like this:
This produced the filter like this:
I checked that the patch and the MR submitted the same code, which they do.
I also looked at patch 7 ✨ Select/Options formats in views as exposed filter Needs work . This reversed the configurability for the filter, so I would not recommend this patch. Although having the ability to define a dynamic range could be helpful in some cases. Maybe for another issue though.
The MR only add a new filter.
Setting to RTBC for the MR.
john cook → created an issue.
mradcliffe → credited john cook → .
mradcliffe → credited john cook → .
mradcliffe → credited john cook → .
john cook → created an issue.
Hi @gto1.
I think it's a problem with DDEV rather than Drupal CMS. I get the same error with a lot of the sites I run locally.
I find that running ddev start again fixes the issue. Mutagen doesn't take as much time to run the second time.
I know it's annoying, but it's a work-around that gets the site running while the DDEV folks find out what the problem is.
To get around this for now, commit 'f6ec3c8e6286b7fba880ca7a9d52f230e2b4df27' can be used.
```
composer require "drupal/facets:dev-3.0.x#f6ec3c8e6286b7fba880ca7a9d52f230e2b4df27"
```
john cook → created an issue.
john cook → created an issue.
jjchinquist → credited john cook → .