Branding not suppressed after update

Created on 5 August 2025, 2 months ago

Hello,
After updating a few websites I noticed that the branding and background image that where suppressed / removed are now again displayed.
I have attached a screenshot where I point a red arrow to those items.
In my custom css file I have the code below, which was already there previously.
On a site with exactly the same configuration with version 1.26 these items are suppressed as they were before.
As the code here explains commenting out or removing these lines should remove the image in the right sidebar and the brand image but after updating to 1.27 they are still there even with this code in place.

/* Erase or comment the lines below to get rid of the image in the right
sidebar and the brand image at the bottom

#middlecontainer {
background: transparent url(../images/_sidebarimg.png) 99% 99% no-repeat;
}
#brand {
background: url(../images/_brand.png) 50% 0 no-repeat;
margin: 0 auto 1em;
height: 50px;
}
*/

💬 Support request
Status

Active

Version

1.27

Component

Code

Created by

🇳🇱Netherlands RobBNL

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @RobBNL
  • 🇲🇹Malta florian

    Looks like your custom.css file is not being executed. You should go to theme settings, theme customization and put the correct path to your custom.css file, like "_custom/custom.css". Then refresh the caches.

  • 🇳🇱Netherlands RobBNL

    Hi,
    Thanks for your prompt reply.
    I have restored a website to a previous backup so that it was running the previous deployment with zeropoint v1.26
    In that deployment I do not have that field in the theme settings configured that points to my custom css. But it does work and my customizations are processed. Also in other web sites I had never updated that field but all my custom css files were processed.
    Then I update to v1.27 and my custom css is not processed.
    Then I update the field in the theme settings that points to my custom css and then they are again processed.

    It by default seemed to process my _custom/custom-style.css even without specifying it in the settings.

    But I am glad that I have a solution that if I specify the path to my custom CSS in the settings it is processed so with this issue it is now also documented for others that might seek for a solution.
    Thanks,
    Greetings,
    Rob

Production build 0.71.5 2024