Forums

 
  Support Forum  Modules  Engage: Publish  Manage Content is temporarily unavailable
Previous Previous
 
Next Next
New Post 5/28/2008 2:36 AM
  ahmet.cetin
17 posts
10th Level Poster


Manage Content is temporarily unavailable 

 

When I was trying to add a new article, I've started to get this error:

DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Engage.Dnn.Publish.Item.SendStatusUpdateEmail() at Engage.Dnn.Publish.Item.UpdateApprovalStatus(IDbTransaction trans) at Engage.Dnn.Publish.Article.Save(Int32 authorId) at Engage.Dnn.Publish.ArticleControls.ArticleEdit.cmdUpdate_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

I had three Publish module in one page showing three different categories, I've added one article to one of them and selected to show in the same page. I saw that the article shown in all three modules. Therefore I've created three pages and moved the modules to the corresponding pages. Then I've tried to add an article to one category, I've started to get the above error. Now, whatever I want to save in content (edit another article in another category/page or add/edit category), when I try yo save, I get the above error always. I've tried to add article with another user login but it didn't help.

Cheers,

Ahmet Cetin

 
New Post 5/28/2008 9:09 AM
  Chris Hammond
1117 posts
1st Level Poster


Re: Manage Content is temporarily unavailable 

The first thing i would do is to try and see if you can just disable approval emails for now, on the manage content page click on the Settings icon, from there uncheck the "Send Email Notification" option, then try adding an article. Let me know if that works, if so we can try to track down where this error may be coming from.

As for having 3 modules on one page, what you'll want to do is only have one of those on the page marked as "Overrideable" in the module settings, by default all modules are overrideable, so you'll have to edit the settings for two of them and turn that off.

Let me know if that clears up some of the issues,

Chris

 


Directory of Training Programs, DotNetNuke Corporation
 
New Post 5/29/2008 1:35 AM
  ahmet.cetin
17 posts
10th Level Poster


Re: Manage Content is temporarily unavailable 
Modified By ahmet.cetin  on 5/29/2008 1:37:29 AM)

Send Email Notification option was already turned off, and still I have the error. I'm using Publish in two portals at the same dnn installation, in one of them it works without a problem, in the other one I have this error. The strange thing is, I was entering the articles without a problem until I moved the two modules from that page I described above to the new pages. Then I've started to get the error. It might be coincidence.

If you send me your email address, I can open an admin account for you to check the site.

Cheers,

Ahmet

 
New Post 5/29/2008 9:51 AM
  Chris Hammond
1117 posts
1st Level Poster


Re: Manage Content is temporarily unavailable 

You can email me with chammond -at- engagesoftware.com


Directory of Training Programs, DotNetNuke Corporation
 
New Post 1/15/2010 1:31 PM
  bharman
1 posts
No Ranking


Re: Manage Content is temporarily unavailable 

Chris,

We too are experiencing 3 similar errors.  When we attempt to add a new article, we get this error:

Error: Manage Content is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Engage.Dnn.Publish.Item.SendStatusUpdateEmail() at Engage.Dnn.Publish.Item.UpdateApprovalStatus(IDbTransaction trans) at Engage.Dnn.Publish.Article.Save(Int32 authorId) at Engage.Dnn.Publish.ArticleControls.ArticleEdit.cmdUpdate_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

We have the SMTP setting disabled and, when adding the article, we uncheck the "Use Approval Status for this article" option.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

When we click the "edit" menu option of the News, it displays a list with links to Articles, Categories, Settings, Admin Tools, and Delete Item.  At the bottom of this page an error displays stating:

Unhandled error loading module.
DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to contentpane ---> System.ArgumentNullException: Value cannot be null. Parameter name: virtualPath at System.Web.VirtualPath.Create(String virtualPath, VirtualPathOptions options) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at Engage.Dnn.Publish.AdminLoader.LoadControlType() at Engage.Dnn.Publish.AdminLoader.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

After displaying the list above, we click the Articles option.  On the subsequent article filter screen, we pick Approved Articles and the list of articled displays.  We click the Edit link for one of the existing articles, make a change, and receive the following when we attempt to save:

Error: Manage Content is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Engage.Dnn.Publish.Item.SendStatusUpdateEmail() at Engage.Dnn.Publish.Item.UpdateApprovalStatus(IDbTransaction trans) at Engage.Dnn.Publish.Article.Save(Int32 authorId) at Engage.Dnn.Publish.ArticleControls.ArticleEdit.cmdUpdate_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

 

Any ideas?

 

 

 

 

 
Previous Previous
 
Next Next
  Support Forum  Modules  Engage: Publish  Manage Content is temporarily unavailable

Purchase

Please click here to buy now.
Payment will be processed via credit card or PayPal.

Please click here to buy now.
Payment will be processed via credit card or PayPal.

Test Drive!

Want to find out how it works? Visit our demo site to see the modules in actions!

Want to find out how it works? Visit our demo site to see the modules in actions!

Subscribe

Sign up for our newsletter and get the latest product updates!

Sign up for our newsletter and get the latest product updates!

Online Support

Powered by DotNetNuke