Upgrade Gallery 3.x to 4.3 issue with Basic Path


The Basic Path setting in the Gallery settings of Gallery 3.x needs to begin with a backslash (). This backshlash is already set by the module or core, so you get a linked path like this samble:
...\Gallery\651 but it have to be ...\Gallery\651 .
Simple fix is to change this setting manuell in the Gallery setting and delete the first backslash in the Basic Path setting.
A Code fix can be to check if the value of the basic path setting begins with a backshalsh and delete it if it exist.
The event log for this issue looks like the following:
ModuleId: 427
ModuleDefId: 127
FriendlyName: Bildergalerie
ModuleControlSource: DesktopModules/Gallery/Container.ascx
AssemblyVersion: 5.2.2
PortalID: 0
PortalName: Moonlightradio.net
UserID: 1
UserName: host
ActiveTabID: 65
ActiveTabName: Bildergallerie
RawURL: /Service/Bildergallerie/tabid/65/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.moonlightradio.net/Service/Bildergallerie/tabid/65/ctl/Login/Default.aspx?returnurl=%2fService%2fBildergallerie%2ftabid%2f65%2fDefault.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.2)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 4358e647-a68e-4d3e-97e7-4289a05c8fd0
InnerException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Modules.Gallery.Container.GetStats
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt. ---> System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt. bei DotNetNuke.Modules.Gallery.Container.GetStats() bei DotNetNuke.Modules.Gallery.Container.Page_Load(Object sender, EventArgs e) --- Ende der internen Ausnahmestapelüberwachung ---


imagemaker wrote Mar 21, 2011 at 12:14 AM

This issue was fixed in v 4.03.03 but not marked as fixed.

wrote Feb 14, 2013 at 7:01 PM

wrote May 16, 2013 at 9:09 AM

wrote May 16, 2013 at 9:09 AM

wrote Jun 14, 2013 at 7:06 AM