🇦🇹Austria @drupalfan2

The following patch solves the problem.

Feel free to write a better patch.

drupalfan2 → created an issue. See original summary → .

Hello,

I have the same problem on Drupal 11.1.2 with Drupal CMS.

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/webform_booking ^1.1 -> satisfiable by drupal/webform_booking[1.1.0, ..., 1.1.7].
    - drupal/webform_booking[1.1.0, ..., 1.1.7] require drupal/webform_ui * -> satisfiable by drupal/webform_ui[5.0.0, ..., 5.31.0, 6.0.0, ..., 6.2.9].
    - drupal/webform_ui[5.9.0, ..., 5.13.0] require drupal/core ^8.7.7 || ^9 -> found drupal/core[8.7.7, ..., 8.9.20, 9.0.0, ..., 9.5.11] but the package is fixed to 11.1.2 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - drupal/webform_ui[5.0.0, ..., 5.15.0] require drupal/core ^8 -> found drupal/core[8.0.0, ..., 8.9.20] but the package is fixed to 11.1.2 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - drupal/webform_ui[5.16.0, ..., 5.31.0] require drupal/core ^8.8 -> found drupal/core[8.8.0, ..., 8.9.20] but the package is fixed to 11.1.2 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - drupal/webform_ui[6.0.0, ..., 6.1.4] require drupal/core ^8.8 || ^9 -> found drupal/core[8.8.0, ..., 8.9.20, 9.0.0, ..., 9.5.11] but the package is fixed to 11.1.2 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - drupal/webform_ui[6.1.5, ..., 6.1.8] require drupal/core ^9.3 -> found drupal/core[9.3.0, ..., 9.5.11] but the package is fixed to 11.1.2 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - drupal/webform_ui[6.2.0, ..., 6.2.6] require drupal/core ^9.4 || ^10 -> found drupal/core[9.4.0, ..., 9.5.11, 10.0.0, ..., 10.4.2] but the package is fixed to 11.1.2 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - drupal/webform_ui[6.2.4, ..., 6.2.7] require drupal/core ^10.1 -> found drupal/core[10.1.0, ..., 10.4.2] but the package is fixed to 11.1.2 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - drupal/webform_ui[6.2.8, ..., 6.2.9] require drupal/core ^10.2 -> found drupal/core[10.2.0, ..., 10.4.2] but the package is fixed to 11.1.2 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

When trying
composer require drupal/webform_booking

the following version is installed:
drupal/webform_booking (1.0.13)

After that I download v1.1.7 from https://www.drupal.org/project/webform_booking/releases/1.1.7 → manually and it is working without any problems in Drupal CMS 11.1.2.

How can we solve the dependency problem?
Thank you.

I have a simular problem getting the error message:

InvalidArgumentException: "attributes" is an invalid render array key. Value should be an array but got a object. in Drupal\Core\Render\Element::children() (line 97 of core/lib/Drupal/Core/Render/Element.php).

The attached patch #8 solves my problem.

hello claudiu.cristea,

private_message v.3.0.7 is still not working, same problems.

I tested this commit
https://git.drupalcode.org/project/private_message/-/commit/17a48a67fa64...
It is not working!

I testesd v4.0.0-alpha4: works fine.

When will v4.0.0 be realeased?
When we will get a working 3.0.8 version?

Then you very much.

The following patch avoids the infinite while loop.

drupalfan2 → created an issue.

drupalfan2 → created an issue.

@ptmkenny
Thank you for your answer and your info.

