5.2.0. Beta 1 - CSS not loaded on the front-end

Beta
#1

Hi!

Exciting about this update!

I uploaded the Beta 1 to my staging site. Unfortunately, it seems that no CSS is being loaded on the front-end. All pages are broken. They look normal in Cornerstone. I disabled the caching.

I’ll give you the access in the secure note.

Oh, btw, one more minor thing:

Cornerstone settings save button is missing the text on it.

Thanks!

image

#2

Thank you! Confirmed. Something is off with Element CSS. It’s turning

$el .x-off-canvas-content {
  background-image:url(https://www.example.com/link/to/image.jpg);
  background-size:100px;
}

into…

.e3288-1 .x-off-canvas-content{background-image:url(https:background-size:100px;}

Will let you know what I find out there.

2 Likes
#3

Confirming this is fixed for the next patch. Was a side effect of allowing Dynamic Content in Element CSS.

1 Like
#4

That’s fantastic! I’m eagerly waiting for the next patch (with this fixed) so I can start testing the beta properly. It will be much easier when installed on a real (staging) website.

#5

Sounds good! We’re still working through a few items, but hopefully we’ll be able to get something out soon.

1 Like
#6

Hi @alexander!

The site looks a bit better, but it is still broken in many places:

  • Quote element is not loading
  • Content of an entire section missing
  • One of the header bars copied itself to the top of the page
  • Content area Off canvas flies in by itself on the page load (on the Outlet page)

This is in the console:

Summary

Uncaught TypeError: Cannot read properties of null (reading ‘style’)
at Jl (cs-classic.30e6da2.js:1:66894)
at cs-classic.30e6da2.js:1:66386
at oi (cs-classic.30e6da2.js:1:66111)
at cr (cs-classic.30e6da2.js:1:66059)

Another quick Beta would be great if this is just a minor bug. :slight_smile:

Thanks!

#7

Thanks! I’ll look into these and let you know when they’re worked out. Are you ok if I install a patched version on this site directly?

#8

Hi Alexander! No problem!

#9

Ok thanks! I’ll let you know what I find.

#10

Ok, most of the issues are sorted out. Still not sure what’s going on with the off canvas. I’m going to be out of pocket for a few days, but I’m pushing the current patch as beta3 so we can have more of those issues sorted out.

1 Like
#11

Great!

I am noticing also this:

  • Dynamic content pulled from ACF fields on Custom post types and custom taxonomies is not being displayed. For example, the images on the /o-nama/ page. It is a custom post type “zaposlenici” (Employees).

Also brand logos on the Outlet page should come from the custom taxonomy “Brendovi”, but they are not displaying.

I also tried to install Beta 3 on a newer staging site that has more custom post types, and none are displaying dynamic data.

Here’s the same page on the production site: https://www.optika-kobacic.hr/o-nama/.

Content area modal > Toggle > Bottom border: it has a set color, but it is not displaying it. (It displays the purple link color for some reason. The same is if I remove all the custom CSS.

image
image467×531 82.3 KB

Thanks!

#12

Thank you! We haven’t pushed another beta yet, but I believe both of those should be corrected by the changes we’ve made so far.

1 Like
#13

Hi @alexander!

I copied your patch to a newer staging version, to get it closer to the original website. Link is in the secure note.

I am testing page-by-page. You are probably aware of it, but just in case: the off-canvas is still flying in by itself and it cannot be closed on the first click.

Thanks!

#14

Thank you! I really appreciate you patience in all of this. I was able to track this down and correct it. For this cycle we’ve removed jQuery as a front end dependency and refactored it to use vanilla JS. The problem was that Accordions and Off Canvas use the same “Toggle” API under the hood. When the Accordion fires its “starts open” event, that was bubbling up to the parent and causing the Off Canvas to open. It’s explicitly not bubbling anymore which corrects the problem.

Unfortunately my dev site isn’t in a good place to bundle a patch due to other WIP going on, but it will be working when we get the next patch out.

1 Like
#15

Thank you @alexander!

One more thing. Probably Beta is not optimized yet and it will be fixed on the final version, but just in case:

Opening the same live page (in Cornerstone builder) on the live site takes a few seconds, while on Beta it takes forever. First the loader is on for a long time, then images come after that, and a lot later things like slides with dynamic content.

I am in a coffee shop right now with relatively good Internet but not great. So it might be partly due to that, but at the same time, the backend (Cornerstone) of the live version of the website is loading decently.

#16

Yes, I’m sorry, this is a known concern, especially on larger than average pages. We may still have some refactoring to do to get components fully working but once that’s done we’re going to do some profiling and see what can be tuned up.

1 Like
#17

Great!

For me, the backend speed might be the Pro’s number one advantage over pretty much all the competitors. It is so vital because time is literally money. Even one second longer loading time on simple tasks accumulate into a lot of lost dev time.

1 Like
#18

100% agree here. It was one of the biggest reasons I never switched to Oxygen.

1 Like
#19

@urchindesign absolutely. Before Pro had a lifetime license, I was considering Oxygen for simple quick builds. However I never actually did simple quick builds, and the second reason was just that: no matter how they are advertising it as a fast and optimized builder, the backend is unusably slow for me.

#20

I did a few cheap ones for exactly that reason. They ended up costing me money and I stuck with Pro…

1 Like