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?

I just started with Drupal in my current company(fresher, no prev knowledge either)

I'm in a project where they are running Drupal 10.2.7 on XAMPP with PHP 8.3.27 installed locally. I'm trying to install the config_split module and upgrade to Drupal 11, but I'm hitting a dependency conflict.

The Error:

When I run composer require drupal/config_split, I get:

drupal/search_api_solr 4.3.10 requires maennchen/zipstream-php ^2.2.1|^3.0.2 maennchen/zipstream-php 3.2.0 requires php-64bit ^8.3 Your php-64bit version (8.1; overridden via config.platform, actual: 8.3.27) does not satisfy that requirement. 

This issue is repetitive, for upgrade_status as well as Keys Module.

Context:

• I manually installed PHP 8.3.27 (outside XAMPP's bundled version)
• My composer.json still declares PHP 8.1 in the config.platform section
• I can't wait for XAMPP to update or switch to Docker/Lando—need a quick solution
• I'm using SearchStax (so I need to keep search_api_solr and its dependencies)
• Eventually want to upgrade Drupal 10.2.7 → 10.3 → 11.x

And have been told to not update composer since it brings about multiple thousand changes.

can somebody pls tell me any solution for this?

UPDATE: See end for some things I figured out.

I'm giving Drupal Canvas a look through and I'm trying to figure out where it works into the kind of sites I work on. It looks to me that Drupal Canvas is (currently) only a solution for building stand alone pages.

Is this accurate or am I missing something?

The sites I work on are highly structured and template driven. I'm just looking for something that will allow me and my users some flexibility within that structure, but not something that would require every publishing action to be a design decision. My current favored approach is to break the pages down into component blocks that can be manipulated with Layout Builder.

For the forseeable future, it looks like that might still be the most sensible approach?

---

UPDATE: I'm wrong that Drupal Canvas is only for building stand alone pages. It can also be used to manage a Display Mode layout or your site wrapper. The latter is evident since Canvas will actually disable your ability to use the Blocks Layout admin console for any theme that's added to Canvas.

However, speaking from the viewpoint of someone who builds sites with highly structured content, Canvas still appears to be most appealing to someone who would *want* to build stand alone pages with it.

Also, the best demo of Canvas I've found is the one in Drupal CMS 2.0 Beta. All the other ones I've tried are worthless.
https://www.drupal.org/project/cms/releases/2.0.0-beta2