-
Bug
-
Resolution: Won't Do
-
Neutral
-
None
-
5.4.3
-
None
-
None
-
-
Empty show more show less
During training material creation I have encountered bad and strange behavior of the ActionBar of the page's detail subApp.
Generally:
When using a script not containing cms:page and cms:area no ActionBar is displayed in the page's detail app.
I think this can be defined as a bug -> why should the outer Content App framework react in its ActianBar to the inner rendered item within the subApps workbench?
=> the ActionBar should always be there.
Reproduce:
- Create a type Freemarker page template
- Have a 'main' area of type 'list' in it
- Don’t add any components into the main (no component content)
- Use this code in its script:
<!DOCTYPE html> <html xml:lang="en" lang="en" class="no-js"> <head> [#--[@cms.page /]--] </head> <body> <h1>Hello Test</h1> [#--[@cms.area name="main" /]--] </body> </html>
Be aware:
The cms:page and cms:area are commented out. I will use them for the different scenario explanation.
Situation 1.: Bug
(Use the code as it is)
Setup:
Mode of editor: view or edit the same
cms:page -> NOT used
cms:area -> NOT used
Result: No ActionBar
Situation 2.: Strange behaviour (Bug)
Setup:
Mode of editor: view
cms:page -> NOT used
cms:area -> IS used
Result:
- Has ActionBar, but wrong -> as if you had clicked on the area itself
- BUT the area itself is not rendered
Situation 3.: Strange behaviour (Bug)
Setup:
Mode of editor: edit
cms:page -> NOT used
cms:area -> IS used
Result:
- Has ActionBar, but wrong -> it does not change from the 'view' state. Still having "Preview Page". But its not reacting at all, not able to switch back to the 'view' mode.
- BUT the area itself is not rendered
Situation 4.: Correct behaviour
Setup:
Mode of editor: edit and view
cms:page -> IS used
cms:area -> NOT used
Result:
Correct behaviour
Situation 5.: Correct behaviour
Setup:
Mode of editor: edit and view
cms:page -> IS used
cms:area -> IS used
Result:
Correct behaviour, also the area is rendered as expected.
For a second round of test scenarios use now this code:
[#--[@cms.page /]--]
<h1>Hello Test</h1>
[#--[@cms.area name="main" /]--]
Be aware again:
The cms:page and cms:area are commented out. I will use them for the different scenario explanation.
Situation 6.: Bug
(Use the code as it is)
Setup:
Mode of editor: view or edit the same
cms:page -> NOT used
cms:area -> NOT used
Result:
Same as in situation 1. (Problem)
Situation 7.: Strange behaviour (Bug)
Setup:
Mode of editor: view
cms:page -> NOT used
cms:area -> IS used
Result:
Same as in situation 2. (Problem)
Situation 8.: Strange behaviour (Bug)
Setup:
Mode of editor: edit
cms:page -> NOT used
cms:area -> IS used
Result:
Same as in situation 3. (Problem)
Situation 9.: Correct behaviour
Setup:
Mode of editor: edit and view
cms:page -> IS used
cms:area -> NOT used
Result:
Same as in situation 4. (Correct)
Situation 10.: Correct behaviour
Setup:
Mode of editor: edit and view
cms:page -> IS used
cms:area -> IS used
Result:
Different to situation 5.
- Same behaviour with the ActionBar as in Situation 2.
- Main problem: the area-bar itself is not rendered at all.
=> I think with even no html doc tag etc the area bar should be there. Try outs and page rendering snippets (called for example via Ajax) will probably not have them.
- duplicates
-
-
- Closed
-