[MGNLFORM-74] Form components are not movable Created: 20/Dec/10 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia Form Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | next, verify | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
Form components are not movable, i.e the "move" button is not rendered in the template. This issue is not visible on the demo project, since the contact form is added as a "singleton" paragraph on the contact-form page, and no other form can be added, as far as I can tell. But if we modify a template definition to allow the "form" paragraph, the move button is not rendered and such form components can thus only be moved using the jcr browser. |
| Comments |
| Comment by Tobias Mattsson [ 11/Jan/11 ] |
|
Philipp, I think I remember a discussion we had about this. The reason the form isnt movable is that it doesnt include an editBar and i think you wanted it that way for STK. Should we add the editBar or leave as is? |
| Comment by Philipp Bärfuss [ 11/Jan/11 ] |
|
We shouldn't show the move/delete buttons in case of a singleton template (like the contact template). The idea was to pass an attribute to the paragraph by its parent |
| Comment by Christopher Zimmermann [ 05/Dec/13 ] |
|
Probably solved by area concept. |
| 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. |