This is a very useful package, but after installing it, we began getting the following error when attempting to subscribe to notifications on any document in the tree:
Server Error in '/'
Application.
________________________________
Multiple controls with the same ID 'r' 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
'r' were found. FindControl requires that controls have unique IDs.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can be
identified using the exception stack trace below.
Stack Trace:
[HttpException (0x80004005): Multiple controls with the same ID 'r' were found.
FindControl requires that controls have unique IDs.]
System.Web.UI.Control.FillNamedControlsTable(Control namingContainer,
ControlCollection controls) +273
System.Web.UI.Control.FillNamedControlsTable(Control namingContainer,
ControlCollection controls) +320
System.Web.UI.Control.FillNamedControlsTable(Control namingContainer,
ControlCollection controls) +320
System.Web.UI.Control.EnsureNamedControlsTable() +61
System.Web.UI.Control.FindControl(String id, Int32 pathOffset) +222
System.Web.UI.Control.FindControl(String id, Int32 pathOffset) +327
System.Web.UI.Control.FindControl(String id, Int32 pathOffset) +327
System.Web.UI.Page.FindControl(String id) +38
System.Web.UI.Page.ProcessPostData(NameValueCollection postData, Boolean
fBeforeLoad) +232
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
Boolean includeStagesAfterAsyncPoint) +1743
Uninstalling the package fixed the error.
Hope there is an obvious, quick fix to this because we really found the package to be useful in our implementation!
This seems a bit odd. Which document notifications are you subscribing to?
Do you know where this error occurs? It could be that the controls within the Standard Values section has the same id as the controls in the content section, but I don't see how they can be it at the same time as they are loaded individually. And I dont' see anything specific to my plugin.
If you can give me some more info I will try and track down the error, but the stack trace isn't super helpful. I can setup a solution with the same notifications and test if you guide me in the right direction.
It seems to happen with all notification types. I tried subscribing to several different types: publish, send to publish, create, move, translate - the result is the same. After selecting the notification type and clicking "update", the notification window displays the "Multiple controls..." error.
Our Umbraco version is v4.0.3.
4 of the environments (dev, qa, staging and production) are running blogforUmbraco4 v1.0.0
My local dev box is running BlogForUmbraco v2.0.24
All environments are using AutoFolders v2.0.2 and Content Maintenance v1.1.
All environments exhibit the same behavior.
Please let me know if there is additional information I can provide to help track this down.
I think I found the problem. I can recreate the issue when I try to create a new Notification from the Content trees Context Menu. Problem is that my "Create new key"-action uses lowercase R as the Letter identifier and the Rights action uses uppercase R, and since the FindControl method isn't case sensitive an error occurs because these two controls are present:
<input type="checkbox" name="ctl00$body$R" id="ctl00_body_R"> and <input type="checkbox" name="ctl00$body$r" id="ctl00_body_r">
I have changed the key and uploaded a new release, but I cannot garantee that this won't happen again if you use other packages with Actions.
Thank you very much for the update. I've installed in all environments except production and all seems well so far. Will try to get it on production tomorrow.
I dont think issue is related to this project as I get the same error and I do not have this package installed - unless it is also coming up in your google analytics package morten? - which I do have installed
Well i'm sorry to see that i'm causing problems with my custom Actions, but yes my Google Analytics package will produce the same error as Jeff has outlined here.
In the Google Analytics package i'm using 8 custom Actions, and I have just checked that 7 out of 8 uses a lower case Char which is used in upper case by Umbraco source. This will result in the same error as above, because the FindControl isn't case sensative.
I'm real sorry about this. Had I know about the FindControl method I would have been more thorough in testing the custom Actions.
I will write up a blog post outlining the issues encountered here, and I will look to update the Google Analytics package (but it will probably be at least a week before I have time).
Andrew, how urgent is this matter for you with regards to the Analytics package and the notification failures?
Hi Morten - it is not urgent at all. and please don't be sorry - your contribution to the community is invaluable. I will check back in a couple of weeks for an update to the package- thanks a million!
You can download the source of codeplex (http://gaumbraco.codeplex.com), change the chars used in the custom actions and drop a newly compiled dll in the bin folder and you should be good to go. Custom actions are located in the Sitereactor.GoogleAnalytics.Application.Actions namespace. In each of the 8 actions look for the following method:
public char Letter { get { return 'i'; } }
change it to a char that isn't already used.
Here is a list of chars that is used by standard umbraco actions (as well as the one mentioned in this thread for the standard values package):
Any update on this one? Did you create a blog post of how to fix the issue? or is there somewhere that we can download the modified DLL that fixes the issue?
Is your question in relation to the Standard Values package or the Google Analytics package?
The Notification issue has been fixed in the Standard Values package, but I have yet to check-in and release the changes for the Google Analytics package.
Please drop me a line if you have issues with Notification and the Google Analytics package and I'll point you to some new assemblies.
Notifications issue
This is a very useful package, but after installing it, we began getting the following error when attempting to subscribe to notifications on any document in the tree:
Server Error in '/' Application.
________________________________
Multiple controls with the same ID 'r' 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 'r' were found. FindControl requires that controls have unique IDs.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[HttpException (0x80004005): Multiple controls with the same ID 'r' were found. FindControl requires that controls have unique IDs.]
System.Web.UI.Control.FillNamedControlsTable(Control namingContainer, ControlCollection controls) +273
System.Web.UI.Control.FillNamedControlsTable(Control namingContainer, ControlCollection controls) +320
System.Web.UI.Control.FillNamedControlsTable(Control namingContainer, ControlCollection controls) +320
System.Web.UI.Control.EnsureNamedControlsTable() +61
System.Web.UI.Control.FindControl(String id, Int32 pathOffset) +222
System.Web.UI.Control.FindControl(String id, Int32 pathOffset) +327
System.Web.UI.Control.FindControl(String id, Int32 pathOffset) +327
System.Web.UI.Page.FindControl(String id) +38
System.Web.UI.Page.ProcessPostData(NameValueCollection postData, Boolean fBeforeLoad) +232
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1743
Uninstalling the package fixed the error.
Hope there is an obvious, quick fix to this because we really found the package to be useful in our implementation!
Jeff
Hi Jeff,
This seems a bit odd. Which document notifications are you subscribing to?
Do you know where this error occurs? It could be that the controls within the Standard Values section has the same id as the controls in the content section, but I don't see how they can be it at the same time as they are loaded individually. And I dont' see anything specific to my plugin.
If you can give me some more info I will try and track down the error, but the stack trace isn't super helpful. I can setup a solution with the same notifications and test if you guide me in the right direction.
Thanks,
- Morten
Hi Morten,
It seems to happen with all notification types. I tried subscribing to several different types: publish, send to publish, create, move, translate - the result is the same. After selecting the notification type and clicking "update", the notification window displays the "Multiple controls..." error.
Our Umbraco version is v4.0.3.
4 of the environments (dev, qa, staging and production) are running blogforUmbraco4 v1.0.0
My local dev box is running BlogForUmbraco v2.0.24
All environments are using AutoFolders v2.0.2 and Content Maintenance v1.1.
All environments exhibit the same behavior.
Please let me know if there is additional information I can provide to help track this down.
Thanks,
Jeff
Hi Jeff,
I think I found the problem. I can recreate the issue when I try to create a new Notification from the Content trees Context Menu.
Problem is that my "Create new key"-action uses lowercase R as the Letter identifier and the Rights action uses uppercase R, and since the FindControl method isn't case sensitive an error occurs because these two controls are present:
I have changed the key and uploaded a new release, but I cannot garantee that this won't happen again if you use other packages with Actions.
- Morten
HI Morten,
Thank you very much for the update. I've installed in all environments except production and all seems well so far. Will try to get it on production tomorrow.
Again, thank you for the quick fix.
Jeff
I dont think issue is related to this project as I get the same error and I do not have this package installed - unless it is also coming up in your google analytics package morten? - which I do have installed
Hi Andrew,
Well i'm sorry to see that i'm causing problems with my custom Actions, but yes my Google Analytics package will produce the same error as Jeff has outlined here.
In the Google Analytics package i'm using 8 custom Actions, and I have just checked that 7 out of 8 uses a lower case Char which is used in upper case by Umbraco source. This will result in the same error as above, because the FindControl isn't case sensative.
I'm real sorry about this. Had I know about the FindControl method I would have been more thorough in testing the custom Actions.
I will write up a blog post outlining the issues encountered here, and I will look to update the Google Analytics package (but it will probably be at least a week before I have time).
Andrew, how urgent is this matter for you with regards to the Analytics package and the notification failures?
- Morten
Hi Morten - it is not urgent at all. and please don't be sorry - your contribution to the community is invaluable. I will check back in a couple of weeks for an update to the package- thanks a million!
Hi everybody,
Does anyone know how to fix it while Morten updates the package ?
We are having a demo on monday where both "notifications" and "Google Analytics" functionality would be very appreciated.
Thanks in advance
jac
You can download the source of codeplex (http://gaumbraco.codeplex.com), change the chars used in the custom actions and drop a newly compiled dll in the bin folder and you should be good to go.
Custom actions are located in the Sitereactor.GoogleAnalytics.Application.Actions namespace. In each of the 8 actions look for the following method:
change it to a char that isn't already used.
Here is a list of chars that is used by standard umbraco actions (as well as the one mentioned in this thread for the standard values package):
Hope this works out for you (will probably have to blog about this).
- Morten
Hi Morten,
Any update on this one? Did you create a blog post of how to fix the issue? or is there somewhere that we can download the modified DLL that fixes the issue?
Sorry, didn't see your post.
Is your question in relation to the Standard Values package or the Google Analytics package?
The Notification issue has been fixed in the Standard Values package, but I have yet to check-in and release the changes for the Google Analytics package.
Please drop me a line if you have issues with Notification and the Google Analytics package and I'll point you to some new assemblies.
- Morten
is working on a reply...