🇺🇸United States @greenskin

When marking something as duplicate, it would be best to include a link.

greenSkin → created an issue.

Yes, what PCate mentioned. The issue is when using the published or unpublished form element, but not both.

Added an issue 📌 Actions broken when using workflow transition form Active with a merge request in Gin's issue queue to ignore the workflow transition form IDs. That issue fixes the general missing actions, while the patch from #2 here resolves the drop button getting hidden behind "More actions".

greenSkin → created an issue.

Dug a little deeper and the issue with the missing actions looks to be with Gin and how it's altering actions for the content form. Gin is effectively setting the actions based on the transition form and not the actual node content form (see GinContentFormHelper::formAlter()). Because the workflow transition form is altered after the node form, the workflow transition actions take precedence for Gin. I'm not sure there's anything specific the workflow module can do here other than work with gin maintainers for a solution.

Looks like something when building the transition form in WorkflowManager::getWorkflowTransitionForm() is causing the additional actions (e.g., preview, delete, etc) to disappear.

It would be fantastic to work with UI Patterns Settings → so settings can be exposed on previews and users can preview them in real-time.

Tested latest 3.x-dev branch and the icon shows correctly there, so there's something in the dev release that is missing from the MR when applied to RC12.

I'm seeing the same thing as rkoller. I've cleared Drupal cache and have browser caches disabled in dev tools. Tried in latest Chrome and Safari.

Patch from #27 applies clean for me, Drupal 10.3.0.

greenSkin → created an issue.

greenSkin → created an issue.

+++ b/modules/lightning_scheduler/src/Time.php
@@ -12,30 +13,59 @@ use Symfony\Component\HttpFoundation\RequestStack;
+    return $this->get('lightning_scheduler.request_time', parent::getRequestTime());