In the README file of your firebase_php module I did not find any docs how I can send my Firebase Notifications with custom code in my custom module.
How does it work, where can I find an exmple code etc.?`
Thank you.

I can not install a alpha version on a production site.

You did not answer my question:
You did not use the 3.0.x-dev version to create the version 3.05 of private message?

3.0.x-dev worked ... but 3.0.5 does not work. What happened?

This issue was a 3.0.x-dev issue, please do not change this afterwords, because this is still a 3.x issue and this problem still exists in the 3.0.5 version.
Thank you.

How can I help to create a new dev version that is working with the new API and contains the last patch?

I need a working solution as soon as possible and I am willing to help write some code or do the tests.

What are the next steps to do?

3.0.5 version does not work, same problems!
We testet a lot and the dev version was working. What have you done?

All the tests where in vain? You did not use the 3.0.x-dev version to create the version 3.05 of private message?

What happened?

Since v3.0.1 the problem exists.
Please publish a new version that is working. We already testet und the dev versions have been working without the problems.

Thank you very much.

When?

We will release shortly 4.0.0.-alpha1 and 3.0.5 if the -dev are OK for you

When?

This issue "Loading previous messages and listing last messages doesn't work" is an ajax issue.

Both, 3.0x-dev and 4.x-dev seem to work. But I am not sure.

And I can not install them via composer.
And I will NOT install any dev version on my productive site.

Please include code out of the patch #29 into v3.0.5 or have a look it the code is already part of it.
I will not use 4.0.0 as long as a 3.0.x version exists. There is no need for a 4.0.x version.
It would be glad to have a stabe. 3.1.x version soon.

I have done more than a half dozen tests and I generated/wrote patch #23, which solves both problems of this issue.
And all of the problems did not exist in v3.0.0. We should come to an end here.
Thank you.

This patch #29 for v3.0.1 solves both problems.
The patch for v3.0.4 must be the same or nearly the same.

Please include code out of this patch into v3.0.5!

Without patching this problem the module is unusable.

Thank you very much.

Nobody else here who has this problem?

Same problem in v3.0.4.

And ajax refresh in the inbox of the message receiver is not working anymore.

Tell me how I can help to write a patch for these problems.

drupalfan2 → created an issue.

Do you know, where in the code the problem is located?

Maybe I can help to write a patch.

The  starterkit: true is outdated.

The themename.starterkit.yml file should be mentioned on this page.

I tested it: Same problem in v3.0.3.

drupalfan2 → created an issue.

The problem still exists in v3.0.1 as you can see here:
https://www.drupal.org/project/private_message/issues/3486589 🐛 Answer is not shown in message thread after posting a new reply Active

drupalfan2 → created an issue.

drupalfan2 → created an issue.

Patch is no longer needet?

Full CKEditor 5 support is not needed in any case.

But what we need is to add the <video> tag to the allowed html tags of "Filtered HTML" text format.

How can I achieve this?

drupalfan2 → created an issue.

drupalfan2 → created an issue.

Patch #66 works for Drupal 10.3.2.

drupalfan2 → created an issue.

I had the same problem and an

item_selector: 0

instead of

item_selector: /

solved my problem.

I am using countup 3.x-dev and have the same problem.

I get this error message
Drupal\Component\Plugin\Exception\InvalidPluginDefinitionException: The "countup" CKEditor 5 plugin definition must have a plugin ID that starts with "countup_". in Drupal\ckeditor5\Plugin\CKEditor5PluginManager->processDefinition() (line 100 of core/modules/ckeditor5/src/Plugin/CKEditor5PluginManager.php).

when I am on /admin/config/content/formats/manage/full_html (edit Full HTML text editor format)

Additionaly I get similar error messages.

How can we move forward here to write/get a complete patch?

Patch #2 (3394691-2.patch) works for me.

Attached is the same patch as in #325 but with unix line endings.
Needed to be able to use the patch with an older version of the unix patch command line tool.

Allow translation of input placeholder - patch.

drupalfan2 → created an issue.

el7cosmos → credited drupalfan2 → .

Same problem here in version 4.0.2.
Patch #5 solved the problem.
We need a new version 4.0.3 including this patch.

New patch file

Patch file

drupalfan2 → created an issue.

Because we do not get the new release, I generated this patch file.

I have the same problem in v2.2.3 and dev version.
Mailchimp subscription does not work anymore on user registration.

I wrote the following patch to solve the problem.

Feel free to optimize the patch or provide another solution.

@mariacha1: Thank you.

drupalfan2 → created an issue.

Thank you.

I recently got this reminder from google:

[Reminder] Update your apps to the latest Firebase Cloud Messaging APIs and SDKs

We’re writing to remind you that starting June 20, 2024 the legacy Firebase Cloud Messaging (FCM) APIs will be discontinued.

On June 20, 2024, we’re reducing the number of Firebase Cloud Messaging (FCM) legacy register APIs and legacy send APIs that provide similar functionality. This step will allow us to provide you with a more consistent experience and align with Google security standards to improve security, reliability and performance.

Because of these API decommissions, some already-deprecated SDKs and features will stop working after June 20, 2024.

What do you need to do?
Take the following actions before June 20, 2024, to ensure that you have access to the latest supported features and to reduce the risk of future decommissions affecting your usage:
•Follow the instructions described in Firebase FAQ to migrate your individual APIs.
•Update to the latest versions of Firebase SDKs:

Android >= 23.1.2
iOS >= 10.10.0
Web (Javascript) >= 9.22.1

Your Firebase project(s) that use Firebase Cloud Messaging APIs are listed below:
◦Your recent usage of impacted APIs/features: Legacy HTTP protocol
◦Your recent usage of impacted APIs/features: Server Keys

Will this patch provide the needed actions?
Will this patch update the "Legacy HTTP protocol" and also the "Server Keys" topic?
Will this patch change over to the latest api versions?

Thank you.

Thank you for patch #25.

I am using patch #16 for a few years and I have changed to patch #25 (after updating the profile module) now, but both versions have the following problem:

When profiles are updated a new revision is only generatet when the logged in user is the admin. For other users no new revisions are created when they log in and update/change their profiles.

How can I solve this problem? I want to achieve that on any profile change a new revision is generated (also for non admin users).
Thanks.

#12 is solved here: https://www.drupal.org/project/profile/issues/3437825 🐛 Error: Class "Drupal\profile\ProfileType" not found Closed: cannot reproduce

Thank you very much, seems to work.

But I found another (older) problem of the patch #25: when profiles are updated a new revision is only generatet when the logged in user is the admin. For other users no new revisions are created when they log in and update/change their profiles.

So the first patch "Provide Views argument for current user's profile ID" can be removed?

Can you help to rewrite the second patch "Create the revision UI for profiles"?
Or will patch #25 work?
https://www.drupal.org/project/profile/issues/2599014 📌 Create the revision UI for profiles Needs review

Thank you very much.

Yes, in profile 1.8 I have applied 2 patches via composer.json:

            "drupal/profile": {
                "Provide Views argument for current user's profile ID": "https://www.drupal.org/files/issues/2021-03-23/profile-default-argument-2835930-3.patch",
                "Create the revision UI for profiles": "https://www.drupal.org/files/issues/2020-05-21/profile-revisions-ui-2599014-16.patch"
            },

drupalfan2 → created an issue.

After upgrading from profile 1.8 to 1.9 I get this error message:

Error: Class "Drupal\profile\ProfileType" not found in Drupal\profile\ProfileListBuilder->getDefaultOperations() (line 120 of modules/contrib/profile/src/ProfileListBuilder.php).
Drupal\Core\Entity\EntityListBuilder->getOperations() (Line: 212)
Drupal\Core\Entity\EntityListBuilder->buildOperations() (Line: 194)
Drupal\Core\Entity\EntityListBuilder->buildRow() (Line: 112)
Drupal\profile\ProfileListBuilder->buildRow() (Line: 242)
Drupal\Core\Entity\EntityListBuilder->render() (Line: 23)
Drupal\Core\Entity\Controller\EntityListController->listing()
call_user_func_array() (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 627)
Drupal\Core\Render\Renderer->executeInRenderContext() (Line: 121)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext() (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 181)
Symfony\Component\HttpKernel\HttpKernel->handleRaw() (Line: 76)
Symfony\Component\HttpKernel\HttpKernel->handle() (Line: 58)
Drupal\Core\StackMiddleware\Session->handle() (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle() (Line: 28)
Drupal\Core\StackMiddleware\ContentLength->handle() (Line: 32)
Drupal\big_pipe\StackMiddleware\ContentLength->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: 36)
Drupal\Core\StackMiddleware\AjaxPageState->handle() (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle() (Line: 704)
Drupal\Core\DrupalKernel->handle() (Line: 19)

Same problem with profile 1.10.

I do not allow multiple profiles per user, "Allow multiple profiles per user" is off.

And patch #16 of https://www.drupal.org/project/profile/issues/2599014 📌 Create the revision UI for profiles Needs review does not apply anymore.

I need a solution to get profile 1.9 and 1.10 running.

I am using mimemail and mailsystem without smtp.
In Drupal 9 it works without problems.

I have the same problem after Drupal 10 uprade and using 8.x-1.0-alpha6.

I need a solution.
Can you help?
Without soving this problem Mimemail is useless for Drupal 10.

Patch #11 helped me to get this module work with Drupal 10.

drupalfan2 → created an issue.

Please let me be an maintainer to be able to publish the Drupal 10 version of this theme.

Thank you for #11.

The solution is:

Open your webform in your browser, search for "form_id" in the html source and use the form_id to create a new captcha point.

Added patch #57 to composer.json
and this helped me to solve the problem at downloading files from /sites/default/files folder (page not found error for urls like /index.php/sites/default/files/filex.pdf).

drupalfan2 → created an issue.

#13 & #14 worked for me. Thanks.

drupalfan2 → created an issue.

+19: +1

I applied this MR 7 using this patch
https://git.drupalcode.org/project/views_entity_embed/-/merge_requests/7...

and afterwords my 2 embed buttons for embedding blocks and nodes did not work anymore. Each button wants to embed views instead of blocks or nodes:

This patch has negative effects on the Entity Embed module! Embeding blocks and nodes do not work anymore.

But I would need a working solution.
Can you help?

Thank you very much.

I have the same problem.
Patch #15 helps so far.

Hoping for a new version of the profile module with correct solution in it.
Thank you.

I have exactly the same problem:

Mailchimp 2.2.2
Drupal 10

I needed patch #15 in order to get it run after Drupal 10 Upgrade.
Patch #4 is also working.

Patch #17 worked after Drupal 10 Upgrade.

+1

I have the same problem.

Patch

drupalfan2 → created an issue.

On a node page, Drupal Core takes the title out of the normal page display. The manage display settings have no effect, and this module has no effect. The title will show in the title block, but if you don't display that block you won't see any title.

But on some sites and some pages we need to disable the tilte block and to show the title within the node (within the tag).
This is exactly what this module is for.

But the title within the node is not display, still if "Manage display" is configured correctly.

And again: When the title (Manage display) is not show then this module is not usable.

This is expected - the sub-module is obsolete now.

Then please remove the submodule immediately to avoid confusion.

The module works fine for nearly 3000 sites - only a small number have a problem. I have can't reproduce this bug when I follow the steps to reproduc

Maybe 2900 sites are using an older version of this module.

Please try to reproduce on a new Drupal installation.
Please ask for further information if you can not reproduce.

The Manage display still does not work. No title is show on node page (node/xxx).

The patch #24 is not working!

Actually the submodule manage_display_fix_title does only contain 1 file:
manage_display_fix_title.info.yml

A file manage_display_fix_title.module is missing!

The Manage display module is unusable! I had to remove it. It does not work.

The Manage display still does not work. No title is show on node page (node/xxx).

The patch #24 is not working!

Actually the submodule manage_display_fix_title does only contain 1 file:
manage_display_fix_title.info.yml

A file manage_display_fix_title.module is missing!

The Manage display module is unusable! I had to remove it. It does not work.

Okay, I found out, that $blue is set here:

/web/themes/contrib/bootstrap5/scss/_variables_bootstrap.scss
$blue: #003CC5 !default;

This should be removed!

drupalfan2 → created an issue.

I need patch #23 to be able to send mails to mail addresses @gmail.com .
Without patch #23 the SPF entry in our domain is not recognized by gmail and the mail is rejected from gmail.

So this patch should be commited as soon as possible.

I need a patch like this for Drupal 8.