Question

5.0 Beta 7 to 5.0 - Theme destroyed

3

Just decided to take the leap and see how our Mendix 5.0.0-beta 7 project would hold up when converting to the first official Mendix 5 release. It hasn't. There were a number of java errors to work through (as always....) but what I currently cannot figure out is how to repair the theme. It has been completely destroyed by the new bootstrap 2.x to 3 upgrade. The release notes point to http://getbootstrap.com/getting-started/#migration but that doesn't help me. The fact of the matter is that I had a working theme and now it is nowhere close. The solution doesn't seem obvious. It started out by the bootstrap.min.css file being in a completely different location, but even pointing the index.html to the correct one does not solve anything. It seems the mxui.css file has changed completely. To be honest I am not really interested in bootstrap or following whatever conventions or upgrades it may apply - I was simply happy with the theme we had. Any way to get back to that point? Is there a clearer guide than what is on the link above? Why is it not optional to keep using the 2.x bootstrap version?

asked 2014-01-21

Querijn Chorus

3 answers

Eelco de Vries · Answer 1 · 2014-01-24

Hi Querijn,

thanks for trying out the beta of Mendix 5! From beta 8 to our final release, we integrated bootstrap 3 support that changes the way some elements are rendered. Besides, we changed certain naming conventions and display properties in the stylesheet to improve on our overall consistency in the way things are handled on the front end.

We have outlined a document that summarises some of the most important changes that make the theme more consistent with the rest of the front end elements. Older stylesheets will have the older naming, for instance, which makes it break - which is only an issue for our beta users, of course, as anyone starting from scratch in our final release should be fine.

I’ve dug out your email from our support systems and have sent you a document that outlines some of the impactful changes beta users might run into. If you apply some of the handful of changes back to your theme, you should be a good amount closer to what you had before.

If anyone reading this visits the forum with a similar question coming from our beta release, feel free to email me at eelco.de.vries@mendix.com and I’ll gladly send you the same document.

Kind regards,

Eelco

Elena Naum · Answer 2 · 2014-01-24

Hello,

I've ran into the same issue, having a custom css file for the project theming and then realising that the names for the classes had changed. Unfortunately, I could not find sufficient documentation for an elegant or even effective way for "migrating" themes, so I rebuild the css file with the new names for the classes.

That being said, i wish you good luck and maybe someone with a bit more insight can provide a more helpful answer.

Eelco de Vries · Answer 3 · 2014-01-24

Hi Elena,

I've sent you the same document as well. Do email me any feedback on what items or explanation may be missing, so I might be able to help out if things still are in too bad of a state for you to continue implementing your theme.

Kind regards,

Eelco