Are you wanting all the blocks of this type to not be cached or only this specific block?

Which weather widget are you using?

You need to think of the block cache and page cache as separate entities.

w.r.t the block cache:

If the block cache is enabled in the dashboard, the way a block is cached is set by some constants in the block controller. The only way to change that is to override the block controller and change those constants. That changes the block cache behaviour globally for all blocks of that type.

I have been campaigning (without success) for a more selective control of the block cache, so its behaviour can be overridden for individual blocks, just like you can assign a block design or custom template.

w.r.t the page cache:

The page cache takes a snapshot of the rendered html for pages and cannot adapt to anything because it never even gets as far as testing for any reason to adapt before serving the cached html.

I like the idea of cache settings for individual blocks. That is the most logical and user friendly way to doing this.

Some links on previous discussion. The more concrete5 users say 'yes, we need it', the more likely it is that something will actually happen.

http://www.concrete5.org/developers/pro-accounts/community-leaders-...

http://www.concrete5.org/community/forums/documentation_efforts/spe...