Like many in other threads here, I'm having the issue where if user comments are turned on (at the parent/child blog level or for the individual blog post) the blog entry cannot be read by clicking on the blog title or the "read more" link. The errors in the event viewer were the same as are being reported in other posts:
ModuleId: 673
ModuleDefId: 105
FriendlyName: Recent Blog Entries
ModuleControlSource: DesktopModules/Blog/MainView.ascx
AssemblyVersion: 04.09.01
PortalID: 1
PortalName: ScotBecker.com
UserID: 10
UserName: Scot
ActiveTabID: 121
ActiveTabName: Blog
RawURL: /Blog/tabid/121/EntryId/107/test.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.scotbecker.com/Blog/tabid/121/BlogID/28/Default.aspx
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 1a96ecf0-16f3-4fad-b038-c01494be739a
InnerException: Value cannot be null. Parameter name: format
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.String.format
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Value cannot be null. Parameter name: format ---> System.ArgumentNullException: Value cannot be null. Parameter name: format at System.String.format(IformatProvider provider, String format, Object[] args) at DotNetNuke.Modules.Blog.ViewEntry.BindCommentsList() at DotNetNuke.Modules.Blog.ViewEntry.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---
Source:
Server Name: DEDI379
AssemblyVersion: 04.09.01
PortalID: 1
PortalName: ScotBecker.com
UserID: 10
UserName: Scot
ActiveTabID: 121
ActiveTabName: Blog
RawURL: /Blog/tabid/121/EntryId/107/test.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.scotbecker.com/Blog/tabid/121/BlogID/28/Default.aspx
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 972021d1-33bc-4d05-b150-bdc43eca25d1
InnerException: The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>).
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.UI.ControlCollection.Add
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>). ---> System.Web.HttpException: The Controls collection cannot be modified because the control contains code blocks (i.e. <% ... %>). at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, PortalModuleBase ctrlModule, Exception exc, Boolean DisplayErrorMessage) --- End of inner exception stack trace ---
Source:
Server Name: DEDI379
... and the page refreshes to: http://www.scotbecker.com/Default.aspx?tabid=121&def=ErrorMessage
which just shows the blog listing and not the individual post.
One interesting item to note is that when I select the drop down to get to the module options from this page, there are two new items in the menu, both with blank text. One accesses the blog settings and the other creates a new blog entry.
Also, the module options for the blog view component have only about half of the labels present. For example, none of the labels in the vertical section show up. I can provide screen shots if that would be of any use.
Other suggestions in the various threads (e.g. making sure all connection strings pointed to the right DB, incorrect image paths, et al.) were not applicable to me.
I can reproduce this at will. Currently, all blogs have comments turned off. If I make a new post and select "Allow users to comment on this entry (overrides Blog Setting) " prior to posting I will not be able to read the post and the above errors will get thrown.
In my case, I upgraded from DNN 03.02.02 to 04.09.01 and then upgraded to blog version 03.05.01. I don't know if this problem manifested itself after the DNN upgrade or after the component upgrade. I'm currently hosting 3 portals on this installation. Each portal has a single parent blog. One has no child blogs but the other two do. All blogs are on pages viewable by everyone (e.g. none are on private/restricted pages). All three portals exhibit the same behavior described above.