[MAGNOLIA-2782] EditButton edits MainContent instead of CurrentContent Created: 12/Jun/09 Updated: 23/Jan/13 Resolved: 04/Aug/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | taglibs |
| Affects Version/s: | 4.0.1, 4.1 |
| Fix Version/s: | 4.1.1 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Christian Menzel | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | EditButton, taglib | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Patch included: |
Yes
|
| 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 <cms:loadPage/> before <cms:editButton/> the edit dialog opens with the hande of the 'main' content in the parameter 'mgnlPath'. |
| Comments |
| Comment by Philipp Bärfuss [ 12/Jun/09 ] |
|
You are right. Unfortunately we can't commit that to 4.1 as we are in progress of releasing. Scheduled for 4.0.1. Being able to pass a content object directly similar to other tags is appreciated. You can currently workaround that by setting the main content AggregationState.setMainContent(Content). Since 4.0 you have a state object available in your template. |
| Comment by Jan Haderka [ 04/Aug/09 ] |
|
Done as of r26985. |