Version 3.0 Beta Test FeedBack

Hi John,

I started testing PageBlaster v3 Beta and have some issues would like to report.

Module Version: Snapsis.DNN.PageBlaster_3.0.0_Install.zip

Test Instance: DotNetNuke v4.8 with Full Trust Local Environment Hosted on Windows Server 2003 SP1

DNN is running fine.

First i installed Snapsis.DNN.PageBlaster_3.0.0_Install.zip file via Host > Module Definitions.

Then i checked existing installation guides for 2.0 version of Page Blaster and they were pointing me to add

*add name="PageBlaster" type="Snapsis.HttpModules.PageBlaster.PageBlasterModule, Snapsis.HttpModules.PageBlaster" /* (replace * with < and >

to HTTPModules section on web.config file.

If i add this to my web.config i receive following error while browsing my local website.

[ArgumentException: Empty path name is not legal.]
   System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32

Am i doing something wrong? Any suggestions are welcome :)

One enhancement of this version is that it automatically updates the web.config and copies a default Snapsis.PageBlaster.config file to the root of the website.
If the Snapsis.PageBlaster.config was already in the root, then it wouldn't have copied it.

The problem you are describing is probably because the Snapsis.PageBlaster.config file does not have a trace node:

trace level="Header" file-path="/PageBlaster.trace.config" /

Look in the DesktopModules/Snapsis/PageBlaster/Config folder to compare the default one with the one in your website's root folder.

Also new is the "Header" value for trace level. This allows you to turn off the PageBlaster response header if you wish by setting it to "None".

Let me know how you were setup before you installed PageBlaster. If it was a new install, or if the Snapsis.PageBlaster.config was already there.
Maybe I have a problem in the way it upgrades.

hi,

i have installed pageblaster 3 in dnn 4.8. before i uninstall pageblaster 2.x. i delete the old snapsis. pageblaster config.

i had to manually set the add key parameter in web-config, because there was an old entry which was disabled.

most things should work, but my portal rules didn´t work. i have the feeling that none rule works. same for basic rules like white space filter in config.

thanks jens

hi john,

yes i do the uncoment. and the rules didn´t work. i can see the rules in pageblaster admin.

i do a complete new install of pageblaster 3 now. and i tested it now. i will post results later here.

jens

i think the same problem.

i will place a module pb3 and then i will see

jens

omly when i place a pb3 module in non admin mode to page with page rules the portals rules seems to be work.

when a pb3 module is in admin only mode the page rules and portal rules didn´t work.

jens

Hi Jens,
I will look into this right away.
Thanks for the feedback.

in first installations the saved rules are not shown. after i make a click on folder icon the rules are there.

when i open pb3 next time the rules are invisable as long as i dind´t click the folder icon.

jens

hi,

an other question? is pb3 feature complete?

jens

I just sent a new build to everyone.

For those who haven't seen it yet, there is a description of the new Conditional Rules syntax in this thread:

http://www.snapsis.com/PageBlaster-Support/tabid/601/forumid/9/postid/7958/view/topic/301-Redirect-feature-for-PageBlaster.aspx

While I was testing yesterday I noticed that it is not such a good idea to search for a period when doing a 301 redirect response.
The reason is that if your condition is not matched then it replaces everything with nothing.

A better way to implement it is to search for something that is known to be in the output and on the Respond - Replace with part of the rule you can include an else condition that just replaces what was searched for.  Here is an example of what I mean.

I had some difficulty geeting your previous example of 301 to work. Even when I kept the snapsis urls, which should have made this a no-operation it clobered my whole localhost site! Needles to say I have to get this to work locally before I place it on my primary server.  I'll try the new one today Monday.

/DaveS

I just re-read your post and I think maybe there is a misconception that can easily happen here.

The Conditional Rule (using an IF function) makes the true condition or the false condition part available to the part of the Rule it is used in. 
So if the Condition is placed in the Respond - Replace With part of the Rule it is actually changing what the Rule Replaces or Responds With.  
In the case of Searching for a period, that matched every character in the output. Since there was a match on the Search For part of the rule  the Replace-Respond part is then executed. After the condition did not match the Replace - Respond part of the rule didn't have anything left to use a replacement for the period, so it caused the rule to replace all characters with nothing.

To summarize, the Search For and Replace With parts of the Rule are still executed as if they were just a normal search and replace. 
By adding the condition it allows the search for and replace with fields to change before being executed depending on the request or other input.

I'll be showing more examples to demonstrate how powerful this can be.