DavidWSnow
Posts:162
| | 02/08/2008 9:17 PM |
| I got the menu working correctly. I messed up and left a script tag in the new javascript file. No progress on PageBlaster, still not compressing. BTW in looking at your Exclude from pulldown, maybe that should be a series of checkboxes. You are getting a lot of combinations and permutations. /DaveS | | | |
|
John Mitchell
Posts:2780
| | 02/08/2008 10:10 PM |
| Hi Dave, The Thread was being aborted exception is normal in ASP.Net when you do a redirect and/or end the Response.
DNN used to supress those errors in the viewer, but they stopped doing that recently for some reason. For the PageBlaster test page try it without setting the excludePath. Maybe I have a bug in the None setting when excluding everything. I thought about a checkbox and still may go there, but I wanted to do the more obvious combinations and make it less clicks. This setting also corresponds to the allowed settings in the global config so I wanted to keep continuity since the free version doesn't have a UI. | | | |
|
John Mitchell
Posts:2780
| | 02/08/2008 10:13 PM |
| Hi AllanE,
Thanks for your interest.
Things are getting stable and I'm going to release as soon as I get the Javascript Merging and minification which is almost finished.
I expect to release on Monday. | | | |
|
DavidWSnow
Posts:162
| | 02/09/2008 12:52 PM |
| I was doing some xhtml work on my site using PB V3.0 and it seems as if more than just the caching is intermittant. Sometimes I test the Blog page and there are one error having to do with < /link > not being valid. Another time I have 29 including the "autocomplete=off xhtml bug that is in DNN's search box that I have a rule that takes care of. However if I go to the home page that rule is working. I think that the crazyness may have to do with saving the data. The home page hasen't bee -resaved since there were no changes nor refreshes, while the blog is being refreshed. /Dave | | | |
|
John Mitchell
Posts:2780
| | 02/09/2008 10:28 PM |
| Hi Dave,
I'm doing some debugging step through to make sure that caching is working as expected for several different scenarios now. Empty client cache, empty server cache, after a post-back, when the user manually clears cache, etc.
I have found a bug there, but it is with the new merging of CSS & JS and using a .axd file extension (handled through the Static File Handler). I'm currently working on making sure that all works as expected, so it may clear up some other intermittent cache issues as well. If you can reproduce something that is not working correctly, please let me know the steps involved.
Thanks,
John | | | |
|
DavidWSnow
Posts:162
| | 02/10/2008 1:33 PM |
| While I am not really sure how to test all of the aspects of this module I have seen the following On http://www.agingsafely.com/Help/TestPage/TestWithPB/tabid/974/Default.aspx with ExcPath=.* and EXcFrom = None, YSlow is reporting 7 external css files On http://www.agingsafely.com/Help/TestPage/TestWithPB/tabid/974/Default.aspx with the same exclutions as above W3C valisator is reporting AutoConfig=off even though I have a rule to delete it. Note: that rules IS WORKING for pages I have not messed with with V3! /Dave | | | |
|
lodani dani
Posts:45
| | 02/14/2008 2:41 AM |
| Folks, I'm a little ashamed to ask but ...I cannot find the Portal rules node with the beta 3.0.4  has it been moved somewhere? find attached a screenshot of the module any clue? |
 Attachment: 1214301562971.zip
