[magnolia-dev] [JIRA] Created: (MAGNOLIA-3353) Extends feature brakes various things (templates/dialogsparagraphs) if wrong configured
Extends feature brakes various things (templates/dialogsparagraphs) if wrong configured --- Key: MAGNOLIA-3353 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3353 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.8, 4.3.7, 4.3.6, 4.3.5, 4.3.4, 4.3.3, 4.3.2 Reporter: Christian Ringele Assignee: Ondřej Chytil The behavior is very different on tempates/dialogs and paragraphs, so I'll open for these three situations a sub issue with a detailed description. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3354) Extends: Registered teamplates get lost below wrong configuration
Extends: Registered teamplates get lost below wrong configuration - Key: MAGNOLIA-3354 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3354 Project: Magnolia Issue Type: Sub-task Components: core Affects Versions: 4.3.8, 4.3.7, 4.3.6, 4.3.5, 4.3.4, 4.3.3, 4.3.2 Reporter: Christian Ringele Assignee: Ondřej Chytil Attachments: Screen shot 2010-11-02 at 10.49.55 AM.png, Screen shot 2010-11-02 at 10.51.44 AM.png, Screen shot 2010-11-02 at 10.52.11 AM.png Base setup: Adding a template definition, which extends another template definition (see print screen). Problem: If the value of the extends property is set wrong, all template definitions registered below the wrong node are invalid. So if placed for example below the stkSection (see print screen), all template below are not found anymore (print screen). Behavior on correct reconfiguration: When correcting the wrong extends value, all templates are registered correct again. What should be changed: Following template definitions of a wrong definition should be still registered. and usable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3354) Extends Templates: Registered teamplates get lost below wrong configuration
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3354: Summary: Extends Templates: Registered teamplates get lost below wrong configuration (was: Extends: Registered teamplates get lost below wrong configuration) Extends Templates: Registered teamplates get lost below wrong configuration --- Key: MAGNOLIA-3354 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3354 Project: Magnolia Issue Type: Sub-task Components: core Affects Versions: 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7, 4.3.8 Reporter: Christian Ringele Assignee: Ondřej Chytil Attachments: Screen shot 2010-11-02 at 10.49.55 AM.png, Screen shot 2010-11-02 at 10.51.44 AM.png, Screen shot 2010-11-02 at 10.52.11 AM.png Base setup: Adding a template definition, which extends another template definition (see print screen). Problem: If the value of the extends property is set wrong, all template definitions registered below the wrong node are invalid. So if placed for example below the stkSection (see print screen), all template below are not found anymore (print screen). Behavior on correct reconfiguration: When correcting the wrong extends value, all templates are registered correct again. What should be changed: Following template definitions of a wrong definition should be still registered. and usable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3355) Extends Dialogs: All registered dialogs get lost after correcting a wrong configuration
Extends Dialogs: All registered dialogs get lost after correcting a wrong configuration --- Key: MAGNOLIA-3355 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3355 Project: Magnolia Issue Type: Sub-task Components: core Affects Versions: 4.3.8, 4.3.7, 4.3.6, 4.3.5, 4.3.4, 4.3.3, 4.3.2 Reporter: Christian Ringele Assignee: Philipp Bärfuss Attachments: Screen shot 2010-11-02 at 10.59.22 AM.png, Screen shot 2010-11-02 at 11.11.04 AM.png Base setup: Adding a dialog, which extends an existing one (see print screen) Problem 1 - Dialog is below all others: Step1: Adding a wrong value to the extends property makes the dialog unusable (that is correct yet). All other dialogs are still usable as they should. Step2: Changing the wrong value back to the correct value used before - all registered dialogs are lost! No dialog is available anymore provided by this module. Behavior on correct reconfiguration: All dialogs of the module are lost, no matter on which location the dialog was registered. Only a restart of the server registers the dialogs again. Problem 2 - Dialog is places in between: Step1: Adding a wrong value to the extends property makes the dialog unusable (that is correct yet). All dialogs placed below this wrong dialog are not registered anymore (same as on templates). What should be changed: That all dialogs are always registered and usable, except the one which has a wrong configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3355) Extends Dialogs: All registered dialogs get lost after correcting a wrong configuration
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3355: Assignee: Ondřej Chytil (was: Philipp Bärfuss) Extends Dialogs: All registered dialogs get lost after correcting a wrong configuration --- Key: MAGNOLIA-3355 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3355 Project: Magnolia Issue Type: Sub-task Components: core Affects Versions: 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7, 4.3.8 Reporter: Christian Ringele Assignee: Ondřej Chytil Attachments: Screen shot 2010-11-02 at 10.59.22 AM.png, Screen shot 2010-11-02 at 11.11.04 AM.png Base setup: Adding a dialog, which extends an existing one (see print screen) Problem 1 - Dialog is below all others: Step1: Adding a wrong value to the extends property makes the dialog unusable (that is correct yet). All other dialogs are still usable as they should. Step2: Changing the wrong value back to the correct value used before - all registered dialogs are lost! No dialog is available anymore provided by this module. Behavior on correct reconfiguration: All dialogs of the module are lost, no matter on which location the dialog was registered. Only a restart of the server registers the dialogs again. Problem 2 - Dialog is places in between: Step1: Adding a wrong value to the extends property makes the dialog unusable (that is correct yet). All dialogs placed below this wrong dialog are not registered anymore (same as on templates). What should be changed: That all dialogs are always registered and usable, except the one which has a wrong configuration. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3353) Extends feature brakes templatesdialog definitions
[ http://jira.magnolia-cms.com/browse/MAGNOLIA-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Ringele updated MAGNOLIA-3353: Summary: Extends feature brakes templatesdialog definitions (was: Extends feature brakes various things (templates/dialogsparagraphs) if wrong configured) Description: The behavior is very different on templatesdialogs, so I'll open for these two situations a sub issue with a detailed description. If doing the same as described in the sub-tasks with paragraph definitions, it works fine. Only the wrong configured paragraph definition is invalid, but all other paragraph definitions stay always registered and available. was:The behavior is very different on tempates/dialogs and paragraphs, so I'll open for these three situations a sub issue with a detailed description. Extends feature brakes templatesdialog definitions --- Key: MAGNOLIA-3353 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3353 Project: Magnolia Issue Type: Bug Components: core Affects Versions: 4.3.2, 4.3.3, 4.3.4, 4.3.5, 4.3.6, 4.3.7, 4.3.8 Reporter: Christian Ringele Assignee: Ondřej Chytil The behavior is very different on templatesdialogs, so I'll open for these two situations a sub issue with a detailed description. If doing the same as described in the sub-tasks with paragraph definitions, it works fine. Only the wrong configured paragraph definition is invalid, but all other paragraph definitions stay always registered and available. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3356) AdminCentral Accessibility Improvement - Edit screen buttons
AdminCentral Accessibility Improvement - Edit screen buttons Key: MAGNOLIA-3356 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3356 Project: Magnolia Issue Type: Improvement Components: admininterface Affects Versions: 4.3.7 Reporter: Steve Pugh Assignee: Philipp Bärfuss Fix For: 4.4.x The red/amber/green Status icons do not have alt or title attributes on the IMG tag. Would be great if you could add these in. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3356) AdminCentral Accessibility Improvement - Edit screen buttons
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Pugh updated MAGNOLIA-3356:
-
Description:
On the edit page screen, the page components (paragraps) have green banners
containing Edit, Move and Delete buttons.
These are currently implemented as spans:
span onmousedown=mgnlShiftPushButtonDown(this);
onmouseout=mgnlShiftPushButtonOut(this);
onclick=mgnlShiftPushButtonClick(this);mgnlOpenDialog('/www/main','','0','stkTeaserNewsList','website','.magnolia/dialogs/editParagraph.html',
null, null, 'en'); class=mgnlControlButtonSmall style=background: none
repeat scroll 0% 0% transparent;Edit/span
From an accessibility point of view it would be better if these were standard
HTML buttons. It would also have the advantage of making them selectable via
the tab key.
was:
On the edit page screen, the page components (paragraps) have green banners
containing Edit, Move and Delete buttons.
These are currently implemented as spans:
span onmousedown=mgnlShiftPushButtonDown(this);
onmouseout=mgnlShiftPushButtonOut(this);
onclick=mgnlShiftPushButtonClick(this);mgnlOpenDialog('/www/main','','0','stkTeaserNewsList','website','.magnolia/dialogs/editParagraph.html',
null, null, 'en'); class=mgnlControlButtonSmall style=background: none
repeat scroll 0% 0% transparent;Edit/span
From an accessibility point of view it would be better if these standard
buttons. It would also have the advantage of making them selectable via the
tab key.
AdminCentral Accessibility Improvement - Edit screen buttons
Key: MAGNOLIA-3356
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3356
Project: Magnolia
Issue Type: Improvement
Components: admininterface
Affects Versions: 4.3.7
Reporter: Steve Pugh
Assignee: Philipp Bärfuss
Fix For: 4.4.x
On the edit page screen, the page components (paragraps) have green banners
containing Edit, Move and Delete buttons.
These are currently implemented as spans:
span onmousedown=mgnlShiftPushButtonDown(this);
onmouseout=mgnlShiftPushButtonOut(this);
onclick=mgnlShiftPushButtonClick(this);mgnlOpenDialog('/www/main','','0','stkTeaserNewsList','website','.magnolia/dialogs/editParagraph.html',
null, null, 'en'); class=mgnlControlButtonSmall style=background: none
repeat scroll 0% 0% transparent;Edit/span
From an accessibility point of view it would be better if these were standard
HTML buttons. It would also have the advantage of making them selectable via
the tab key.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Updated: (MAGNOLIA-3356) AdminCentral Accessibility Improvement - Edit screen buttons
[
http://jira.magnolia-cms.com/browse/MAGNOLIA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Pugh updated MAGNOLIA-3356:
-
Description:
On the edit page screen, the page components (paragraps) have green banners
containing Edit, Move and Delete buttons.
These are currently implemented as spans:
span onmousedown=mgnlShiftPushButtonDown(this);
onmouseout=mgnlShiftPushButtonOut(this);
onclick=mgnlShiftPushButtonClick(this);mgnlOpenDialog('/www/main','','0','stkTeaserNewsList','website','.magnolia/dialogs/editParagraph.html',
null, null, 'en'); class=mgnlControlButtonSmall style=background: none
repeat scroll 0% 0% transparent;Edit/span
From an accessibility point of view it would be better if these standard
buttons. It would also have the advantage of making them selectable via the
tab key.
was:
The red/amber/green Status icons do not have alt or title attributes on
the IMG tag.
Would be great if you could add these in.
AdminCentral Accessibility Improvement - Edit screen buttons
Key: MAGNOLIA-3356
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3356
Project: Magnolia
Issue Type: Improvement
Components: admininterface
Affects Versions: 4.3.7
Reporter: Steve Pugh
Assignee: Philipp Bärfuss
Fix For: 4.4.x
On the edit page screen, the page components (paragraps) have green banners
containing Edit, Move and Delete buttons.
These are currently implemented as spans:
span onmousedown=mgnlShiftPushButtonDown(this);
onmouseout=mgnlShiftPushButtonOut(this);
onclick=mgnlShiftPushButtonClick(this);mgnlOpenDialog('/www/main','','0','stkTeaserNewsList','website','.magnolia/dialogs/editParagraph.html',
null, null, 'en'); class=mgnlControlButtonSmall style=background: none
repeat scroll 0% 0% transparent;Edit/span
From an accessibility point of view it would be better if these standard
buttons. It would also have the advantage of making them selectable via the
tab key.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
[magnolia-dev] [JIRA] Created: (MAGNOLIA-3357) CompositeFilter does not set correct name in FilterConfig when delegating initialization to contained filters
CompositeFilter does not set correct name in FilterConfig when delegating initialization to contained filters - Key: MAGNOLIA-3357 URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-3357 Project: Magnolia Issue Type: Bug Components: core Reporter: Tobias Mattsson Assignee: Tobias Mattsson Fix For: 4.4.x CompositeFilter needs to pass a FilterConfig object with the correct name set. It can get the name by calling getName() on the filter to initialize. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: dev-list-unsubscr...@magnolia-cms.com
