@sourabhsisodia_ I did some testing and found this:
It only seems to happen when "Prevent text wrapping separating the last word from the icon." is disabled AND font-awesome is enabled.
These values is extlink.settings.yml
extlink_use_font_awesome: true
extlink_prevent_orphan: false
drumanuel → created an issue.
I'm having the same problem (also in Chrome).
Instead of removing the disableFacet function, I went for a change to the unload function.
What I found is that onunload is triggered in Firefox (and Chrome) after pressing the browser's back button, while onbeforeunload is not.
I could have used the solution discussed here, using both onunload and onbeforeunload, but I'm not sure why this would be better than the solution in the attached patch.
https://stackoverflow.com/questions/6895564/difference-between-onbeforeu...
What was the solution?
Created a patch for 2.0.0-alpha10
Got this issue on Drupal 10.3. Patch does not apply.
Got warnings for offers and hasCourseInstance
Here an issue has been logged for hasCourseInstance
https://www.drupal.org/project/schema_metatag/issues/3410151
✨
Missing field 'hasCourseInstance'
Active
Why not set this under system.entity_autocomplete
requirements:
_access: 'TRUE'
to something only available for logged in users?
The problem occured because the date filter was based on completed date, always excluding drafts.
Created a patch based on changed date (applied to beta10).
Drafts seem to be filtered out by default, but when enabling "Include draft submissions", nothing changes, drafts are still not included in the analysis.
Same here
Many improvements here. The module seems to work now using this fork, it didn't out of the box.
Any plans on merging?
Same problem here
Entity Usage 8.x-2.0-beta12
Drupal core 10.2.2
TypeError: array_filter(): Argument #1 ($array) must be of type array, null given in array_filter() (line 273 of modules/contrib/entity_usage/src/Form/EntityUsageSettingsForm.php).
Made a patch for this based on 2.0.4
Prefer a patch? I do
I see this problem too.
Because this module works on all roles, every user will be restricted if no terms are explicitly selected.
A fix would be to enable the functionality on a per role basis. This way only specific roles (e.g. editor with limited permissions) could access nodes by term, other users won't be affected.
Drumanuel → created an issue.
Drumanuel → created an issue.
I have the same problem as mariohernandez #150, it doesn't seem to work in Layout Paragraphs
Update:
By using a bunch of patches it is possible to get the paragraph stable widget to be multilanguage. My patch for Gin is not needed in this case.
At least these:
"drupal/paragraphs_asymmetric_translation_widgets": {
"#3358805 EntityStorageException on paragraphs_asymmetric_translation_widgets_entity_translation_delete" : "https://www.drupal.org/files/issues/2023-05-08/paragraphs_asymmetric_translation_widgets-entity-query-access-3358805-2.patch",
"#3171810 Support experimental widget" : "https://www.drupal.org/files/issues/2020-09-25/3171810-2.patch"
},
"drupal/paragraphs": {
"#2904705 Support asymmetric translation in experimental widget" : "https://www.drupal.org/files/issues/2023-09-27/paragraphs_support_asym_translations-2904705-141.patch"
}
Drumanuel → created an issue.
Like a charm! 👍
Drumanuel → created an issue.
I have the same issue. The linked site is not routing back correctly because of the encoded link in the query string.
What is a sensible solution?
Apparently the URL encoding "works as expected". Should the third party (ezproxy.domain.com in example above) change their handeling of encoded URLs in query strings?
Added a patch with refactor to use drupal/once
Drumanuel → created an issue. See original summary → .
I have a similar problem in Chrome. Firefox seems to open ans save .webp as expected. Chrome saves the images as .txt.
Fixed it by putting this is my composer.json
"patches-ignore": {
"drupal/media_library_media_modify": {
"drupal/inline_entity_form": {
"Changes are lost when collapsing a paragraphs subform including an inline_entity_form": "https://www.drupal.org/files/issues/2022-09-22/47-8.diff"
}
}
}
As reported by others: Tested patch 34 with Focal Point module and all is working as expected.
webp 1.0.0-beta7
focal_point 1.5.0
core 9.5.9
Thank you for the feedback. Will look into it.
Ok, had to do some checks in Drupal 10, did want to rely on the automatic update only. It turned out to be OK.
Will apply later, this can be deleted.
Drumanuel → created an issue.