DNN File Manager

Rate this topic:

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Author

Messages

Shawn

Posts:5

07/28/2006 9:13 PM
First off - nice job on this module. My testing showed it to decrease my pages in size about 19%. Quite significant. I am having a problem with the DNN File Manager. I can't expand any of the treeview nodes in the left nav pane when using the PageBlaster. I have tried to exclude the Admin and Host areas, but perhaps I am not doing something right? I did empty the cache folder after setting the excludes. Any help would be appreciated. Thanks, Shawn

Mariette Knap
<250Posts

Posts:102

07/29/2006 3:13 AM
Add the following exception to your Snapsis config file:

Mariette Knap - www.smallbizserver.net

Mariette Knap
<250Posts

Posts:102

07/29/2006 3:13 AM
<pathpattern="46" />

Mariette Knap - www.smallbizserver.net

Mariette Knap
<250Posts

Posts:102

07/29/2006 3:14 AM
And do the same for tab 19

Mariette Knap - www.smallbizserver.net

Shawn

Posts:5

07/29/2006 6:35 AM
Thanks that did the trick. I'll exclude by tabid next time should I need to. Will this issue be present on any page that uses a treeview? Shawn

John Mitchell
Posts:3471

07/29/2006 1:40 PM
Posted By shawn_duggan on 07/29/2006 6:35 AM Thanks that did the trick. I'll exclude by tabid next time should I need to. Will this issue be present on any page that uses a treeview? Shawn This one is also due to the Ajax being used like in the cute chat posted earlier. The problem most likey comes in when they get a response that has been compressed, because they don't expect it to be compressed. Usually the browser will automatically tell the server if it can handle compression or not (most browsers can). But these Ajax calls work "behind" or "inside" the browser, so any response will have to be handled by them. If the Ajax application makes the call and sets the Accept-Encoding request header correctly it would not get a compressed page, and as Ajax becomes more and more popular they will surely deal with this correctly. I'll bring this up with Jon Henning who does the client api for DotNetNuke, but in the mean time you can exclude any page that has problems like Mariette pointed out.

Shawn

Posts:5

07/29/2006 9:46 PM
Thanks for the replies. The additions to my excludes above did work for a short time. However, after some time I began to experience some problems when logging in as Admin. I would not see the Admin control panel, nor did the pages become editable (i.e. could not see the content panes, etc... it was like I was logged in as a registered user). It knew I was logged in, but I could not do anything. More curious was that I did not have the same issues when logged in as host. It could be that I rarely log in as host and the caching issues (I think its caching) did not have time to manifest. I decided to remove the PageBlaster for now. All problems immediately resolved themselves after deleting all cached content on my server and within my browsers. I may try out the Blowery compression on its own to see if I have the same issues. If I do, I will post back my findings. I think this has real promise and will continue to watch closely. Shawn BlueTango Software http://www.bluetango.ca (I would make a link but link button not working....script errors...I use Firefox...?)

John Mitchell
Posts:3471

07/30/2006 10:34 AM
Hi Shawn, The Snapsis PageBlaster does not currently do any caching when a user is logged in. So I don't think it was the module. The most likely problem if you are using DotNetNuke with not being able to see the admin control panel and other edit controls was probably because you were in "Preview Mode". That is the preview button on the Control Panel. It's easy to forget that you have it on, and it is saved in a cookie so the next time you come back and login you will still be in preview mode. This is stored individually per user that has edit access to the page, so if you logged in as host it would not have been on. Once you cleared cache/cookies on your browser the problem went away. One way to verify if the PageBlaster is causing a problem that doesn't require re-starting your app is to just add an excludePath pattern that excludes everything like this:

Shawn

Posts:5

08/02/2006 7:55 PM
I was not in preview mode. As I stated, once logged in there was no control panel at all. There was no way to get into preview mode. It occurred when logging in as admin, but not as host. I did the whole cookie clearing, cache clearing etc...

John Mitchell
Posts:3471

08/02/2006 8:26 PM
The caching is bypassed when users are logged in so I'm not sure what the problem could have been. If you can re-create it I'll look into it, but I haven't seen this behaviour on any of the sites it's being used on yet.

Shawn

Posts:5

08/03/2006 7:15 PM
Thank you for your replies. I have added it back into my site and so far, so good. Thanks for your help.

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.