Branding settings are saved correctly but are not fully applied on public forms

I am using FormVox 1.4.6 on Nextcloud and I noticed that the branding options do not fully override the default Nextcloud styling on public forms.

In the global FormVox branding settings I configured:

Primary color: #d8a906
Background color: #fff8f0

I also tested custom branding configured directly on an individual form.

The settings are saved correctly. I verified the global values with:

php occ config:app:get formvox branding_globalStyles

which returns:

{"primaryColor":"#d8a906","backgroundColor":"#fff8f0","fontFamily":"default"}

So the problem does not seem to be related to saving the configuration.

On the public form page, parts of the interface still use the default Nextcloud blue styling instead of the configured branding color.

For example:

• the public-page header can remain blue
• some primary buttons use the default blue
• some hover/focus states and accents remain blue
• the page background can still be affected by Nextcloud default styling instead of the configured background
• the issue also occurs when using per-form branding instead of global branding

This makes the branding feature feel only partially applied.

While troubleshooting locally, I noticed that css/public.css in FormVox 1.4.6 still contains several hardcoded Nextcloud blue values

For example, the public header includes a hardcoded blue background, and some primary button styles also use hardcoded blue values.

The public form frontend does receive the configured branding values, because some elements correctly use the selected color, but other Nextcloud Vue components and CSS styles appear to continue using the default Nextcloud theme variables or hardcoded colors.

I was able to work around the problem locally by making the public form use the configured FormVox primary/background colors consistently, so the stored branding data itself seems to be correct.

It would be great if the branding settings could be applied consistently to the whole public FormVox page without requiring local CSS/frontend modifications.

Thanks!

Start with css/public.css and the public form frontend paths that consume the global and per-form branding values. Trace the hardcoded header, button, hover/focus, accent, and background styles alongside the configured values. Done means the public page consistently uses the selected branding instead of the default Nextcloud blue styling.