DotNetNuke "Upload Custom Module" command sometimes does nothing.

I've noticed a few times that when in DotNetNuke 4. "Upload Custom Module" page I had a custom module in the list, “upload new file“ link does nothing instead of importing module.

It seems related to caching issue (see problem here). I suspect that even if the file is shown in the list, it still not in cache.

It will be more reliable to check list control directly instead of cache. And why the list to upload should be saved to cache? 

Additionally even if the list is empty, it is better to report about it to the user instead of silently return to module list.

The issue has been reported to DNN Support

The workaround is described here

  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati
posted @ Monday, February 20, 2006 8:55 AM
Print

Comments on this entry:

# re: DotNetNuke "Upload Custom Module" command sometimes does nothing.

Left by Michael Freidgeim at 7/15/2007 10:54 PM
Gravatar
The problem fixed in DNN (4.3.3) Release

Your comment:



(not displayed)


 
 
 
 
 

Live Comment Preview:

 
«February»
SunMonTueWedThuFriSat
2930311234
567891011
12131415161718
19202122232425
26272829123
45678910