The API is "firmly in place" - meaning we can't disable it. However, we can configure it as we see fit - and disabling file combination can help if someone runs into issues with it. However, issues that are coming up with the new system that are *not* related to file combining are most likely due to ordering issues.

jQuery, as a rule, is placed in the head of the page, along with all of the CSS files. However, there appear to be ways to get stuff (CSS and JS files) to load even higher up in the head than the CSS & JS files that are loaded through the API. So far the two things that seem like they might be doing that are contents of the DNN page header and the dnn:styles skin object.

Here is the Gemini issue that is related to this topic for posterity: http://support.dotnetnuke.com/issue/V...

Ian

---

Got this from Evan...seems DNN "broke" CSS ordering in this release....

Hi Roy,

---(Please disregard my message earlier)

Thank you for purchasing Morpheus and SkinLab and for the details.

We are working on ways to fix this particular issue right now.

UPDATE --

In versions prior to DNN 6.1.0 any stylesheet added using the DNN STYLE token was added at the bottom of all other CSS files being added to the same skin. So they appeared in this order :

1. default.css
2. skin.css
3. container.css
4. portal.css
5. SkinPst.css - added to the skin using STYLE token.

In DNN 6.1.0 however (released earlier today) the stylesheet added using DNN's STYLE token is added at the top of all CSS files loaded on the page. The stylesheets appear in this order:

1. SkinPst.css - added to the skin using STYLE token.
2. default.css
3. skin.css
4. container.css
5. portal.css

Now this causes issues because CSS classes and style definitions (in the SkinPst.css file) that previously dominated the same styles defined in other CSS file are no longer taking precedence because of the reordering of the CSS files.

We are looking at ways we can fix this within the skin, although its actually, probably an oversight by DNN corp. This will cause issues with all skins that use the DNN STYLE token to add stylesheets.

A fix for this issue in the skin will only complicate issues because DNN Corp. may rearrange the CSS again later in an attempt to fix the reordering issue, causing issues with the newer fixed version of the skin.

It was a drastic change by DNN, and no documentation or notification of such a change was released. I have no idea if this was intentional (DNN wanted to rearrange the CSS) or coincidental because of some other work they did to the way stylesheets are loaded.

I will update as soon as we have a new version or a fix for this. I'm sorry for the trouble.

Have a great day, best of luck with your projects,
Thanks,
Evan O'Neil.

Hi Roy,
I want to upgrade to DNN 6.1.0 and have also the Morpheus skin and just before take a look on the forum and now i think it si the best way before upgrading a solution !!
i suppose the fix or new version can be download by snowcovered.com in Patch or a link ?
hope that include the manual to setup correctly
thank you for your help
best regards

---

Cheers from France, Michel