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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsDocumentsDocumentsName Name 'IsEditable' is not declared
Previous
 
Next
New Post
3/8/2011 4:56 PM
 
I have a production portal running version 4.9.1 and very unwisely installed the upgrade to the Documents module 4.1.1 over top of my current version 4.1.  Installation appeared to go fine.

Now every existing and new Document Module shows the following error:

Error: Documents is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: E:\DNN\CCPS\DesktopModules\Documents\Document.ascx(10): error BC30451: Name 'IsEditable' is not declared. ---> System.Web.HttpCompileException: E:\DNN\CCPS\DesktopModules\Documents\Document.ascx(10): error BC30451: Name 'IsEditable' is not declared. at System.Web.Compilation.BuildManager.PostProcessFoundBuildResult(BuildResult result, Boolean keyFromVPP, VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode) at System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(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.Compilation.BuildManager.GetVPathBuildResult(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 ---


How can I fix this?  Thank you in advance
 
New Post
3/8/2011 8:00 PM
 
That is very odd since there were only very minor changes between Documents 4.1.0 and 4.1.1 with no change in the markup or code-behind file for Document.ascx that would cause this error. I checked the version compatibility of 4.1.1 and it is still DotNetNuke version 4.6.2 and later.

I am wondering if after downloading the install package for Documents 4.1.1 you had "unblocked" the zip package before installing it. Windows does consider assemblies (dll files) to be potentially dangerous when downloaded from the web and "blocks" them from being used. I would try the following:

1. Download a fresh install package for Documents 4.1.1.
2. After downloading, right click on the package filename or icon then select "Properties" from the context menu.
3. If you see an "Unblock" button, click on it.
4. Although you are probably safe to simply reinstall the now unblocked zip package which should copy over the various Documents module files to your production site without re-rerunning any SQL scripts, I can't recall if DNN 4.9.1 had any issues with a "repair" installation of the same version of a module. Instead I would if you have FTP access to the site perform the following:
4a. On your local system unzip the install package to a folder.
5. FTP the DotNetNuke.Modules.Documents.dll assembly file from the local folder to the production site's /bin folder replacing the file of the same name.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
3/9/2011 8:16 AM
 
Thanks for the quick reply except that it didn't work.  I did exactly as you described to no avail.  Other suggestions?
 
New Post
3/9/2011 11:27 AM
 
I have the same problem. I tried the proposed solution and it didn't work for me either. Please help!
 
New Post
3/9/2011 2:35 PM
 
Daniel --

What version of DotNetNuke is your site running?

I'll try this evening to do an install of Documents 4.1.1 on a DNN 4.x test site and see if I can track down what may be happening - looking at the code I don't see any reason off-hand that this would be failing.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsDocumentsDocumentsName Name 'IsEditable' is not declared


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