Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

DotNetNuke Marketplace
  Need Help?  
Professional technical support for DotNetNuke is available from DotNetNuke Corporation.
 


  Ads  
 


  Sponsors  

Meet Our Sponsors

DataSprings - Great Ideas. Always Flowing.
R2integrated - formerly bi4ce
Jango Studios - Skins, Modules and Hosting for DotNetNuke
eUKhost.com is commited to offer exceptional UK Windows Web Hosting solutions with quality 24x7 technical support.Our plans support ASP.Net, ASP, ASP.NET Ajax extensions, XML, MSSQL, MySQL, PHP,DNN, multiple domains and Shared SSL as standard.
SmarterTools
The Official Microsoft ASP.NET Website
 


DotNetNuke Forums
 
  Forum  DotNetNuke® Pro...  Documents Modul...  Upgrade to 4.0.0 failed
Previous Previous
 
Next Next
New Post 4/8/2008 11:23 AM
Unresolved
User is offline Thomas Jensen
11 posts
10th Ranked


Upgrade to 4.0.0 failed 

I use DNN 04.03.04

I have upgraded my document module to 4.0.0, but can't load the module get the following message:

 

Unhandled error loading module.
DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to ContentPane ---> DotNetNuke.Services.Exceptions.ModuleLoadException: Error: Test is currently unavailable. ---> System.Web.HttpCompileException: d:\web\kos-sejlsport.dk\www\DotNetNuke\DesktopModules\Documents\Document.ascx(10): error BC30451: Name 'IsEditable' is not declared. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace --- at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, PortalModuleBase ctrlModule, Exception exc, Boolean DisplayErrorMessage) at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(PortalModuleBase ctrlModule, Exception exc) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace

Any ideas what is wrong, I'm a newbie ;-)

Thomas

 
New Post 4/8/2008 11:24 AM
Online now... Chris Hammond
2795 posts
engagesoftware.com
5th Ranked








Re: Upgrade to 4.0.0 failed 

The new Documents module requires DNN 4.5.2 or greater


Chris Hammond
Engage Software
St. Louis, MO
314.966.4000


The leading provider of DotNetNuke skinning, training and custom module development.
Official DotNetNuke® Training Provider
 
New Post 4/10/2008 7:44 AM
User is offline Thomas Jensen
11 posts
10th Ranked


Re: Upgrade to 4.0.0 failed 

Thanks for the answer

How do I downgrade. When I try uploading version 03.03.08 it says it's an old version

 
New Post 4/10/2008 11:32 AM
User is offline Mitch Sellers
5575 posts
www.mitchelsellers.com
3rd Ranked




Re: Upgrade to 4.0.0 failed 

Downgrades are not supported by DotNetNuke.

The best method would be to restore the site to the point prior to installing the new version of the module.


-Mitchel Sellers
MCITP, MCPD, MCTS
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Consulting Quotes, and DNN Technical Support Services

I reccomend 3Essentials for shared hosting and BaseCamp for project management
 
New Post 4/28/2008 6:27 AM
User is offline levinethemachine
82 posts
10th Ranked


Re: Upgrade to 4.0.0 failed 

OK.

Here is my problem with this.

When you go in as HOST and you look at the module definitions--the icon next to the documents module reads "UPGRADE AVAILABLE". 

So if you upgrade, and you are pre-whatever--the docments module is toast and because there was no README, or any warning, or any pre-requisite check or safeguard of any kind--a site restore has to be performed? No simple way to back out a change? Sorry...that's not even good quality software.

If it doesn't affect anything else-I would eschew the documents module completely and use something else.

 
Previous Previous
 
Next Next
  Forum  DotNetNuke® Pro...  Documents Modul...  Upgrade to 4.0.0 failed
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

 


Integral Hosting | DNN only $14.95/month
Experienced .NET hosting on Windows 2003, ASP.NET 1.1 & 2.0, MSSQL with real technical support.
www.integralhosting.com
Aricie
Aricie is one of the French pioneers and experts in DotNetNuke technology.
www.aricie.com
AFUEGO!
Looking for Free DNN Hosting?
www.AFUEGO.com

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP