Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Event Handler doesnEvent Handler doesn't get called
Previous
 
Next
New Post
12/10/2008 8:07 PM
 

I have a default DNN installation and I'm working on my first module so there is nothing fancy getting in the way (Javascript, validators, etc).

I have a module that has a control that renders a datalist and that datalist has linkbuttons that use the OnCommand handler.  When I click on a link it should call my handler which does a NavigateURL to another control.

When I go to the module, the datalist always renders correctly but when I click on a link button the event isn't fired.  In fact the Page_Load isn't even called at all.  The strange part is that if I wait 60 seconds and then click on a link then it will call Page_Load and my event handler and it will go to the page I want it to.

I read a lot of posts and tried setting causesValidation="false" but that didn't help.  There has been a lot of talk about enablePostBack as well but that doesn't appear to be a problem because 1) It does display the datalist and linkButtons correctly and 2) if I wait long enough it will work.

To be clear, this is not a case where you click on it and then wait 60 seconds for the response, rather a click won't have the desired effect unless you have been at the page for 60 seconds.  Man, I feel crazy just posting this but I swear that is what is happening :)

Any ideas?

Thanks

 
New Post
12/10/2008 10:14 PM
 

And I bet that if you are logged in with edit permission on the module it is working properly . . . If that is case, be sure to set the Cache Time in the module settings to 0 to disable module output caching.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
12/11/2008 12:19 PM
 

Thanks William!  That was the problem.

So with the caching on, all postbacks won't work?  Seems like the caching would hardly ever be a benifit in this case then.  I'm sure I'm missing something here.  When would the output caching be useful?  Maybe if my module was coded a certain way it would lend itself to caching?  Is there a resource you could point me to?

Thanks again!

Peter

 
New Post
12/11/2008 3:44 PM
 

Output (module) caching is a benefit when the content is static such as for the Html module (but not when token replacement is enabled). It cannot be used for interactive modules as a module's controls must be able to trigger postbacks.

Instead of using built in module output caching, you can use the DNN DataCache object's methods to selectively cache data, fragments of generated HTML, extensive custom settings, etc. to avoid multiple hits to the database or lengthy recalculations.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Event Handler doesnEvent Handler doesn't get called


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out