I have mixed feeling with that one.
On the first place, having DOMPurify a hard requirement is a good thing from security purpose, on the other end, it is not strictly required.
I will unblock a user with no DOMPurify at the moment, but still expect it in the library loading so it pops as an error in console.
Fixed in 2.0.3
RTBC
Fixed in release 2.0.2:
https://www.drupal.org/project/text_rotator_filter/releases/2.0.2 →
Correct !
As a follow-up for D10.3+ I will however move from Annotation to Attributes:
https://www.drupal.org/node/3229001 →
Thanks a lot for help and contribution.
I have not been able to reproduce a non-working scenario that would be fixed with the suggested change. Could you please expand on how to test this ?
Metatag was not supported on 8.x, please refer to #2501637: [META] D8 port: Roadmap and Feature Request →
The point is that metatag is now a field on the entity that can display many other sub-configurations.
I added minimal support for metatag (although i don't see the point). Now it could be made better by hide/show individually each metatag configuration I suppose, but that is another story.
This patch should do the trick
Fixed as part of ✨ Drupal 11 compatibility fixes for simplify Active
Fixed as part of ✨ Drupal 11 compatibility fixes for simplify Active
I had a bit of trouble with merging due to conflicts, but should be done properly with appropriate credits to you.
Thanks a lot for help
I added support for removing the thin unbreakable that might be within the content (just as ) and add narrow unbreakable space before/after a list of configurable characters.
Patch to fix D11 compatibility
Thanks a lot for your contribution, fix and test
Oh, totally down to my fault.
I received an automatic email from drupal.org with a list of modules of mine that still have releases for deprecated Drupal version.
So... I clean it out. Everything below Drupal 9 (did I thought) since the rest is EOL right ? Well.. not D7 that got extended lately.
But because of the ticket issue I mentioned, once a branch for D7 is removed from support list, you cannot undo it anymore (since August 1st apparently ).
This used to be a reversible operation so I did minded too much and so there is no warning message.
(Now that I mention it, actually that could be worth addressing on that parent issue that a confirmation message could be added)
I had to create a whole new branch because of this:
✨
[D7EOL] - Do not allow Drupal 7 branches of projects to be re-supported after Aug 1st
Fixed
That might be confusing now to users though since due to the release date it will sound like 7.x is still supported which is not the case.
@agoradesign yes I have upgraded to Drupal 10.1, hence use this module 6.x branch.
The issue you are pointing at seems to indicate that this module has became useless with Drupal 10.1, is that right ?
I had multiple issues with JS aggregation after upgrading my website from 9.5 to 10.1.
Changing advagg minification method from JSqueeze to another just solves them all.
Masonry is indeed a hard library to get working properly, so encapsulate it in a Drupal module above is even harder.
Please feel free to help make that easier, any idea is welcomed.
maybe related:
📌
Improve easyness of configurations
Active
New release done: 2.1.0
Sorry for troubles.
That is definitely something worth supporting indeed :)
Anyone up for creating a patch ?
RTBC for patch at #6.
Also, to get this to work, don't forget to activate the "-coalesce" option in the advanced settings (not really sure why this is not activated by default in the module?)
If you run /update.php, you should have got a warning telling to check your configuration.
On after1.jpg I can see the sizes for columns does not follow the "description" below.
If you save those settings, it should triger an "error" on the setting form because "250" on the column width do not have a unit.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Version 7.x is no more really supported. Just provided as is until end-of-life.
Feel free to reopen and update if there are reason we should still invest work on this.
Could you eventually get me a screenshot of your view settings and of the result, since I don't really figure out the result you have here.
The configurations now requires explicitely the unit for columns for instance.
Also by default, there is a new option (not the last one, just before) to force elements widh to column size.
Actually you can:
Anywhere you want, just add the syntax needed:
Here is a [rotate]simple|easy|cute[/rotate] way to rotate text
Could be on a page, could be on a view, anywhere.
Then, you will need to add the library and configuration to that specific page using hook_page_attachments()
:
function mymodule_page_attachments(array &$attachments) {
// Check if the page if the one you need from the $request
[...]
// Attach the library.
$attachments['#attached']['library'][] = 'text_rotator_filter/text_rotator_filter';
// Add the configurations.
$attachments['#attached']['drupalSettings']['text_rotator_filter'] => [
'animation' => 'dissolve',
'speed' => 350,
];
}
Sorry, you where right about compatibility because of jquery/once library change.
commited to 2.x with you credited
Thanks for help, 2.0.0 release is coming up.
+++ b/composer.json
@@ -5,6 +5,7 @@
+ "drupal/core": "^9.2.0 || ^10",
drupal/core should not be a dependency here as it is not made to be used externaly. The "type" is already defined to drupal-module.
see
https://www.drupal.org/docs/develop/creating-modules/add-a-composerjson-... →
Also the dependency is here 9.2+ while the module is declared to support D8+ according to info.yml file.
+++ b/w3c_validator.info.yml
@@ -1,7 +1,6 @@
+core_version_requirement: ^9 || ^10
why is this twice in the patch file ?
also why removing the support of D8?
+++ b/composer.json
@@ -5,6 +5,7 @@
"rexxars/html-validator": "^2.2.0"
Let's also update this to the latest 2.3.0
Stupid me, I forget to actually create the 4.0 release on drupal.org !!
Let me do this at the moment... et voilà ! That should be good now :)
Could you have a try and let me know ?
I'm so sorry, to much party at #DrupalDevDays Vienna !
Should be fixed by the usage of 4.x, which should therefore simplify that.
Crediting. Thanks for patch :)
After I updated masonry API to 4.x (configuration change), the purpose is now to make this module compatible with the newest version.
Somehow, I think this is already fixed in the latest 2.x version. Won't release a new 8.x-1.x version.
Somehow, I think this is already fixed in the latest 2.x version. Won't release a new 8.x-1.x version.
Perfect, thanks a lot for this correction :)
Dom. → created an issue. See original summary → .
Add a fix for standard autocompletion when no 'group' are provided.