After the latest cornerstone update, images are not visible when uploaded to the background of the sections

Hello,

After the latest cornerstone update uploaded image to the background of the section is not visible any more. It is also not visible in the web page.

1 Like

Me too, gone back to 1.2

Hey @jstliy and @theotcspace,

Thanks for informing us of this and we’re so sorry that you’re running into this issue. This has to do with the fact that on the new sections, we were adding a default z-index of 1 to every section in our static stylesheets with the initial update to allow for the usage of our new advanced background feature, but this was creating an issue for users who were utilizing our section separators, as it was hiding those in certain instances.

With this latest release, we removed the static styling to fix the separator issue and because v2 sections have a control to adjust the z-index value for them. However, in the dynamic stylesheet, it is currently setup to not output if the value is 1 because that was previously in the static stylesheet layer.

We will have this patched in a coming point release, but for now you have 2 options depending on how you want to go about things:

Fix In the Builder

For the time being, as long as your z-index value for your sections or rows is anything greater than 1, your backgrounds will show back up. @jstliy, I adjusted the value of the section you referenced in your image to 2 and you will see that your image is showing back up now. This is quick and easy, but if you have a lot of sections throughout your site using the v2 advanced backgrounds, you may want to try our second approach below.

Fix with Temporary Global CSS

If you have too many section across your website using the advanced backgrounds, or you wish to leave their z-index untouched for right now since it will be patched soon, you can add the following custom CSS in a global location for your website (either in a child theme or the builder’s global CSS editor):

.x-section[class*="el"] {
  z-index: 1;
}

This selector is targeting any element with an x-section class that also has any class containing the string el, because each v2 section is output with a unique identifier for each instance such as el1, el2, et cetera. This could potentially result in a false positive for some sections that have a custom class that contains the string “el,” but since it’s only meant to be temporary and is only adjusting the z-index, it shouldn’t be a big deal.

The snippet above is meant to be removed after the coming releases: Pro v1.2.2, X v5.2.2, and/or Cornerstone v2.1.2

Thank you for your understanding while we work to get this out and we apologize again for this oversight.

Thanks for this solution. This was doing my head in. All good now.

Thank you very much! Works fine now.

Thank you, we will be fixing the issue on the next release which should be out soon.

Could you define soon? I’m 95% done on my website but I’ve built my whole site on parallax sections and now can’t build new sections because they aren’t showing up (in cornerstone or in preview) and not obvious how it all works, because it doesn’t.

Use the code supplied above and everything will work just fine. We are working to get another maintenance release out this week, but there is no ETA at present.

Unfortunately the code supplied did nothing for my problem

Is your problem the one listed above? If so, that code will work. Otherwise, please open a support thread with a secure note including your login so a member of the team can take a look.

Still having minor issues with z-indexing. But it is much better than it was aftter going to 1.2.2. Still had to add

.x-navbar-sticky {
z-index: 1;
position: relative;
}
.x-column:last-of-type {
z-index: auto;
}
.x-column.x-1-3 {
z-index: auto;
}

to get a couple of elements to play right.

Sorry it did work, I had only updated cornerstone which was the issue, once I updated the X theme as well it worked fine, thank you. There was no obvious indication that X theme had an update.

@loend43 Wanted to mention it here as well, but we’re happy to work with you on any outstanding issues over here: https://theme.co/apex/forum/t/left-fixed-header-got-worse-on-the-1-2-1-update/10632/6

@social Glad to hear it’s working again for you.

Just a follow up, Updated to 1.2.3 and all issues seam fixed. Thank you guys Great job.

Perfect! Glad that the issues are resolved. Thank you for using our product :slight_smile: