#21 and #25 seem to be the same issue. Has anyone else tested that scenario?
I did notice a configuration problem I had. It worked better after fixing that but got the "something went wrong" message after previewing and then moving the focal point and trying to preview again. Ajax errors too.
@kristofferwiklund yes, I see that code. I am seeing some Ajax errors in the console when I click preview link. The error is really long, mostly SVG. Not sure it's worth posting.
I'm still having the same issue after applying this patch. I'm finding it strange that there are several people claiming this works.
Drupal 10.3.5
PHP 8.1.27
DDEV
Focal Point 2.1.1
Is there something more to do than apply the patch and drush cr
?
A clean install of FP 2.1.0 also doesn't work as indicated in the description of the ticket.
This just came up now for me on Drupal 10.3.0
The solution in #13 worked.
Ron Collins β created an issue.
Confirming the patch in #17 works with Drupal 10.3.1 and that the patch in #19 is exactly the same.
It might be a mistake. Or maybe a span account looking for quick cred? It's their only post. Maybe don't confirm the account based on this alone.
In case this helps someone else, I got this error when I accidentally selected a mapping for a new blank source instead of a new CSV source.
@anybody 3.0.1 is installed.
There was one other patch applied: https://www.drupal.org/files/issues/2023-01-23/3283807-8-deprecated-func... β
Please take a look at this issue as well before committing this
https://www.drupal.org/project/anchor_link/issues/3394328
π
CKEditor5 - Link with id changes to anchor
Active
Seems that the module needs to move to 0.5.0 of the library.
/libraries/ckeditor5-anchor-drupal/package.json
"name": "@northernco/ckeditor5-anchor-drupal",
"version": "0.4.0",
We currently get composer conflicts when installing 0.5.0 so have to override.
I feel like this module could use a point release that fixes these issues and smooths out the install under D10.
User error! We had a space in one of the fields. Closing. We have another error now but I'll open a separate ticket for that.
Have the maintainers tried this module with Drupal 10?
Hi annoul4,
I have found that using version 0.5.0 of northernco/ckeditor5-anchor-drupal solves your issue. You may need to edit the library's package.json to use the same version (web/libraries/ckeditor5-anchor-drupal/package.json)
Hi dineshkumarbollu,
You need to follow these directions from the README.md:
To make sure the correct dependencies are pulled in through composer, you have to first add the following to the repositories section of your root composer.json:
{
"type": "package",
"package": {
"name": "annertech/rxp-js",
"version": "1.3.1.21",
"type": "drupal-library",
"dist": {
"url": "https://github.com/Annertech/rxp-js/archive/1.3.1.21.zip",
"type": "zip"
},
"require": {
"composer/installers": "~1.0"
}
}
}
Ron Collins β created an issue.
Just a heads up: this patch no longer applies (D10.2.2). I removed the conflict locally and I *think* the stuff this fixed is still working but I'm not super familiar with it so don't trust that. Perhaps the issue has been fixed elsewhere?
Ron Collins β created an issue.
Works for 8.1 as well.
This is the error under php8.1
Warning: Trying to access array offset on value of type null in popup_message_init() (line 120 of /home/kidsboost/kidsboostimmunity/web/sites/all/modules/contrib/popup_message/popup_message.module).
I can confirm that manually applying the diff fixed the issue for us.
Looks good and works for me on php8.1.
Worked for me while moving from php7.3 to 8.1.
This worked for me under php8.1
This worked for me. php 8.1
This worked for me.
Context was failing for anonymous users on the French pages after updating 3.11 to 3.12.
Patch #3 worked for me. Thanks.
Seems like an easy one to get rolled in for next release.
I've created a patch from the MR in #37 for Legal 3.0.1
#25 fixed the issue for me.
Was it fixed in 3.0.0?
I just installed Legal 3.0.1 on Drupal 9.5.7 and PHP 8.1 and was seeing the error. Adding the patch in #8 solved the issue for me. Uninstalling the patch makes the error come back.
I checked the repo and I don't see the changes from that patch in the 3.0.0 or 3.0.1 branch but perhaps you are suggesting it was fixed in a different way?
Jesus, rough morning. Looks like I made that patch off the wrong branch.
Hopefully this one is better.
We needed this patch against 6.x-alpha7 to prevent the error on php 8.1. I assume it will be helpful for others that don't want to move to the dev branch.
Sorry about the extraneous issue branch. I didn't think about the fact that I couldn't create the MR against the tag.
Ron Collins β made their first commit to this issueβs fork.
Ron Collins β created an issue.
The patch in #6 worked for me.