After installing pageblaster 3.4.5. The menu disappears when you click any administrative element. When loading any page that appears under the menu "admin" or menu "host", the menu bar disappears completely.

Well, after deleting the cache from pageblaster, it seems that the problem is reduced to just everything under the "host" menu. When loaded the page after clicking on any host menu item, the menu bar disappears completely

This only started after the upgrade?

There may be something interfering with the dnn menu javascript.
Try adding this line to your Snapsis.PageBlaster.config file

<path pattern="dnn.*\.js" excludeFrom="All" />

I added this pattern, I've restarted the application and deleted the cache, without success, the menu bar is still missing.

Please give me a link so I can look at the problem directly.
You can send it in a PM if you don't want to post it on the forum.

Hi John, I sent you a PM and also an email from outlook.
But I've gotten no response.
Please have a look?

Hi John. Need to show me how to solve these little problems with the module. It's important.

Thank you.

Hi guillermo,
Sorry for the delay. I'm not able to log in with the host information you sent.
Are you getting a javascript error on that page?

Hi John, have you seen anything about this?

Did you send me new login info?
Is it a javascript error on that page?

Yes I did, I sent the credentials through a PM. Also let you javascript error details ...

Ok, sorry I missed the notification for the private message.

I logged in and fixed the issue.

John,

Can you share the fix with us? I have a similar issue with a site. It can be remedied by dumping the disc cache and restarting, but this is a hassle.

TIA

Hi John. You've changed something in the web.config?
I had not accessed the site since before you say you were going to correct the error. Today when I go, I found this error:

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as allowDefinition = 'MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error:


Line 107: </ system.webServer>
Line 108: <system.web>
Line 109: <machineKey validationKey="A1E71AFAE44F2BC34BFA944B2C1FC50D5EC84ABD" decryptionKey="C93D2B1CACD1B39F50528DFAA6B26423AEDFA7F60CB4A270" decryption="3DES" validation="SHA1" />
Line 110: <! - HttpModules for Common Functionality ->
Line 111: <httpModules>

No, I have not changed anything since the last change that fixed the problem.

Chris,
What I did was remove the replacement rules in the Snapsis.PageBlaster.config file that move the JS files to the head so they can be merged. Merging is not working on guillermo's site.

<!--
<replacementRules>
<rule>
<ruleName>Move js links to Head</ruleName>
<searchFor><![CDATA[(</head>.*?)(<script[^>]+(ScriptResource|ControlPanel|Search|dnn[^>]*)\.(axd|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>
<rule>
<ruleName>Move initWidjets.js to bottom</ruleName>
<searchFor><![CDATA[(<script[^>]+initWidgets\.js[^>]+></script>)(.*?)</body>]]></searchFor>
<replaceWith><![CDATA[$2$1</body>]]></replaceWith>
<repeatTimes>99</repeatTimes>
</rule>
<rule>
<ruleName>Move dnnNav inits to bottom</ruleName>
<searchFor><![CDATA[(<script[^<]+dnn\.setVar[^<]+</script>)(.*?)</body>]]></searchFor>
<replaceWith><![CDATA[$2$1</body>]]></replaceWith>
<repeatTimes>99</repeatTimes>
</rule>
</replacementRules>
-->

That was exactly the change that you did? I must speak with the support of the hosting service.

I, even I have agreed since my last post (almost a week ago that, just the 2nd day of this month)

This problem will affect everyone with stock FriendlyURLs (maybe just newer DNNs idk). According to this line, both Admin and Host are to be excluded from PB
"<path pattern="/admin/|/host/|install|jquery" excludeFrom="All" />"
But there's no "/host/" in querystring, if you change it to "portalid/0/" then it will work. But again if you don't use FriendlyURLs this won't work for neither admin or host. So I guess this expression was meant for different FriendlyURLs engine or older DNN?

Unless something has recently changed, you should be able to get those human friendly Urls in the core DNN FriendlyUrlRewriter by setting urlFormat="HumanFriendly" in the web.config on the FriendlyUrlRewriter settings.