This is very weird.

I have a custom module which I have altered to include some DevExpress web components. If I run the module on my local dev site, it works fine, but when I upload the module to the live web site, none of the DevExpress components seem to work i.e. I have an aspxDropDownList control which fires the textchanged event which assigns a value and reloads the page.

This doesn't seem to be working and also the aspxgrid is not working.

However,

I have another custom module which uses the same components and this one is working fine on the live site.

Any ideas?

Regards

Mike

Hi,

I could find anything wrong. What I did to get around it was to create a new module, copy and pasted the code from the old module, uploaded it and guess what. It works!

This is not the first time this has happened and I would really like to know what causes this. I have spent 2 days on this issue.

The original module was created in 4.0.3 but I other modules (created in 4.0.3) that are working perfectly fine. Could it be folder permissions on the "Live" web site?

Mike

Interesting. The DNN file did have the cache timeout set to 60. I took it out of the module settings and it didn't seem to make any difference. I didn't look at the page cache settings and I didn't take the caching setting out of the dll.

This would make sense though as this is the only module that I had (some days ago) been playing with the caching.

Why would caching stop the events from working though? Does DNN intercept them and turn them off?

The modules are all in VB.NET