castor-designs → created an issue.
Hi @AaronMcHale Sorry for seeing this so late. I've checked my views.settings.yml (core file) but there is no line that contains "metatag" in any way: https://pastebin.com/6rqsH9GR
I get this error as soon as I do anything in composer like uninstall a completely different module. How can I workaround this issue breaking my site as soon as I want to do basically anything?
Hete's my scenario: https://imgur.com/a/frC5mEA
Hello everyone. I ran into this very problem when migrating from drupal 9 to drupal 10 and running updates.
Is there a workaround in the meantime to "unbreak" the site or prevent it in the first place?
Thank you so much Norbert! Last thing: What is happening when I get errors when trying to upgrade to the latest version of a now incompatible module? So I am on Drupal 9.5 and I see that Mailchimp is incompatible.
However, I see that my installed version is 2.1.0-rc1.
The current version is 2.2.2.
So I run: composer require 'drupal/mailchimp:^2.2'
By doing that I hope to patch my old Mailchimp to the latest which hopefully is compatible with Drupal 10 and I have one less module in my incompatible list.
However, this now throws me the following error:
Problem 1
- drupal/mailchimp 2.2.0 requires thinkshout/mailchimp-api-php 3.0.0-rc4 -> found thinkshout/mailchimp-api-php[3.0.0-rc4] but it does not match your minimum-stability.
- drupal/mailchimp[2.2.1, ..., 2.2.2] require thinkshout/mailchimp-api-php 3.0.0 -> found thinkshout/mailchimp-api-php[v3.0.0] but it conflicts with your root composer.json require (^2.1).
- Root composer.json requires drupal/mailchimp ^2.2 -> satisfiable by drupal/mailchimp[2.2.0, 2.2.1, 2.2.2].
What is happening here?
Thanks Norbert
Actually I am already running Upgade Status I figured and it gives the following report:
Environment is incompatible: CKEditor (4)
Remove: 2 projects (Custom Theme Modules for Sliders and such)
Update: 4 projects
Collaborate with maintainers: 6 projects (Mailchimp, Ludwig, Simple Image Rotate)
Fix with rector: 3 projects (Custom Theme Modules)
Fix manually: 1 project (Custom Theme Module)
I don't quite unterstand this line: "You have to find the version which worked with D9.5 and put this version number in your composer.json file, one at a time. In case trouble occurs, you have only to deal with one module, not with all the dependencies. "
But I think it's because I don't understand how composer works fully.
So you are saying you don't runn all updates, but you go into the composer file and write the latest module number version module after module to see if it works?
How to apply the change once you change the composer.json file? Do you have to run cron or update.php?
Hi nofue, thank you so much.
Ah don't worry. Of course I backed everything up and I only broke my staging.
The thing is: I am already trying to upgrade to Drupal 10. But in terms of gettign to Drupal 10 I was adviced to upgrade all modules inside Drupal 9 first.
That's why I got this error int he first place.
Hi nofue →
Wow, thank you very much for your reply, your time and effort! Here is more information:
- Functioning Composer File before Updating
- Broken Composer File after Updating
- SSH Console Log of what I did
Any help is much appreciated!
Hi have the exact same problem as OP 4 years later and I am wondering what path I have to put as described here.
My Drupal installation runs inside /home/myname/drupal-installation-folder
So what do I have to put in this json file? thanks in advance.
Hi @marcoka. Thank you so much I missed in last month but will definitely test it! You are awesme.
Hi team. What's the status on this issue? For me Patch from #53 is not working: "Could not apply patch! Skipping. The error was: Cannot apply pat ch https://www.drupal.org/files/issues/2023-01-27/schema_metatag-n2 → 976935-53.patch"
I tried to apply patch from #82 and got this error (while a different patch works flawlessly):
Could not apply patch! Skipping. The error was: Cannot apply patch https://www.drupal.org/files/issues/2023-01-05/metatag-n3067803-82.patch
Second topic: As soon as your sentence e. g. in the answer has a comma in it it pivots as well. So if I use fields to populate this section e. g. like this: [term:field_faq:0],[term:field_faq:1],[term:field_faq:2]
then as soon as a value of this field has a comma in it e. g. "How long have you been studying English, and what motivated you to start?" it will pivot that but it makes no sense of course.
So is there a way to prevent this?
Hi @marcoka I wanted to ask what the status is regarding the issue. I understand that you have a lot on your plate and I did not mean to stress you out :D thanks for your great work regardless!
Patch works for me as well but definitely should be added to the main version of this module!
Castor-designs → created an issue.
Thanks for addressing this. It means a lot to me. It's not clear when it will be phased out. For more information see: https://www.drupal.org/node/3223395#s-ckeditor →
Hi both of you. I found the very same problem. It can't be tested because this setting does not allow the user to save the settings. So there is no way to test whether it works. This will be important as with further versions the old CKE will phase out (already has) and CKE 5 is the new standard and implemented in core.
Hello everyone I am using 2.1@alpha and have the same problem as OP.
I enabled the rotate option for the field and yet there is no such icon showing up on edit forms.
Castor-designs → created an issue.
Thank you very much for all your work! For me the second latest Beta version manually installed works with the librarie shared by you in this thread. We can close this issue.
Thank you very much @marcoka!
I completely uninstalled the module and started again from scratch. I install the library you linked and then the latest Amazon module (Version: 2.1.0-beta12).
However, I still get the following error in the backend and when visiting pages where I use amazon tokens:
The website encountered an unexpected error. Please try again later.
Error: Cannot use object of type Drupal\Core\Render\Markup as array in Drupal\amazon_pa_filter\Plugin\Filter\AmazonFilter->process() (line 293 of modules/amazon_pa/amazon_pa_filter/src/Plugin/Filter/AmazonFilter.php).
Drupal\amazon_pa_filter\Plugin\Filter\AmazonFilter->process() (Line: 118)
Drupal\filter\Element\ProcessedText::preRenderText()
call_user_func_array() (Line: 101)
Drupal\Core\Render\Renderer->doTrustedCallback() (Line: 788)
Drupal\Core\Render\Renderer->doCallback() (Line: 374)
Drupal\Core\Render\Renderer->doRender() (Line: 204)
Drupal\Core\Render\Renderer->render() (Line: 479)
Drupal\Core\Template\TwigExtension->escapeFilter() (Line: 87)
__TwigTemplate_e5b9730da48bbc843781931639e6d952b46abbb193029fcf7a812ad65c0f11ab->doDisplay() (Line: 405)
Twig\Template->displayWithErrorHandling() (Line: 378)
Twig\Template->display() (Line: 390)
Twig\Template->render() (Line: 55)
twig_render_template() (Line: 384)
Drupal\Core\Theme\ThemeManager->render() (Line: 433)
Drupal\Core\Render\Renderer->doRender() (Line: 446)
Drupal\Core\Render\Renderer->doRender() (Line: 204)
Drupal\Core\Render\Renderer->render() (Line: 479)
Drupal\Core\Template\TwigExtension->escapeFilter() (Line: 220)
__TwigTemplate_940aa5ec85d8795e85d016f15a60bea6937dce618d7f236992e93a3ff722fa6d->doDisplay() (Line: 405)
Twig\Template->displayWithErrorHandling() (Line: 378)
Twig\Template->display() (Line: 390)
Twig\Template->render() (Line: 55)
twig_render_template() (Line: 384)
Drupal\Core\Theme\ThemeManager->render() (Line: 433)
Drupal\Core\Render\Renderer->doRender() (Line: 204)
Drupal\Core\Render\Renderer->render() (Line: 242)
Drupal\Core\Render\MainContent\HtmlRenderer->Drupal\Core\Render\MainContent\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 243)
Drupal\Core\Render\MainContent\HtmlRenderer->prepare() (Line: 132)
Drupal\Core\Render\MainContent\HtmlRenderer->renderResponse() (Line: 90)
Drupal\Core\EventSubscriber\MainContentViewSubscriber->onViewRenderArray()
call_user_func() (Line: 142)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch() (Line: 174)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 81)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 58)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass() (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle() (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle() (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle() (Line: 23)
Stack\StackedHttpKernel->handle() (Line: 718)
Drupal\Core\DrupalKernel->handle() (Line: 19)
Thanks marcoka. How do I find it? I install amazon_pa on a drupal 7 installation with composer and try to find the library and copy that over to the druapl 9 installation? I am a bit confused sorry. (In the file downloads the library is not present of course.)
Thanks marcoka
Where do I find the repository dww set up? What I did was:
- Download paapi5-php-sdk-and-samples archive from the amazon.com page
- delete everything but src and vendor folder.
- put it on my webspace under /libraries/amazon_sdk
Castor-designs → created an issue.
Hi both of you. I can replicte this problem. I guess I will install it manually then.
Thanks for your work marcoka!
why should I write the root folder in plain text in the composer.json? The article states: * note:
the `web` represents the folder where drupal lives like: ex. `docroot`.
However, my composer.json declares the root anyway in the form of "locations": {"web-root": "./"}
so I should be able to use ./modules/contrib/webform/composer.libraries.json
by default no?
So it would be correct and less static if the code in the article would just use that instead? Am I missing something?
I can reproduce everything written by the original poster.
@Jaypan what do you mean with restart the webserver? Not all of us have access to restart the webserver. In my case I use a shared hosting where I can't simply restart the server.
Hello @jrockowitz
I ran into the very same poblerm.
- Webform Node is installed and enabled
- I have access to the token and can use it in the subject line
- When i would use an invalid token I get an error message and can't save the settings like this. Therefore it's a valid token.
- it's a basic text field
- it does not get printed/rendered and is simply empty.
See this screenshot series: https://imgur.com/a/yhEiDot
One thing that is special in my setup: Webform (and Webform node) is installed via Composer while Token is installed manually. I had no other problems with tokens so far.