[MGNLSITE-59] Site app should automatically configure itself correctly when added to a project Created: 12/Apr/16 Updated: 18/May/17 Resolved: 18/May/17 |
|
| Status: | Closed |
| Project: | Magnolia Site Module |
| Component/s: | app |
| Affects Version/s: | 1.0.5 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Nils Breunese | Assignee: | Federico Grilli |
| Resolution: | Workaround exists | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.5d | ||
| Original Estimate: | Not Specified | ||
| 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)
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Sprint: | Basel 96 | ||||||||||||||||
| Story Points: | 1 | ||||||||||||||||
| Description |
|
We build our own Magnolia WAR project with custom modules. We added the magnolia-site-app to our project after we had already upgraded to STK 2.9.3 and found that we had to manually change config:/modules/site-app/apps/site/subApps/browser/contentConnector@rootPath to /modules/multisite/config/sites for our multisite setup. Also, STKModuleVersionHandler removes the legacy Site definitions and Themes entries from the STK app launcher group when the site-app module is installed when upgrading to STK 2.9.3, but in our case the site-app module was installed after upgrading to STK 2.9.3, so this didn't happen and we also had to remove these legacy entries manually. Maybe it would be better to have SiteAppModuleVersionHandler take care of this, so that this also happens when adding the site-app module later on. |
| Comments |
| Comment by Michael Mühlebach [ 17/Nov/16 ] |
|
I guess one part of that issue with the accidental removal of the theme has been solved by |
| Comment by Antti Hietala [ 12/May/17 ] |
|
Instead of implementing this feature, we:
|
| Comment by Federico Grilli [ 18/May/17 ] |
|
See |