I can't seem to find a clear write up on this - but I need to build a user contact form with webform, and send an email to user's email account....

A user will look at a user profile at "/user/[user-name]"

And see a link to a webform, and I want the link to be something like

"/user/contact-form?userid=123"

Or "/user/contact-form/123" and have the email handler on the webform be able to look up user id 123's email address, to send to...

Is there a token syntax I can use in the "TO" field in the email handler?

or... how would you do it?

Thanks!

I can't believe it's been a quarter of a century! I wrote a reflection post on LinkedIn https://www.linkedin.com/feed/update/urn:li:activity:7417497520567750656/

But for anyone reading here, thank you for being part of this great journey. I'm grateful to everyone who helped out along the way.

-Robert

I have a weather block I built. Obviously I don't want it cached for the next week, but this is what Drupal is doing using its out of the box page caching.

That would be fine if I could find a way to override this, but I can't. I've tried everything suggested on various forums, but nothing is working.

The last thing I tried was creating a lazy builder but I couldn't even get that to work.

I don't entirely understand how Drupal caching works. But all I want to do is set the cache of the entire node (or ideally just the block) to an hour or two.

I have Redis caching set up if this makes any difference.

Any ideas? Thanks

EDIT:

I seem to have something working, although it's possibly not as granular as I would like. I did 3 things, and I'm not sure which worked and whether it was individually or in combination.

1. Installed the Cache Control Override mod - https://www.drupal.org/project/cache_control_override

2. Added this to my settings file:
   $config['system.performance']['cache']['page']['max_age'] = 3600;

3. Added this to the block build array (in conjunction with existing 'max-age' => 3600,):
   'tags' => ['weather:' . $nid],

Will now do some experimenting to figure out which is essential. Note - It didn't work without 3.

I’ve been working with Drupal for a while and I’m curious how others handle ongoing support and maintenance.

When you run into Drupal bugs, configuration issues, or performance problems:

- Do you rely on forums?

- Slack/Discord?

- Internal devs?

- External support?

What works well for you, and what doesn’t?

I’m genuinely interested in how different people manage this, especially for smaller teams or solo developers.

I know there was a scandal with the Pantheon founder a couple of years ago. Do you feel like they have done the work to find justice?

Are there other great places to commit to Drupal in 2026?