Should this not be calling get() on the $this->keyValueStore (patch from #11 🐛 Circular reference detected for service "cache.backend.database". Active )?

I like the idea of #5 but need it for setting a font color class but the "view" option doesn't appear to work for fontColor. We try to use Tailwind CSS for our themes and would love the option to apply these style options (font, size, color, etc) as classes.

We had come across an instance where the value had to be added as an expression (it used a mysql date function). However the original issue we had was an incompatibility with google_analytics_reports query (see https://git.drupalcode.org/project/google_analytics_reports/-/blob/4.0.x..., doesn't have an addWhereExpression() method) and the simple addWhere() was sufficient. If I recall correctly, the field returned the mysql date function as the field value.

greenSkin → created an issue.

Re-roll of patch from #22 for 3.1.0.

Re-rolled MR 50 against 2.2.3.

Rerolled patch from #37 against 8.x-2.4.

We have a need for this feature. Additionally we needed the title/label to reflect similarly, where it displays the active item's title when it has children otherwise it displays the parent's title. This patch is a re-roll of #42 with a new block label option that will use the active item's title when the item has children, otherwise uses the parent title.

Fixed patch paths.

Updated patch that conditionally uses `addWhere()` when the query object does not have an `addWhereExpression()` method.

Add forward slash at the beginning of the path for the admin settings route.

greenSkin → created an issue.

Here's a patch with the switch from using addWhereExpression() to addWhere().

greenSkin → created an issue.

Tested latest and still not working with Layout Paragraphs → widget. The button shows but is disabled. I'm still seeing use of .field--widget-paragraphs.

Latest commits to merge request #5 broke our composer build against 8.x-2.3. Here's a working patch from MR#5.

I'm looking for a compatible solution with Layout Paragraphs → . Pull request #80 does not seem to work with layout paragraphs.

Pull request #76 was closed in favor of #80.

We ran into this warning when exposing a filter as type "Grouped filters". Patch resolves the warning for us.

Created a merge request that provides the option to enable download.

greenSkin → made their first commit to this issue’s fork.

Attached patch that implements the proposed resolution.

greenSkin → created an issue.

Related to this? https://www.drupal.org/project/exif_orientation/issues/2895434 🐛 The module doesn't work with Imagick toolkit Active

I'm seeing this works when using GD image toolkit. However using imagemagick (via ImageMagick → ) doesn't really work. It seems that imagemagick does some level of orientation itself.

We are on Drupal 10.2 and don't believe we are using any module that affects file extension validation, but I'll spin up a clean install and see if I can reproduce the issue.

Note however that "file_validate_extensions" is deprecated and will be removed in Drupal 11. Maybe this is worth a D10+ release?

greenSkin → created an issue.

Implemented the post update to run orientation updates to existing files in batches.

greenSkin → made their first commit to this issue’s fork.

greenSkin → changed the visibility of the branch 3415622-access-control-isnt to hidden.

greenSkin → created an issue.

greenSkin → changed the visibility of the branch 3410023-php-8.2-compatibility to active.

greenSkin → made their first commit to this issue’s fork.

greenSkin → made their first commit to this issue’s fork.

Added file_url_generator to constructor to pass to ImageFormatter.

greenSkin → made their first commit to this issue’s fork.

greenSkin → created an issue.

#5 looks to work when expecting a single media reference, but only returns the first when the field references multiple media.

Found there's a `max_bundle_number` config set to 20 by default. If you have more content types (bundles) than this setting, you'll only see the first X processed. This setting is configurable at /admin/config/user-interface/admin-toolbar-tools.

Missing comma in editor settings JSON code.

The LinkitFilter doesn't look to work with the patch. I'm not seeing the additional attributes getting added to the tag.

Found the problem for my particular issue. My issue was resolved by setting the configuration on /admin/config/content/layout_paragraphs/modal-settings. Specifically I set: width to 90%; height to auto; and checked the "Modal autoresize" option.

greenSkin → made their first commit to this issue’s fork.

#21 does stop the jumping back to the top on scroll, but it doesn't keep the modal within the viewport. So the issue with #21 is on long pages with the edit dialog open, one could lose where the dialog is open/visible if they scroll too far above or below it.

greenSkin → made their first commit to this issue’s fork.

Confirmed, map files are missing for dist CSS and JS.
https://git.drupalcode.org/project/tb_megamenu/-/tree/3.x/dist?ref_type=...
https://git.drupalcode.org/project/tb_megamenu/-/tree/3.x/dist/js?ref_ty...

greenSkin → made their first commit to this issue’s fork.

greenSkin → made their first commit to this issue’s fork.

Here's a patch that adds a field handler to display a link to the rename form.

greenSkin → created an issue.

Re-rolled patch from #41.

Rolled patch from #27 that is compatible with 4.0.0-rc2.

We're witnessing these log messages when accessing pages that don't explicitly grant access (i.e., access result is neutral), which seems like a bug to me.

greenSkin → made their first commit to this issue’s fork.

greenSkin → created an issue.

The issue seems to stem from relying on the existence of the delimiter to determine current level while also not requiring the filter which includes a "- All -" option (code recognizes this as a level 1 when it should be 0 because of starting with "-"). Patch sets the current level to 0 when the key is "All".

Note am seeing this when using an exposed taxonomy field with "Show hierarchy in dropdown" enabled. When this hierarchy setting is disabled I'm not seeing the error.

Confirmed, we too get this error. Also seeing it in 6.x.

Attached a patch that provides empty array when tree is empty.

greenSkin → made their first commit to this issue’s fork.

Here's an update for patch from #21 that checks the entity ID is not empty when determining if generating the auto label is needed, i.e., if empty ID then auto label is not needed (don't auto-generate label).

Here's an alternate patch that moves the "isTitlePreserved()" check into the "autoLabelNeeded()" method and ignores preserving the title if the title is empty or is "%AutoEntityLabel%".

The patch only fixes the issue when the paragraph is contained within a region, not when the paragraph is the root element for the entity reference field. Confirmed patch needs work.

The patch does fix the issue I've been experiencing, using version 2.0.2. Thank you!

smustgrave → credited greenSkin → .

Still digging into the issue. I'm starting to think the inability to save is related to Layout Paragraphs, so will get a ticket created over there. But the "Orphaned" title is misleading. Would be better if it read "Unsaved" or something.

greenSkin → created an issue.