| | |
|
John Mitchell
Posts:2780
| | 02/14/2008 7:26 AM |
| | The Portal Rules have been moved to their own Admin page. On the main menu Admin > PageBlaster. | | | |
|
John Mitchell
Posts:2780
| | 02/14/2008 10:33 AM |
| There have been some reports of trouble with the new MergeCSS and MergeJS features on some CSS files and JS files.
To disable these features you can use an exclude in your global config like this:
<pathpattern=".*"excludeFrom="MergeCSS"/><pathpattern=".*"excludeFrom="MergeJS"/>
That will exclude those operations on all pages, or you can exclude them on individual pages by putting the module on a page and setting that exclusion in the configuration.
I'll probably be making the optimizations done in these routines a lot less aggressive since there is a lot of badly formatted CSS & JS out there that just can't handle it.
| | | |
|
DavidWSnow
Posts:162
| | 02/14/2008 12:08 PM |
| I installed PB 3.0.4 in my localhost http://dsnow2.dnsalias.com/asi3 and edited the PB.config as requested. The Home Page has ".* exclude from none" There are page replacement rules on this page! It looks very different went logged in. I assume that is what you want Exercised PB enough to be willling to install this on the online system. It might help us exercise and report bugs if we had a better idea of exactly what you expected when looking at YSlow. Not all external JS scripts are merged or minified, even though they are located on the system (I am not surprised that Google Analytics and add-this scripts aren't minimized or concatinated) YSlow shows: (DWS edited after post --- it appears that Active forum ate some the the YSlow text) | [script removed] | [script removed]
This page has 6 external JavaScript files. | | [script removed] | Edited out by DWS | | [script removed] | [script removed]
These components do not have a far future Expires header:
- [script removed]http://s7.addthis.com/css/addthis_widget.css
- [script removed]http://dsnow2.dnsalias.com/ASI3/js/dnncore.js
- [script removed]http://s7.addthis.com/js/addthis_widget.php?v=12
- [script removed]http://dsnow2.dnsalias.com/ASI3/DesktopModules/ListX/xListing.js?v=198
- [script removed]http://www.google-analytics.com/ga.js
- [script removed]http://dsnow2.dnsalias.com/ASI3/Portals/_default/Skins/ASI-skin6/ListX-print.js
- [script removed]http://s7.addthis.com/select/select_load.png?r=0.6204891744262618
- [script removed]http://dsnow2.dnsalias.com/asi3/Portals/0/GrammySnow2.jpg
- [script removed]http://dsnow2.dnsalias.com/asi3/Portals/0/GrammySnow4.jpg
- [script removed]http://dsnow2.dnsalias.com/asi3/Portals/0/section_508.gif
- [script removed]http://dsnow2.dnsalias.com/asi3/Portals/0/pr2.gif
- [script removed]http://dsnow2.dnsalias.com/asi3/Portals/0/valid-xhtml10.png
- [script removed]http://dsnow2.dnsalias.com/asi3/Portals/0/vcss.png
- [script removed]http://s7.addthis.com/button1-bm.gif
- [script removed]http://dsnow2.dnsalias.com/ASI3/images/action_rss.gif
- [script removed]http://dsnow2.dnsalias.com/ASI3/Portals/0/ASI5-logo4.gif
- [script removed]http://www.google-analytics.com/__utm.gif?utmwv=3&utmn=2130686650&utme=&utmcs=UTF-8&utmsr=1440x900&u[snip]
- [script removed]http://dsnow2.dnsalias.com/ASI3/Portals/_default/Skins/ASI-skin6/GradBlue04.png
- [script removed]http://dsnow2.dnsalias.com/ASI3/Portals/_default/Skins/ASI-skin6/GradBlue03.png
- [script removed]http://dsnow2.dnsalias.com/ASI3/Portals/_default/Skins/ASI-skin6/tabs/tab-left.gif
- [script removed]http://dsnow2.dnsalias.com/ASI3/Portals/_default/Skins/ASI-skin6/tabs/tab-right.gif
| | [script removed] | [script removed]
These components are not gzipped:
- [script removed]http://s7.addthis.com/js/addthis_widget.php?v=12
- [script removed]http://s7.addthis.com/css/addthis_widget.css
| | [script removed] | [script removed]
1 external stylesheets were found outside the document HEAD.
- [script removed]http://s7.addthis.com/css/addthis_widget.css
| | [script removed] | [script removed] | | [script removed] | [script removed] | | [script removed] | [script removed]
Only consider this if your property is a common user home page. | | [script removed] | [script removed] | | [script removed] | [script removed]
The following JavaScript files do not appear to be obfuscated nor minified.
- [script removed]http://dsnow2.dnsalias.com/ASI3/js/dnncore.js
- [script removed]http://dsnow2.dnsalias.com/ASI3/DesktopModules/ListX/xListing.js?v=198
- [script removed]http://dsnow2.dnsalias.com/ASI3/Portals/_default/Skins/ASI-skin6/ListX-print.js
| | [script removed] | [script removed] | | [script removed] | [script removed] | | [script removed] | [script removed] |
| | | |
|
DavidWSnow
Posts:162
| | 02/14/2008 12:21 PM |
| From your email: "I have made all the optimizations that can be made to my site and I’m proud to say I now have an ‘A’ (90) on my report card. To get a score that high you need to have your images processed by the static file handler in PageBlaster, but even without having images processed you’ll see big improvements in performance." How does one "have your images processed by the static file handler in PageBlaster?" I don't see any such option. /DaveS | | | |
|
John Mitchell
Posts:2780
| | 02/14/2008 12:48 PM |
| Thanks for asking Dave. On the first question, the reason that some JS does not have the optimizations applied (especially when logged in) is because the JS is not in the Head section of the page. Only JS links from the head section are merged & optimized, and then moved to the bottom of the page. I'm currently working on some replacement rules that will move JS from the page up into the head before the other process runs so that you can control which other files get added to that process. Another reason is that the .JS and .CSS extensions do not get sent to ASP.Net by default in IIS. Which leads into the second question. For the StaticFileHandler, I showed how to set that up earlier in this thread. You will need to configure IIS to send .gif, .png, .jpg, .css, .js etc. to ASP.Net, and then you will need to add those extensions to the StaticFileHandler declaration in the httpHandlers section of the Web.Config to send them through PageBlaster. I'll look at the problem with setting Exclude "everything" to None on an individual page now, but you really should never need to use an option like that. Leaving the exclusion blank does the same thing. You should only use the exclude path on a specific page if you want to keep it from doing something, not to enable it to do something. | | | |
|
DavidWSnow
Posts:162
| | 02/14/2008 12:52 PM |
| The reason that my pages are setup with ExcPath = .* and ExcFrom = None is that when testing or working on the pages I set the path and exclude from all. When I am done I only switch the pulldown. Lazy I guess, but efficient in key strokes ;=} The StaticFileHandler setup would be unwise for me. If I have to disable PB for some reason I don't want to have to require my ISP to make a bunch of changes. I'll have to look closer into the Plesk Control Panel and see if I have the power to make these changes. /Dave | | | |
|
John Mitchell
Posts:2780
| | 02/14/2008 1:03 PM |
| So you are setting the global config file to exclude everything? And then trying to turn some pages back on by setting the exclusion to None? I guess I can see why you would try to do that since the module does have that option, but I'm thinking that I probably need to remove that as an option then because if everything is excluded at the host level, then I probably should not allow individual pages to turn it back on. Hmm, that may not be good either. I guess some people might want to do what you are doing and just enable PageBlaster on select pages.
I used to have a complete config section just for "IncludePaths" that would do this, but I found that it was hardly ever needed since you have the ability to do negative patterns in the exclude. I'll have to give this one some thought, but for now I'll see why setting Exclude everything from Nothing isn't working. | | | |
|
allane
Posts:9
| | 02/14/2008 2:09 PM |
| John, I have an urgent problem. Just tried to uninstall the beta...the entire site crashed and is currently unavailable. It looks as though PageBlaster isn't completely removed from web.config nor is Snapsis.PageBlaster.config removed from the root. Could you please tell me what to do? Here's a copy of the error that I get when visiting my site: | | | |
|
John Mitchell
Posts:2780
| | 02/14/2008 2:13 PM |
| If you uninstall the module then you will also need to modify the web.config to remove the declarations.
Remove or comment out these two lines in web.config <addname="PageBlaster"type="Snapsis.HttpModules.PageBlaster.PageBlasterModule, Snapsis.HttpModules.PageBlaster"/><addverb="*"path="*.css,*.js,*.gif,*.jpg"type="Snapsis.HttpModules.PageBlaster.StaticFileHandler,
Snapsis.HttpModules.PageBlaster"/> | | | |
|
John Mitchell
Posts:2780
| | 02/14/2008 2:20 PM |
| Dave,
I tracked down the reason you can't exclude everything globally and then try to enable it again by page.
This is because if you exclude from All in the global, the filter to process everything else is not attached.
You could do it by excluding a widcard pattern on seperate lines like this:
<pathpattern=".*"excludeFrom="CompressionAndCaching"/><pathpattern=".*"excludeFrom="Replacements"/><pathpattern=".*"excludeFrom="MergeCSSAndJS"/>
| | | |
|
allane
Posts:9
| | 02/14/2008 2:25 PM |
| It worked. Thanks. Guess I should have figured that one out myself , but I was affraid that more than the web.config was "left behind". I'm all new to PB and look forward to work more with it. Looks really great. | | | |
|
John Mitchell
Posts:2780
| | 02/14/2008 2:38 PM |
| Was there a problem that made you need to uninstall the module? If so please let me know and I'll try to make the module work better in that situation.
Also, an alternative to uninstalling the module it to just put an exclude pattern in the Snapsis.PageBlaster.config file that looks like this:
<pathpattern=".*"excludeFrom="All"/>
This will make everything in the module be bypassed without having to uninstall or change the web.config.
| | | |
|
allane
Posts:9
| | 02/14/2008 2:49 PM |
| No, there was no problem at all. I'm currently working on a new version of my site (DNN-based this time), and I need to concentrate on getting ready to "open the gates" for a group of beta-testers. I have to get concentrate the work on the basic features, before having fun with PB. Chose to uninstall it to be sure, that PB doesn't interfere when debugging the various features of the site. Using the exclude pattern is what I need. Wasn't sure how to do it. Thanks! | | | |
|