0

Hi,   We are upgrading Mx7 projects to Mx8 and Atlas 2. These projects have their own custom theme. We followed the instructions on Mendix docs: https://docs.mendix.com/refguide8/migration-dom-issues/ and https://docs.mendix.com/refguide8/migration-atlas/.   However somehow after the upgrade to Atlas 2, the custom theme is no longer used.   On the Mendix troubleshooting pages I read the following (vague) comments:   “3 Streamlined Custom Themes Before Mendix 8, the client provided a large amount of default styling if your app lacked a theme. This made building your own theme difficult, as you needed to override the default styling. As of Mendix 8, all styling has been moved to AtlasUI. Now, building your own theme from scratch requires significantly less work. If you have already built your own theme from scratch in an earlier version of Mendix, you might depend on the default styling (specifically the Bootstrap files and the mxui.css file) not included in Mendix 8 applications by default. For this case, Mendix provides legacy mxui.css and Bootstrap files with defaults in this GitHub repository. Download files from this repository to enable your custom theme.”   Downloading these legacy files from the Github repository is not enough. Should we download the whole folder structure from the Github repository? Where should we put these folders and/or files in the project directory?   Are we dependent on these legacy files, or is there another way to use our custom theme in combination with Atlas 2?   Our knowledge about custom theming is limited. Our existing theme was created by external consultants, most probably based on the old Mendix UI Framework, when Atlas didn't even exist.   Kind regards, Elco Fransen

asked 2022-10-18

0 answers