I can confirm that in 3.0.0-beta3 the modules work together as expected.
After looking through all of the facet options, it turns out that all you have to do is uncheck the "Hide facet when facet source is not rendered" option.
damienmckenna → created an issue.
damienmckenna → created an issue.
The current documentation file (in the _documentation directory) is also out of date and needs to be updated.
What you need to do is:
* Open the "Processors" settings page of the index you want to add the glossary to.
* Enable the "Glossary processor" processor.
* In the "Processor settings" section, open the "Glossary processor" tab and enable the field you want to use for the glossary.
* Save the index.
* Add a facet to the view or Search API Page that points to the "Glossary AZ" field that corresponds to the field above.
* Set the facet to use "Glossary AZ" widget.
* Work through all of the options that include "Glossary" in their name, enable the ones that you want.
* Save the facet.
* In the block layout settings, use the "Place block" option to open the block selection, and add the glossary facet you created above; adjust the block visibility settings as necessary.
I was fumbling in the dark a bit, but this seems to work.
Ran into this today, the workaround was to disable the drag UI and just edit the weights manually.
Marking the existing work as RTBC as it works really well.
While testing the latest MR it gave an error that dynamic properties was deprecated, so adding the $adminCache property resolves the error.
I would suggest creating a follow-on issue to rework some of the logic to properly use DI for \Drupal::cache(), and some of the other things that are loaded via services.
damienmckenna → made their first commit to this issue’s fork.
damienmckenna → created an issue.
damienmckenna → created an issue.
damienmckenna → created an issue.
damienmckenna → created an issue. See original summary → .
Please don't mark something RTBC if you haven't checked the test pipeline, because unfortunately these changes broke a lot of tests. Also, it seems to have added a cspell issue.
Please try naming the field something different, e.g. "meta_tags", see if that works. If it ends up being a compatibility issue we can add a note to the docs and via hook_requirements().
How did you create the field without the typical "field_" prefix? I wonder if there's a collision happening somehow?
This has been completed in the D11 issue.
Thank you for creating this issue.
Test coverage to confirm the backup works is 100% the way to go.
I'm sorry the module hasn't been working for you. Please help us make it better by testing the current dev release and reporting issues that show up. Thank you.
Going to give it a few days for people to test before I tag this release, just to make sure there aren't any regressions.
Going to give it a few days for people to test before I tag this release, just to make sure there aren't any regressions.
Committed.
damienmckenna → changed the visibility of the branch 8.x-1.x to hidden.
Committed.
Committed. Thanks everyone!
This is what I'm going with.
Committed! Thanks everyone!
Committed. Thanks.
There's a regression in the tests against D11, that needs to be fixed then it'll be ready to go.
Committed. Thank you!
Meta tags that allow multiple values will automatically have a note added to their description.
Committed. Thank you!
damienmckenna → created an issue.
Committed. Thank you!
Committed.
Committed.
Fixed.
damienmckenna → created an issue.
damienmckenna → created an issue.
Committed.
damienmckenna → created an issue.
Committed. Thank you everyone for digging through this.
Ok.. so at some point today the default build changed from 10.3 to 11.0. I'll do a separate issue to update the tests to also test 10.3, but otherwise this is ready to go.
The v2 upgrades fail because the d9 fixtures file was removed. That makes sense.
I've changed it so that phpcs tests can fail, will deal with that later: 📌 Resolve phpcs issues in 2.0.x / 2.1.x Active
damienmckenna → created an issue.
The providerSource() change means we can't have the tests run against 10.2 anymore, though the rest of the codebase should be compatible. I guess that will have to be a limitation we deal with, and we'll have to disable OPT_IN_TEST_PREVIOUS_MINOR.
Should there be a change notice for this? Or maybe an 11.1 tag?
Thanks for the patch, this resolved the problem for me.
It might be worth turning this into a merge request.
Ran into this one again.
#26 results in this error when loading core/install.php:
TypeError: Symfony\Component\DependencyInjection\Container::set(): Argument #2 ($service) must be of type ?object, string given, called in /var/www/html/docroot/core/lib/Drupal/Core/DependencyInjection/ContainerBuilder.php on line 47 in Symfony\Component\DependencyInjection\Container->set() (line 146 of /var/www/html/vendor/symfony/dependency-injection/Container.php).
Rerolled for 10.2.x.
Can you please confirm the version of Metatag that is being used, which Metatag submodules are being used, and whether you're also using Schema.org Metatag and its submodules?
joelpittet → credited damienmckenna → .
I think it should be a module.links.task.yml item.
Thanks for asking. The last issue is 📌 Fix tests in 8.x-2.x branch Active .
Committed, will deal with the faulty tests in 📌 Fix tests in 8.x-2.x branch Active .
damienmckenna → created an issue.
Waiting for the test run to finish.
I'm going to throw this together.
Thanks everyone!
damienmckenna → created an issue.
That is good to know, thank you koosvdkolk!
I opened a separate issue so we can document using HTML Purifier: 📌 Document how to use HTML Purifier instead of core filters Active
damienmckenna → created an issue.
There's also seckit → which also can set the CSP headers.