🇺🇸United States @boinkster

boinkster → created an issue.

boinkster → created an issue.

Thank you! That is super helpful. Wondering how often the '/ //' UUIDs show up... probably will need to add logic to parse them all, just in case.

boinkster → created an issue.

These were helpful to me:
https://kentrichards.net/blog/drupal-radix-sub-theme-browsersync-ddev

You might have to install lts/iron, check https://stackoverflow.com/questions/61918002/install-a-specific-node-ver...
I did a:
ddev nvm install v20

Changing the directory to run the commands was confusing, so I created a custom DDEV command in .ddev/commands/web:

#!/bin/bash

## Description: NK Custom for Radix 6: Installs nvm version and frontier_radix stuff
## Usage: h2m_rdx_rw
## Example: ddev h2m_rdx_rw

GREEN='\033[0;32m'
RED='\033[0;31m'
NC='\033[0m\n' # set no color and line end

printf "${GREEN}Launching npm install inside ddev${NC}"

cd web/themes/custom/your-radix-subtheme

nvm alias default `cat .nvmrc`

#nvm alias default lts/iron

npm run watch

I added a check for the unset variable. There might be a more elegant way to solve this but it makes the error go away. Without it, I was unable to edit ECA models - the warning messages took up the whole page.

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

ECA is definitely the way to go. It's got a growing ecosystem and is actively developed and supported (Drupal Slack support is great). Guessing the Rules usage is mostly D7 when it WAS awesome.

Integrating with ECA is about adding action plugins. I did one for a custom module and it was well documented. I haven't look under the hood of Advanced PWA rules but perhaps a few actions and you could leverage the whole ECA world.

boinkster → created an issue.

boinkster → created an issue.

Thanks for the patch. This solved a problem I was having with numeric filters in a Views Database Connector → view.

boinkster → created an issue.

I can confirm that this a Gin problem. Tried the fix in #4 and the twig isn't loading. I haven't had time to track down what changed and where it's failing. If this isn't too much of a moving target, maybe it should be an extra module in Mercury or contrib.

boinkster → created an issue.

boinkster → created an issue.

Is it possible to populate the amount with a token from another form element?
- the user enters an amount in a number field
- a computed field adds a 3% markup
- this value is passed to the Stripe amount to make the charge

boinkster → created an issue.

boinkster → created an issue.

boinkster → created an issue.

I hit this with 10.2.0 today... I'll dig a bit and see what I can find.

boinkster → created an issue.

boinkster → created an issue.

It's unclear to me what is happening with the twig utility_classes ternary statement and subsequent classes merge. How does a value get passed in to utility_classes and why would you need to?

I'm new to SDC so don't have knowledge of whether utility_classes everywhere would be an issue down the road.

Still throws the same error after changing every navbar-brand_utility_classes to utility_classes in navbar-brand.twig

Working though templates with the fix suggested in #7, eventually leads to:

TypeError: Unsupported operand types: null - array in __TwigTemplate_7c900ea4bd68698dd0a963aeeff08683->doDisplay() (line 47 of /var/www/html/vendor/twig/twig/src/Environment.php(361) : eval()'d code).

Maybe quirks is too strong a word... just all the different LB solutions out there. Each offers different opinions and approaches. Some combine nicely, while some collide badly. The issue queue probably isn't the right forum to riff on this.

Looking forward to it. I keep bouncing between this and Layout Paragraphs - each has UI quirks for my use case and themes so choosing is difficult. Staying closer to core LB is preferable, though. Great work on this!

Would it be an option to use the default field value?

Thanks. it comes from an old nickname
A field sample value module sounds useful. My main issue is a couple of block types that have a potpourri of optional fields (text and media) with the intention that the user could edit as needed but never use all of them. I'll see if I can adapt your code to populate one but null the rest.

boinkster → created an issue.

The demo ran and installed for me without any issues. Installed on a local DDEV instance.

Could you please re-open this issue? I'm having the same issues on 2.01 and Drupal 10.

Is it possible to use a id's from a column in a remote table to create a relationship with a Drupal entity?

@freelock, I was able to use ECA to send an email with a attachment using Easy Email 2.1/Drupal Symfony Mail 1.3 with the patch here: 🐛 Update for Drupal Symphony Mailer 1.3 Fixed
Also, in ECA, loading a node before creating the Easy Email entity enabled content to be passed via tokens to the template before sending.

Not an ECA issue queue, but here's a POC that sends an email attachment. It's cloned model of the Asynchronous views export with an Easy Email addition. It sends a Views Data Export as an email attachment. It uses SMTP as a transport on the Drupal Symfony Mailer side.

Updated how file attachments are handled. It was a stdClass, but Drupal Symfony Mailer uses a array in Legacy mode.

boinkster → created an issue.

Trying to piece this together in ECA...
The plugin asks for an entity token, assuming that's an easy_mail entity. So would ECA need to create the entity as part of the model? Or how would you ref existing easy_mail entities?

The namespace needs to be updated.

boinkster → created an issue.

Another way to achieve this is to edit exported config then re-import:

edit your config/core.extension.yml file and remove the "classy" and "stable" elements under "theme"

then do a "drush cim"

https://www.drupal.org/project/drupal/issues/3328016#comment-14967373 🐛 Deprecated core themes cannot be disabled on the "Appearance" tab because they are hidden Needs work

Confirming that #24 worked for me - do a 'drush cim' after the edit.

This would be helpful on the project page. Entity clone is way more heavy handed and has less granular control on fields, not a bad thing if that's what you need. I had a project with a bunch of entity ref fields, some of them with nested ref's, Entity Clone enthusiastically cloned all the ref's down the stack (again, not bad and kind of cool - if that's what you need).
This module makes it easier for content editors to choose before committing to make a copy.