Hey John,

Am getting this error when useing PageBlaster that is preventing my Menu from appearing. Any Suggestions?

"dnn.controls.initMenu is not a function" - Firefox
"Uncaught TypeError: Object #<an Object> has no method 'initMenu'" in Chrome

The only changes to the snapsis.config file were to

1) "comment or remove the next two exclude paths to further optimize DNN JS & CSS files"

2) "enable the replacement rules below"...

<replacementRules>
<rule>
<ruleName>Move dnn xhtml js to Head</ruleName>
<searchFor><![CDATA[[PB:IIF([PB:Request.IsAuthenticated]=='False')
{
(</head>.*?)(<script[^>]+dnn\.xmlhttp\.js[^>]+></script>)
}]]]></searchFor>
<replaceWith>$2$1</replaceWith>
<repeatTimes>99</repeatTimes>
</rule>
<rule>
<ruleName>Move dnn js links to Head</ruleName>
<searchFor><![CDATA[[PB:IIF([PB:Request.IsAuthenticated]=='False')
{
(</head>.*?)(<script[^>]+dnn[^>]+\.js[^>]+></script>)
}]]]></searchFor>
<replaceWith>$2$1</replaceWith>
<repeatTimes>99</repeatTimes>
</rule>
<rule>
<ruleName>Move dnn.Controls inits to bottom</ruleName>
<searchFor><![CDATA[(<script>dnn\.controls[^<]+</script>)(.*?)</body>]]></searchFor>
<replaceWith><![CDATA[$2$1</body>]]></replaceWith>
<repeatTimes>99</repeatTimes>
</rule>
</replacementRules>

</provider>

That's something that happened with the changes in DNN5.

There is a new default config with those replacement rules done a little different in a post pinned to the top of this forum.

I am using a 4.9.4 install. Should I still use the new default config in the stickied post?

If so, do I just copy the new files into the root and restart the application?

Thanks.

A couple of other questions,

1) does Pageblaster minify the js, css by default.
2) one of the rules (I havent spent too much time on it) is causing a problem with the CSS on the Module settings page (no matter which module). The module settings appear but with zero styling. Do I need to exclude the CSS file that contains these settings. If so, do you know which?

Partial Answer #2: is the default.css file must be getting merged and then for some reason not be able to be referenced. If I exclude default.css from mergecss, then problem 2 should be fixed - correct?.

<path pattern="default.css" excludeFrom="MergeCSS" />

Thanks!

The CSSMin and JSMin operations happen inside the CSSMerge and JSMerge routines, so you can exclude just the CSSMin, or JSMin, and still merge them, but if you exclude them from Merge then they won't be minified either.

I would have to see your specific problem, but you can try excluding each CSS file from CSSMin only and see if that fixes it.

Make sure you do a hard refresh or delete the CSS cache files when you make changes to the way CSS is optimized.

For the question about 4.9.4, the answer is yes, you need the new global replacement rules since 4.9.4 is essentially the same as 5.0

You can either just start with that config, or just replace parts of your old one if you already have changes in your current config file that you need to keep.