[MGNLUI-1472] Content app should launch without actionbar configuration Created: 29/May/13 Updated: 28/Jun/13 Resolved: 27/Jun/13 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | content app |
| Affects Version/s: | 5.0 |
| Fix Version/s: | 5.0.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Antti Hietala | Assignee: | Tobias Mattsson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
5.0 beta 2 |
||
| Issue Links: |
|
||||||||
| 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
|
||||||||
| Description |
|
A content app does not launch unless you configure an action bar. This is too much to ask. When you configure your first content app step-by-step, you have to create a lot of configuration before you can see the app run for the first time.
Make the threshold lower. Give new users the "whoa it works" feeling faster. Make the app launchable after step 3. Even if it just displays an empty subapp. The system can handle a missing actionbar definition already today. WARN: No actionbar definition found. This will result in an empty action bar. Is that intended? So maybe it is just the configured content app that fails to start. |