[BLOSSOM-219] No action bar when editing a page created with Blossom 3.1 Created: 05/Aug/15 Updated: 25/Jul/16 Resolved: 13/Nov/15 |
|
| Status: | Closed |
| Project: | Blossom |
| Component/s: | None |
| Affects Version/s: | 3.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jean-Francois Nadeau | Assignee: | Tobias Mattsson |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows 7 |
||
| Attachments: |
|
| 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 |
|
On Magnolia 5.4 and Blossom 3.1 |
| Comments |
| Comment by Tobias Mattsson [ 07/Aug/15 ] |
|
Is this on a fresh 5.4 install or was it updated from 5.3 to 5.4? Did you have any error messages during the update? Do you see anything in the logs that might hint at a problem? Do you see warnings in the console when you use the browser developer tools? Can you export the node '/modules/pages/apps/pages/subApps/detail/actionbar' and attach it to the ticket? |
| Comment by Jean-Francois Nadeau [ 07/Aug/15 ] |
|
I tested it on a fresh community bundle and a fresh enterprise bundle. Do you have the same problem if you drop my module in your environment? |
| Comment by Tobias Mattsson [ 14/Aug/15 ] |
|
I've reproduced it and found that the problem is in the freemarker file. The cms:init directive wants to be in a <head> tag. If you replace test.ftl with this it works: <html> <head> [@cms.init /] </head> <body> ${cmsfn.decode(content).contenu!} ***test*** </body> </html> |