🇺🇸United States @nkraft

nkraft → created an issue.

I've gotten this working just now on a Drupal 10 website. So far, so good.

The instructions are lacking on the project page.

First enable the module, and one of the "Sub" modules. I picked the taxonomy related sub module, and then I created a new Drupal vocabulary that I called "Glossary."

Then I went into the configuration for my "Full HTML" text format, located here:

/admin/config/content/formats/manage/full_html

Then you have to follow TWO significant steps on your text format.

Step 1) under the "Enabled Filters" section, be sure to check the box next to the new Glossify filter (screenshot below):

Once you've done this, proceed to...
Step 2) scroll down to the "Filter Settings" section. ENabling the Glossify filter above should have loaded and exposed a new vertical tab in this area called "Glossify: Tooltips with Taxonomy". You need to go here, and check some additional configuration options -- suchy as WHICH taxonomy you want to load as a your glossary; whether to use tooltips and/or links; and whether or not to enable "case sensitive". (Screenshot below) Once you've updated your settings as desired, be SURE to save your changes at the very bottom of this screen. Then check out any node that has a word matching a term in your newly created glossary vocabulary -- and you should see that term now getting underlined, with a tooltip displaying the "description" you saved under a matching term in your glossary.

I just attempted to install the dev version of this module, and got this complaint (over and over and over) in lando composer:

lando composer require 'drupal/drulma_companion:2.x-dev@dev'

Problem 1
- drupal/core_event_dispatcher[3.0.0, ..., 3.2.0] require drupal/core ^8 || ^9 -> found drupal/core[8.0.0, ..., 8.9.20, 9.0.0, ..., 9.5.11] but the package is fixed to 10.1.7 (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/core_event_dispatcher[3.3.0, ..., 3.3.4] require drupal/core ^9.3 -> found drupal/core[9.3.0, ..., 9.5.11] but the package is fixed to 10.1.7 (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/drulma_companion 2.x-dev is an alias of drupal/drulma_companion dev-2.x and thus requires it to be installed too.
- drupal/drulma_companion dev-2.x requires drupal/core_event_dispatcher ^3 || ^4 -> satisfiable by drupal/core_event_dispatcher[3.0.0, ..., 3.3.4].
- Root composer.json requires drupal/drulma_companion 2.x-dev@dev -> satisfiable by drupal/drulma_companion[2.x-dev (alias of dev-2.x)].

Please fix

hi! we've been watching this for client sites. We just tested 10.2.0 -- and we are not seeing the presevation of commetns, they are still being stripped.

Does 10.2.0 have this fix natively, or does it rely on some additional plugin to be installed still? was testing done? I don't see any "RTBC" comments above for the work done by star-szr

Thanks for your efforts! We're really eager to see this patched into CK5. These sorts of issues have been causing us all sorts of headaces on our enterprise sites.

The patch in #18 PLUS the config update in #23 from AndySimple worked for me!

I applied patch #18.
Then went into my config sync folder, searched for: node_type
And then changes all instances related to view_mode_page from:
node_type to entity_bundle:node

then ran: drush cim
top import the modified config files
then
drush cr

And voila! My view mode pages are back and working correctly! Thanks alll, you saved my day, getting ready to take D10 live hopefully tomorrow. Cheers to you all.

Was there an UPDB hook for this? I ask because I just jumped through some unexpected hoops, dealing with the old, deprecreted MRSS module, and the new sub-module --

Specifically, here's my steps, and where i ran into problems:

1) used composer to update Views RSS to 2.2
2) disabled MRSS module... but left in composer and project, disabled
3) did NOT attempt to run DB updates
3) checked my rss views... missing media items
4) could not find way to enable missing media components in view
5) started digging around
6) realized MRSS ahd Views Advanced RSS: Media (new submodule) had same machine name of views_rss_media
7) used composer to remove MRSS module
8) Views RSS disappeared completely from /admin/modules
9) manually ran check of module updates available, and also drush CR
10) Views ADvanced RSS reappeared in /admin/modules
11) and NOW Views Advances RSS: media appeared in /admin/modules, though not enabled
12) enables Views Advanced RSS: media
13) checked my rss view -- everything seemed to snap back into place, and my RSS feed was rendering correctly again.

Was there a way I could have avoided all of the above confusion? Some UPDB install/uninstall hook maybe I forgot to check for? Just want to make sure I do it right next time, and see if I can save anyone else the confusion. Thanks for all your recent work getting this into D10!!

Adding a note for anyone else falling down the same rabbit hole I just did.
https://www.drupal.org/project/ideas/issues/3265493 📌 [Policy] Move book to contrib in Drupal 11 Fixed --
Managers of Core have decided to deprecate the module, and remove it from Core as of Drupal 11 -- which means the OTHER related ticket/report, referred to in the previous comment, decided to drop their patch entirely from being applied to Book going forward. I'm hoping my clarification here might help others that come after me to this thread :)

nkraft → created an issue.

nkraft → created an issue.

As discussed over DMs, this problem is still occurring as of the current release. Re-opening this bug :)

omg, how is this still a problem? My dev team requires that we handle ALL libraries through Composer, rather than manually tracking files in the "libraries" folder.

The module is still upset that I don't have "dropzone.min.js" -- even though I followed tthe project page instructions exactly, AND I DO have dropzone.js (no MIN) in my libraries folder.

This seems like it should have been updated or patched appropriately by now. Am I missing instructions somewhere? Or can I safely abandon this module finally?