Hi Sravana,

Can you send me the code for the module you are trying to page? I can see there is definitely a problem but it would help greatly if I could take a look at the code.

Do the modules function properly when they are placed outside of the Aggregator?

Please send any code directly to me (support at dnnstuff.com)

Richard

Hi Sravana,

Thanks for the heads up. There were a couple of other users who reported a similar problem but I hadn't been able to reproduce it until now. I'll get on this and let you know as soon as I find out what the problem is.

It seems that if the module is on the last tab, it works fine but if it's on any other tab it won't work. This all worked fine in the DNN2 version because I use multiple paged grids within the Aggregator all of the time.

Thanks again,

Richard

Well, I took a look at this and it's a weird one. The only way I could get it to work consistently was to rebind the datagrid on each load. I know that's not the 'accepted' way to code the datagrid but it seems to be a 'work around' for now.

On my journey today I came across this page http://west-wind.com/weblog/posts/211.aspx . There seem to be lots of issues regarding the datagrid events not firing so it doesn't really surprise me that something might not work as expected in the Aggregator. By putting the modules into the Aggregator, we're introducing another level of container around the module and this might be causing the problem. Perhaps there is a maximum number of container levels that cause the events not to bubble up. I'm not sure.

I am sure though that I'm injecting the modules the exact same way that the DNN framework does. In fact I'm using the very same method that the framework uses, InjectModule within the Skins namespace.

I'll continue to look into this and see if there is something else that can be done.

Richard