The latest OpenWISP reloads to the default CSS settings, overriding the custom CSS that has been created

[kevpiece]

Hi, I’m currently working on a project using the latest version of OpenWISP2.

I noticed an issue when applying custom CSS to some pages. After restarting the service, the custom CSS does not take effect anymore. If I restart the Ansible playbook, the custom CSS and cache are reset back to the default settings.

In the previous version (22.x), this problem did not occur — custom CSS remained intact even after restarts.

My question:
👉 Is there a configuration or recommended way to prevent custom CSS from being overwritten or reset after a restart/playbook run?

Thank you!

[nemesifier]

@kevpiece can you please share more details about the technical solution you used to apply the custom CSS?

Where did you place the file, did you define it in the ansible playbook?

[kevpiece]

I modified some parts of the openwisp.css file located in the static folder. The issue is that this CSS is cached, and every time I restart Ansible, the changes are reverted to the default.

So my question is if I want to add custom CSS/JS files, do I need to register them in the Ansible playbook? I couldn’t find where exactly the Ansible configuration files for these assets are located.

[nemesifier]

Refer to:

Deploying Custom Static Content & Customizing the Admin Theme

You don't want to modify openwisp's source code directly or you will lose your customizations when you upgrade.
OpenWISP is built in a way that allows to extend, configure or override a most of its features.