Well, I waited for version 2.0, no change, then for version 2.01 to come out, but it doesn’t make any difference.
If I have “epik-darkblue” set up as my default color scheme, for example, and then I select for a specific page a custom body class of “epik-black”, in the raw page HTML I can see the line ~
<body class="page page-id-1172 page-template-default logged-in mp6 custom-header header-image full-width-content epik-darkblue epik-black" itemscope="itemscope" itemtype="http://schema.org/WebPage">
Both are color schemes are called but only the “epik-darkblue” shows.
However, if I leave the default set at “epik-darkblue” and then change the same page’s custom body class to “epik-pink”, the page then becomes pink.
So the custom body class “epik-black” doesn’t work in combination with “epik-darkblue” in the standard CSS setup, but the combination with the custom body class “epik-pink” works, for some reason.
This is with the standard CSS supplied as the HTML5 version of Epik.
Any ideas? I have been trying for ages to get my terms and conditions pages to be in black.