Hi,

I upgraded to 5.0 which has really good new features, thx.

But unfortunatly in the detail of a blog entry there are the combo boxes for adding Blog Part are shown.

 see: http://www.woax-it.com/news/entryid/1...

How can they be removed? (I miss also the "update content button")

thx and best regards

thx chris for info, I will look at this.

 Meanwhile I found there are log DB Exceptions:

AssemblyVersion: 6.2.2

PortalID: 0

PortalName: WoAx-IT Software Solutions

UserID: 1

UserName: servfoko

ActiveTabID: 98

ActiveTabName: News

RawURL: /news/ctl/edit_blog/blogid/1/mid/430

AbsoluteURL: /Default.aspx

AbsoluteURLReferrer: http://www.woax-it.com/news/ctl/edit_blog/blogid/1/mid/430

UserAgent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1

DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider

ExceptionGUID: ff6fffe5-3c5b-4cc0-84fc-500a1bddc3fb

InnerException: TotalRecords

FileName:

FileLineNumber: 0

FileColumnNumber: 0

Method: System.Data.ProviderBase.FieldNameLookup.GetOrdinal

StackTrace:

Message: System.IndexOutOfRangeException: TotalRecords bei System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName) bei System.Data.SqlClient.SqlDataReader.GetOrdinal(String name) bei System.Data.SqlClient.SqlDataReader.get_Item(String name) bei DotNetNuke.Modules.Blog.Components.Entities.EntryInfo.Fill(IDataReader dr) bei DotNetNuke.Common.Utilities.CBO.FillObjectFromReader(Object objObject, IDataReader dr)

Source:

Any ideas which can cause this?

best regards

The first error, related to Total Records, isn't a problem (it needs to be corrected eventually but doesn't actually cause an error the user sees), we have the same one here on dnn.com. The qaplaceholder error is caused because the javascript for it isn't being loaded. It's not being loaded for another reason, which I assume has something to do w/ your skin or other modules on the page. If you change the skin on that page to a core one, does the problem still happen? If not, then remove other modules from the page at that time and see if it still happens. At that point, using Dark Knight and no other modules, then it would be a blog problem.