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

rkorell

Answer yourself is a nice sport :-)

sometimes structured telling hepls thinking - or in other words:
How I can I know what I mean before I’ve heard what I’ve said …

As I read my own words - I’ve seen that it might be a good idea to test, if the header must be set indentical in both instances…

Leaving them both commented - so “blank” doesn’t work.
Setting both to something “not null” at least survives some PIR-switch-offs …

Keep you posted.

nevertheless with two headers it do not look nice so I’m still looking for a hint, how to get this done properly …
Thanks so far.

Ralf

rkorell

Additional question as CSS rookie:
I’ve tried to identify the object of the header.

how can I address this correctly?
Sorry, I’m not able to figure this out.

My best guess is

.weather_forecast .header {
  border-bottom-width: 0px;
  color: black;
  font-size: 0px;
}

but this doesn’t work.
How do I make this right?

Thanks!
Ralf

sdetweil

@rkorell .module_header

rkorell

@sdetweil thanks.
But this seems not to work.

.weather_forecast .module_header {
  border-bottom-width: 0px;
  color: black;
  font-size: 0px;
}

changes at least not, what I would like to happen: not visible regardless of content, so text color black and line below not visible, as well - line thickness (border-bottom-widht) 0 …
What I’m doing wrong?
Am I on the wrong properties?
Thanks again,
Ralf

rkorell

No, setting both headers to a text doesn’t help.
Any suggestion where THIS error comes from???

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