Interested to join this, I am into back-end and front-end and open to development and no development tasks. looking forward contribute and request to count me in..
Thank You
dan2k3k4 → credited tdnshah → .
tdnshah → created an issue.
@cafuego Can we closed this issue if it has been committed ?
tdnshah → created an issue.
Closing this issue as the error resolved upon upgrading the acquia_cms_search module to 1.5.2
dan2k3k4 → credited tdnshah → .
Read The RFC +1 from me too for idea and formation of working group.
I have few suggestion over handling the case where if the maintainers do not respond even after trying to reach out by the working group member, can we mark such releases as updated by community or something similar.
Thank you
This change is not required work perfectly fine with this change as well, just while running the update command add a composer flag to update with dependency `composer update drupal/focal_point -W`.
Closing this issue.
tdnshah → created an issue.
Reviewed this and the implementation is not working and needs some more understanding on to to implement this hence rerolling the last update to version 1.
@sandipta I would be fine test locally if the implementation is working before update the patch or asking for review, as the implementation is also not considering all the steps mentioned the attached article link, also try to create a new issue fork and raise the PR so that anyone using the working patch via git link do not get impacted.
Thanks
The patches are not resolving the issue when upgraded to D10, In D10 i am getting the below error
ArgumentCountError: Too few arguments to function Drupal\image\Plugin\Field\FieldFormatter\ImageUrlFormatter::__construct(), 9 passed in /var/www/html/docroot/modules/contrib/svg_image/src/Plugin/Field/FieldFormatter/SvgImageUrlFormatter.php on line 41 and exactly 10 expected in Drupal\image\Plugin\Field\FieldFormatter\ImageUrlFormatter->__construct() (line 74 of core/modules/image/src/Plugin/Field/FieldFormatter/ImageUrlFormatter.php).
I would love to add the basic documentation and required step to get it running but currently I am struggling with getting this to work and hence was hunting for documentation :) can any one help with the same.
I have created a search view, added an exposed filter on the field search fulltext, but then I search with any keyword no results are generated; but I can see multiple json files getting generated so seems I was able to properly configure search api and doing something wrong with views.
Thanks
Patch in #25 works for me as well.
#22 works for me well hence moving to RTBC..
Thank you @weekbeforenext for the grt work with the patch.
tdnshah → created an issue.
Hi All,
Still struggling to resolve this, requesting direction towards the resolution or even a work around would help for now ?
Thanks in advance..
@ressa, here onwards Ill add images to the upcoming feeds have made a note of it and have updated the code on our-side.
I was getting alot of warning after upgrading my dev environment to php 8.1 with Drupal 9.5.8, adding the patch in #25 did fix the warnings.
Warnings were as shown in the attached screenshot https://imgur.com/a/UfvpwBs.
As its working fine marking this as RTBC.
Thank you
JoiGarrett → credited tdnshah → .
JoiGarrett → credited tdnshah → .
JoiGarrett → credited tdnshah → .
I was facing the issue with API rate limit as mentioned in #13 and running the drush command drush eval '\Drupal::service("cloudflare.state")->incrementApiRateCount();' as shared by @charginghawk did reset the API rate Thank you @charginghawk for sharing the same.
@SteffenR as mention that this things are covered and fixed in 2.0.x-dev release branch does it also resolved the issue for API Rate limit or should we create another issue for the same and create patch against 2.0.x-dev branch?
Thank you
The patch in #33 is also not helping to solve the drush si issue.
@zakariabdc I tired adding the composer dependency to the project as mentioned by you, and that does not fix the issue on drush si .
yeah I agree with @DamienMcKenna on adding the module as a composer dependency, it do not make any difference.
@DamienMcKenna I tried changing the priority of the metatag_views in mycore.extension file, but no even that do not help.
I feel this has something to do with plugin dependencies not getting calculated properly and hence the metatag_views module is not getting added, not 100% sure on this though.
Tested the above patch, its not resolving this Issue.
The steps to reproduce are as below:
Step 1. Create a normal Drupal Install
Step 2. Add and enable metatag module
Step 3. Add and enable metatag_views module
Step 4. Ensure under admin/structure/views/settings/advanced metatag_display_extender
Step 5. Run drush cex and export all the configs.
Step 6. Then try re running drush si and this should cause the error.
@DamienMcKenna tried adding the dependency to the view definition that uses the metatag_views but even this didnt work, secondly I obsered that it fails when scheduler module is getting installed, and hence little confused how and why installation of scheduler module is is looking for
The "metatag_display_extender" plugin does not exist. Valid plugin IDs for
Drupal\views\Plugin\ViewsPluginManager are: default plugin and causing this to fail.
Looking for directions to debug this further and how this can be resolved ? Any help?
I am facing the above this issue when using blt and running a blt setup command, while blt tries to reinstall the site from scratch and importing the existing config I get the same error as below:
The "metatag_display_extender" plugin does not exist. Valid plugin IDs for
Drupal\views\Plugin\ViewsPluginManager are: default
I tried adding the dependencies of metatag_views module in views.settings.ymlfile as, mentioned in #21 but it didnt resolve the issue for me.
Marking this as RBTC for maintainers to check if the update made to the readme is worth adding else this issue can be closed.
So this issue is not a bug or issue, actually there is a config setting at `/admin/structure/views/settings/advanced` under the Display extenders a config named metatag display extender is enabled and this should start showing the metatag settings in the views edit page.
I have updated the Readme.md file with a note about this edge case as its not mentioned anywhere and i couldn't find any resource explaining this step or config, so if you feel it will be helpful then we can update the readme.
Thank you
@damienMcKenna yes I clear cached alot of times, but still its not coming, secondly I also see an option to add language in my views edit page strange
@apaderno Thanks aot for adding the feed and all of your prompt response by you all.
Also thanks for pointing the typo we have fixed it. :)
@BramDriesen thank you for reviewing the feeds and also for liking the images teasers. :)
The feed link passes the validation
- More as 2 posts. (ok)
- Latest one dates from April 09 2023. (ok)
- Text is trimmed/proper summary (ok)
- Images are not relative (ok)
This got created twice sorry for the garbage, marking this as a duplicate of https://www.drupal.org/project/component/issues/3353700 🐛 Missing Use statement \Drupal\Component\Plugin\Derivative\DeriverBase give fatal error Fixed . PR with the fix is raised against https://www.drupal.org/project/component/issues/3353700 🐛 Missing Use statement \Drupal\Component\Plugin\Derivative\DeriverBase give fatal error Fixed
tdnshah → created an issue.
tdnshah → created an issue.