Standar "weather" Module: Doesn't keep header setting?

sdetweil

@rkorell module header not displayed?

.weather_forecast  .module_header {
    display: none;
}

Before I was giving you the classname of the header element

sdetweil

@rkorell the debugging:true was my choice to provide info during execution cycle vs startup.

It’s not relevant for other modules

There is an option in weather, by default it will append the location(from the api data) to the header.
You can turn that off

appendLocationToHeader:false,

rkorell

module header not displayed?
.weather_forecast  .module_header {
    display: none;
}

sorry doesn’t work, either :-(
I’ve even copied your phrase to avoid typos - nothing happens.
Sounds feasible and plausible, but don’t do the job…
Ive tried

.weather  .module_header {
    display: none;
}

Didn’t work, too…

really strange…
Thanks for any additional idea…

rkorell

@rkorell the debugging:true was my choice to provide info during execution cycle vs startup.

It’s not relevant for other modules

OK - Just a trial :-) - will delete, especially as no debug info is sent by module

There is an option in weather, by default it will append the location(from the api data) to the header.
You can turn that off
appendLocationToHeader:false,

This is an interesting addional hint, thanks.

The REAL problem/question is: Why do the module override my settings?
Reagrds,
Ralf

sdetweil

@rkorell weather is a complex mix of properties
I’ve never seen anyone complain about headers.

That property is the only one I know that manipulates the header

Also, weather is all in browser, so any debug will be shown there unless you use MMM-Logging or some such to redirect them to the startup log

rkorell

@sdetweil OK, tanks anyway.
It seems there is something special in my mirror.
Not that magic but unfortunate…