View more context

 

Firesphere

Why would an SRI for CSS work locally, but not on production? It's the same CSS that's build, it's the same hash that's generated, yet production throws a warning saying the sha's don't match

Firesphere

@Ramon Lapenta Not your fault, I'm in Saturday mode, so I just misunderstood 😄

Andy2708

I just created a new SS4 site from scratch, and my css isn't being updated after changes. I have to run composer vendor-expose to make it happen. That can't be right can it?

Andy2708

I'm also seeing all my uploaded images saving as draft. I know this was an issue on 4.1 but im on 4.3

Firesphere

Both are correct. Changes to CSS in the theme need to be exposed to the resources folder. You can do this by updating your webpack (or whatever tooling you use) to directly write to the public/resources/themes/yourtheme/dist folder, or expose every time

Firesphere

Concerning images, once uploaded, they are in draft. You need to publish manually. If it is on a relation, e.g. a banner image on a Page class, the Page class needs to have a $owns property, that triggers the publication of images (and files) that the page owns

Firesphere

If it is in the HTML Editor that the images are uploaded, I believe you still have to manually publish the images before they render

Firesphere

I'm not 100% sure about the latter though, you might need to test and check that 🙂