After testing "Daily Digest" option last night have a couple observations:
- "Daily Digest" e-mails were blasted out at 11:38pm EST
- They look exactly like "Single Emails", plus there is no digest, they're sent individually (all at once) just like Single Emails
- If keeping "Daily Digest," there needs to be unique email settings for the subject line and body
- If keeping "Daily Digest" it might be worth doing it for ALL forum topic and comment subscriptions, one email total for everything you're subscribed to
- In that same respect, "Single Email" would be a single option that would apply to ALL subscriptions. Instead of one-by-one, as it is now for forum topics and comments.
In our experience, Drupal Forum is not used much to begin with. So Daily Digest may be overkill and just make this module Single Emails. That will also simplify the module, as users will not need to choose.
Just commenting this is an issue for me as well, as we only want Glossify on book pages. Thus, will create text formats only for the book content type with Glossify enabled.
Resurfacing this feature request for v3 if possible. Very similar need (see screenshot), except I'm using glossify_taxonomy instead of node:
- Have a term such as President of the United States
- Create field_acronym plain text field for same taxonomy, then enter POTUS into that field
- Glossify would treat either the name or field_synonym equally, applying to whichever appears first on a page
Great module! We're using it with the book module as a glossary of terms, which display as pop-ups on hover.
@kksandr success! Patch #104 worked with PHP 8.3 on 10.3. No errors in logs. Thank you
@joseph.olstad thanks for working on this, when I apply the patch in #104 I get this error:
ParseError: syntax error, unexpected identifier "DEFAULT_IMAGE_DIRECTORY", expecting "=" in Composer\Autoload\{closure}() (line 17 of /app/web/core/modules/image/src/ImageFieldManagerInterface.php).
Patch #94 not working with 10.3, so sticking to 10.2.7 for sites involving this.
Confirming #8 worked for me on core 10.2.3. The message went from "Could not retrieve the oEmbed resource." to something much more helpful, "An error occurred: Could not retrieve the oEmbed resource. Title of video here".
When you fix the media entity, the message stops showing. Thanks!
Confirming #2 worked for me on Core 10.2.3. The switcher was working fine on translation-enabled content that has a translation, but not on translation-enabled content that does NOT have a translation.
The problem also only appeared if you were logged out, not if you were logged in (at least as an admin).
Patch #94 via eiriksm worked for me on 10.2.3, many thanks.
Found same thing as nickbn when I upgraded to rc4 > rc5. So I reverted back to rc4. The images were loading full size with rc5, regardless of the width of the browser window.
Upgrading to core 10.2.1 caused #79 (and #89) to fail to apply.
I was using #79 successfully with 10.1.7.
Patch #2 worked for me, much obliged. This will help solve a lot of user confusion.
Confirming flyke's solution in #19 worked for me as well. Very helpful thanks!
layout_builder_iframe_modal is a bit wacky looking at least for me, but it works.
In Drupal 10 using either 5.4 or 5.5 alpha I'm getting a PHP error using this patch, so had to remove it:
DivisionByZeroError: Modulo by zero in template_preprocess_views_view_grid() (line 720 of /app/web/core/modules/views/views.theme.inc).
Tables work well, but if I was using something besides tables for the view display it would break (such as a grid).
Patch #11 also working for me. Thanks!
Confirming this patch worked for me, very helpful thanks! Not sure if it's related, but in order to edit the section afterward I also needed to apply this patch for media_library_form_element 🐛 Deprecated function: explode(): Passing null to parameter #2 ($string) of type string is deprecated Fixed . Otherwise clicking "Configure" did not bring up the dialog overlay.
Confirming #9 worked, I used asset injector to apply CSS to the Claro theme. Not ideal but it did the job.
For me, this was only an issue in paragraphs and in my case layout paragraphs.
As tomorrow is July 1st and that's the deadline, can anyone clarify whether we use the GA4 Property ID or Measurement ID? My understanding is the Measurement ID is the correct GA4 ID to use with this module (NOT the property ID).
Confirming #3 worked for me and I'm seeing same UI weirdness that @jcandan mentions. This is super helpful as I work on a lot of D9 sites using this module and we're about to upgrade them all to D10.
Hi @themodularlab the problem is we can't get into TB menu settings either. I can get to /admin/structure/tb-megamenu, but when I edit the megamenu I get a white screen. Anything using the front-end theme is broke, as I can't even log into the site.
Thanks @todea and @themodularlab fix/new version works great.