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.0Intermodule Comms - problem.Intermodule Comms - problem.
Previous
 
Next
New Post
2/13/2007 4:12 PM
 
I originally posted this to the wrong area (Config) by mistake so I'll have another go here.

I've created two basic modules on the same page. ModuleTx has a textbox and button,  ModuleRx has a textbox only.

Type something in ModuleTx's textbox, click the button and via ICM the text appears in the text box of ModuleRx. Great. Except it only works if I'm logged on as "host". As soon as I try this as logged on as a registered user the button click event isn't firing and hence the ModuleCommunication event doesn't get fired.

Anyone come across this ? Any idea what the problem is and how to get around it ?

We are using DNN 4.4.1 and I've enabled the site for AJAX.

Regards
Scott
 
New Post
2/13/2007 9:12 PM
 
OK I forgot to mention that I'd used the "DotNetNuke Dynamic Module" template to create these modules. I created new modules from scratch with only the controls I needed and the code that the controls needed. The button click event always fires now and hence the ICM always works. I've no idea what causes the problem with the template generated modules but from now on I won't be using them and in fact I'm going to uninstall them right now.

Regards
Scott
 
New Post
2/14/2007 2:31 AM
 

Could be the module caching... I am not sure if it's enabled by default for the Dynmic modules in their .dnn file, but if it is your events wouldn't get fired and they would work if you were logged in as admin or host.

Anyway.... glad you made it work :)

 


Thanks,
Vladan Strigo
NETMedia

My website: Vladan.Strigo.NET

Vladan.Strigo.NET: Projects
* Advanced VS2005 development approach - BlankModule
* DNN & Microsoft Ajax best practices guidance

Vladan.Strigo.NET: Resources
* Comprehensive list of DNN 4 Module development resources

 
New Post
2/14/2007 5:23 AM
 
I have had the same problem..set the modules caching (in module settings) to 0 and you'll be fine
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Intermodule Comms - problem.Intermodule Comms - problem.


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