How to change the background of the module?

[JKoutro]

I've been re-doing my MagicMirror and running into a visual clashing issue with my rotating background images against ExtCalendar3Agenda.

On my old setup I just used ExtCalendar3 and had enough trouble trying to dim down the entire calendar.

Now I'm revisiting and rebuilding MM as a server and trying out the agenda module instead of the other one and I'm stumped on how to alter any part of this module.

For example, a quick internet research gave me a simple custom.css edit which targets certain aspects of of CX3A, but nothing works.

.CX3A {
  background-color:rgba(0,0,0,0.6);
  border-radius:8px;
  padding:8px;
}

But when trying this or any other specific CX3A parts, nothing seems to even change. Even messing around on the module's .css gets me barely any changes, so I'm doing something wrong.

Looking into my old config regarding the Calendarext3, I don't even see where I got that to have a dim background, but it must be somewhere.

Green is showing up simply because that's the color set via the default calendar module.

I'm missing something big time but I don't see much that is set in the default .css that alludes to background color, and anywhere I do see it, I try to alter it either in custom.css or even directly as a test and nothing seems to take affect.

Is anyone able to point me in the right direction?

I'll place a sample image of how the Weather module looks and what I wouldn't mind going around the entirety of my Calendar and Agenda boxes, which I assume is all wrapped under one module. I'll paste my current Agenda view (black bars for redacted info).

Again, I'm only using Ext3Agenda, not CalendarExt3 on this new device.

[JKoutro]

Please delete, I'm dumb.

I had did one config on my weather module that worked, but then at some point started editing a different custom.css that I stored in my CSS folder and not using the one in the config folder.

I'm now able to get the backgrounds I want on the agenda!

[KristjanESPERANTO]

You're definitely not the only one this has happened to 🙂 The location of custom.css was moved in on of the latest releases.