 |
|
|
|
I just upgraded to the latest locator. I am recieving the following error when clicking [Locations] when logged in as administrator.
Please advise.
Server Error in '/' Application.
Multiple controls with the same ID 'ctr1315' were found. FindControl requires that controls have unique IDs.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: Multiple controls with the same ID 'ctr1315' were found. FindControl requires that controls have unique IDs.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. |
Stack Trace:
[HttpException (0x80004005): Multiple controls with the same ID 'ctr1315' were found. FindControl requires that controls have unique IDs.]
System.Web.UI.Control.FillNamedControlsTable(Control namingContainer, ControlCollection controls) +220
System.Web.UI.Control.FillNamedControlsTable(Control namingContainer, ControlCollection controls) +280
System.Web.UI.Control.EnsureNamedControlsTable() +57
System.Web.UI.Control.FindControl(String id, Int32 pathOffset) +106
System.Web.UI.Control.FindControl(String id) +9
DotNetNuke.UI.Skins.Skin.Page_Init(Object sender, EventArgs e) +6443
System.Web.UI.Control.OnInit(EventArgs e) +99
System.Web.UI.UserControl.OnInit(EventArgs e) +74
System.Web.UI.Control.InitRecursive(Control namingContainer) +321
System.Web.UI.Control.AddedControl(Control control, Int32 index) +221
System.Web.UI.ControlCollection.Add(Control child) +146
DotNetNuke.Framework.DefaultPage.Page_Init(Object sender, EventArgs e) +1990
System.Web.UI.Control.OnInit(EventArgs e) +99
System.Web.UI.Page.OnInit(EventArgs e) +9
DotNetNuke.Framework.PageBase.OnInit(EventArgs e) +118
System.Web.UI.Control.InitRecursive(Control namingContainer) +321
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +834
[PageLoadException: Multiple controls with the same ID 'ctr1315' were found. FindControl requires that controls have unique IDs.]
DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +377
DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) +484
System.Web.UI.TemplateControl.OnError(EventArgs e) +2085460
System.Web.UI.Page.HandleError(Exception e) +71
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +7341
System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +213
System.Web.UI.Page.ProcessRequest() +86
System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18
System.Web.UI.Page.ProcessRequest(HttpContext context) +49
ASP.default_aspx.ProcessRequest(HttpContext context) +4
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +358
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
|
Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433 |
|
|
|
 | |
|
|
| Re: Error in Edit Locations |
|
|
I'm sorry you experienced this problem. This one slipped past us in the last release, but, fortunately, we know how to fix it and it's a rather easy fix that you can do yourself.
Please see this other forum post where I explain the steps required to fix it.
Let me know if that works for you,
The leading provider of DotNetNuke support, training and custom module development. |
|
|
|
| |
|
|
| Re: Error in Edit Locations |
|
|
Thanks Brian,
I actually took a guess at that last night and chose the right control to remove. Problem resolved.
However, now we are having issues with search and find - it returns no results. And the import I ran didn't seem to import anything.
Please take a look at the list of controls we have and let me know if anything else should be removed. ...crap, how do i attach a screenshot to this post? |
|
|
|
| |
|
|
| Re: Error in Edit Locations |
|
|
Brian,
Can't find a way to email you directly. I would like to send you a screenshot of the controls loaded for this module. Also, I ran the import again and took note of the errors in event viewer:
AssemblyVersion: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
RawURL:
AbsoluteURL:
AbsoluteURLReferrer:
UserAgent:
DefaultDataProvider:
ExceptionGUID:
InnerException: Input string was not in a correct format.
FileName:
FileLineNumber: -1
FileColumnNumber: -1
Method:
StackTrace:
Message: System.FormatException: Input string was not in a correct format. at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at Engage.Dnn.Locator.Components.DataImportScheduler.ParseCSV(FileInfo fileInfo, Int32 startIndex) at Engage.Dnn.Locator.Components.DataImportScheduler.CollectData(FolderInfo folderInfo, Int32 startIndex, Int32 portalId) at Engage.Dnn.Locator.Components.DataImportScheduler.DoWork()
Source:
I can email you the .csv file for review as well.
Thanks. |
|
|
|
| |
|
|
| Re: Error in Edit Locations |
|
|
My email address is bdukes@engagesoftware.com.
The leading provider of DotNetNuke support, training and custom module development. |
|
|
|
| |
|
|
| Re: Error in Edit Locations |
|
|
Thanks Brian,
I also recieved your voice message, thank you for calling back. I've worked through all of the minor issues I was having. The file is successfully imorting now. The only thing that seems amiss is the layout. The results of a search returns the [address/city/state/zip/phone] of each location all bunched up - no spaces. Please take a look and let me know what I can do to fix it: http://corteclean.com/Default.aspx?tabid=708
Regards,
Casey |
|
|
|
| |
|
|
| Re: Error in Edit Locations |
|
|
It looks like the reason that it is different than, for example, the version on the demo site is because your skin is using HTML 4 as the doctype, while we're using an XHTML doctype. Apparently in HTML 4 the spaces that are between those elements aren't recognized.
So, to fix it, assuming that you don't have any plans to change the doctype of your skins, we can use CSS to style those elements a bit more like we expect.
The CSS class for the element surrounding those details is .mdLocationInfo. So, you can apply some padding to each detail element using the following declaration in your portal stylesheet (in the Site Settings page):
.mdLocationInfo span{
padding-right: 1ex;
}
This will add one character-width of space between each address element (address, city, state, zip, phone).
Let me know if that works for you,
The leading provider of DotNetNuke support, training and custom module development. |
|
|
|
| |