Quick Nav:  Online Store   |   Login | Register

NukeAlert OptIn Module

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.
AuthorMessages
SAD5643
<20 Posts
Posts:13


06/29/2008 2:35 AM  

John

I have loaded the Onyak NukeAlert Opt-In module.  The module contains a control for managing the emailing lists.  When I access the control page the buttons disappear (they become white on white).

If I disable PageBlaster for the complete site by using ".*" in the config file the page loads correctly.  I have tried to configure PageBlaser to exclude the page but I have had no success.  I used tabid=138 to isolate the page with no luck.  I  tried adding the control name to the pattern that came in the in the default file with no luck.  I installed the PB module on the page and used the pattern ".*" with no luck.

I would appreciate if you could take a look and advise.

As the page is not public on the site can you advise an email where I can provide you with access to the page.

Thanks

 

John Mitchell
Posts:3352


06/29/2008 8:26 AM  
It sounds like an issue with CSS. You can probably get it excluded by using the folder name of the module in your exclude pattern.
Something like:

< path pattern="NukeAlert" excludeFrom="CSSMerge" />

Or

< path pattern="NukeAlert" excludeFrom="All" />

If needed, you can contact me privately by using the Message icon under my user name here in the forums.
John Mitchell
Posts:3352


06/30/2008 8:41 AM  

Hi Stephen,
I checked out the page in question, and it looks like those modules are pulling additional resources from WebResource.axd

Try excluding WebResource from All instead of NukeOptIn or NukeViewer to see if it corrects the problem for that.

< path pattern="WebResource " excludeFrom="All" />

You also asked about merging more JS and CSS files into the single merged file.
PageBlaster on merges the JS & CSS files that are linked in the Head section, so if you want to merge others that are listed in the page then you will need to move those links to the head. 

There are examples of moving the JS file links to the head in the Snapsis.PageBlaster.config file.
Thos examples only move them when the user is not logged in, but you probably don't need to have that condition.

SAD5643
<20 Posts
Posts:13


07/14/2008 8:40 AM  

John

You solution resolved one issue with NukeAlert but I also discovered a conflict between Catalook and NukeAlert that occurs without PB.  I am working with Onyaktech to hopefully find a solution.

SAD5643
<20 Posts
Posts:13


07/17/2008 7:34 AM  

A couple of further questions.

1.  If I use the WebResource pattern it applies it to the whole site.  Is it possible to apply it to one page only.  If I exclude using tabid to identify the page I still have the conflict with Webesource with the modules on that page?

2. In regards to moving the other js, I am not logged in and the replacement rules do not appear to be moving js.  Should I be expecting a single js file.  I still get about 10 js files such as spmenu.js, dtree.js, popupcalendar.js to list a few.  Can these be merged?

 

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.
Forums >Snapsis Product Support >PageBlaster > NukeAlert OptIn Module



ActiveForums 3.7
Powered by: Snapsis Software