U4-3271 - Using @ signs in nodenames causes issues when saving a node

Created by Richard Soeteman 29 Oct 2013, 09:48:34 Updated by Sebastiaan Janssen 28 May 2014, 16:26:39

When using my email address in Umbraco V6.1 I get the following exception. When using on a text field it works fine.

Parameter '@SOETEMANSOFTWARE' specified but none of the passed arguments have a property with this name (in 'WHERE ([umbracoNode].[nodeObjectType] = 'c66ba18e-eaf3-4cff-8a22-41b16d66a972' AND [umbracoNode].[parentID] = 1050 AND upper([umbracoNode].[text]) like 'RICHARD@SOETEMANSOFTWARE.NL%')') 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.ArgumentException: Parameter '@SOETEMANSOFTWARE' specified but none of the passed arguments have a property with this name (in 'WHERE ([umbracoNode].[nodeObjectType] = 'c66ba18e-eaf3-4cff-8a22-41b16d66a972' AND [umbracoNode].[parentID] = 1050 AND upper([umbracoNode].[text]) like 'RICHARD@SOETEMANSOFTWARE.NL%')')

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:

[ArgumentException: Parameter '@SOETEMANSOFTWARE' specified but none of the passed arguments have a property with this name (in 'WHERE ([umbracoNode].[nodeObjectType] = 'c66ba18e-eaf3-4cff-8a22-41b16d66a972' AND [umbracoNode].[parentID] = 1050 AND upper([umbracoNode].[text]) like 'RICHARD@SOETEMANSOFTWARE.NL%')')] Umbraco.Core.Persistence.<>c__DisplayClass1.b__0(Match m) +1056 System.Text.RegularExpressions.RegexReplacement.Replace(MatchEvaluator evaluator, Regex regex, String input, Int32 count, Int32 startat) +292 System.Text.RegularExpressions.Regex.Replace(String input, MatchEvaluator evaluator) +68 Umbraco.Core.Persistence.Sql.Build(StringBuilder sb, List1 args, Sql lhs) +112 Umbraco.Core.Persistence.Sql.Build() +148 Umbraco.Core.Persistence.Database.Fetch(Sql sql) +29 Umbraco.Core.Persistence.Repositories.ContentRepository.EnsureUniqueNodeName(Int32 parentId, String nodeName, Int32 id) +1106 Umbraco.Core.Persistence.Repositories.ContentRepository.PersistUpdatedItem(IContent entity) +389 Umbraco.Core.Persistence.Repositories.RepositoryBase2.PersistUpdatedItem(IEntity entity) +65 Umbraco.Core.Persistence.UnitOfWork.PetaPocoUnitOfWork.Commit() +422 Umbraco.Core.Services.ContentService.SaveAndPublishDo(IContent content, Int32 userId, Boolean raiseEvents) +871 umbraco.cms.businesslogic.web.Document.SaveAndPublishWithResult(User u) +595 umbraco.cms.presentation.editContent.Publish(Object sender, EventArgs e) +90 System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e) +134 System.Web.UI.WebControls.ImageButton.RaisePostBackEvent(String eventArgument) +204 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3804

Comments

Damiaan Peeters 19 Nov 2013, 16:57:49

Why is this bug closed? I have a similar issue.


Richard Soeteman 20 Nov 2013, 04:30:07

Nope still open, but since I know how to do pull requests these days I can try to fix this myself soon.


Damiaan Peeters 20 Nov 2013, 07:52:41

State of this bug is (was) "closed" currently.

EDIT: i've updated the status :-)


Damiaan Peeters 20 Nov 2013, 07:56:52

FYI - I've just tested this in v7, and it works without error.


Sebastiaan Janssen 28 May 2014, 16:26:39

I can't reproduce this in 6.2.1 any more, seems like it's been fixed for 6.2.0 then. I gave the nodename the name RICHARD@SOETEMANSOFTWARE.NL as that's what I see in this error here and that worked.


Priority: Normal

Type: Bug

State: Closed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 6.1.3, 6.1.4, 6.1.5, 6.1.6

Due in version:

Sprint:

Story Points:

Cycle: