[MAGNOLIA-2073] Hypenated contentNode names cause problems with some controls Created: 25/Feb/08  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: templating
Affects Version/s: 3.5.4
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Chris Allan Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Server 2003, Firefox 2.0.0.12, Magnolia 3.54EE


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When using the date control in a dialog, I have configured it as
follows:

Date-interview
controlType date String
description Date of Interview String
label Date of Interview String
name date-interview String
time false String
type Date String

If you try to open the dialog control and enter a date though, you get the following javascript errors:
missing ; before statement
var cal_butt_date-3 = Calendar.setup({\n

missing ; before statement
mgnlShiftPushButtonClick(this);cal_butt_date-3.show()

This problem seems to go away if you change the value of the 'name' node to anything without a '-' in it. So for, example 'dateinterview' is fine.

There is also a similar problem when using hyphenated-names with the fckEditor control.

I haven't looked at this with other controls yet.



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:33:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.