Hi David, That’s indeed quite unusual, as we haven’t received any similar reports. I also tested it on our end, and the module appears to be working perfectly fine. It’s possible that the specific instance of the module became corrupted, or that a recent update caused a temporary conflict with the previous instance — which could explain why adding a new module resolved the issue. I’m glad to hear it’s working fine now!
SOLVED (kind of...) Ok I've been looking a little more into this, because I added a Divi Blog post, the native one, and I was still having the same issue. For their module, Divi Support, told me to solve it by changing the layout of the module to "Grid". So my wild guess is that when Divi added the Grid feature, something broke in the Divi Supreme modules that already existed on a website. So here's what I've tried: 1) I created a new page on my website and added a Divi Supreme blog module. This one works fine, no issues there. It shows the selected columns in the front end as it is designed in the back end. 2) I created a new section in an existing page with the known issue. This didn't work, the Divi Supreme blog module is broken in the front end. 3) So I saved all the sections on my page to the Divi Library except the Blog, and then created a new page. Here, first I created a Divi Supreme blog module and tested it. Then I added all the sections from my original page, tested again and everything was working fine. PS: All my CSS is added in the "Theme options" section, in order to avoid issues with the CSS in a specific page.
I'm sorry for this rant but why would you say that there aren't any similar reports? There's a bug report from Kyle King reporting exactly the same issue. Also, adding a new module didn't solve the issue, I had to create a new page within my website to solve the issue.