[MGNLSITE-40] Site module does not bootstrap a config node for the site Created: 25/Sep/15  Updated: 06/Oct/15  Resolved: 05/Oct/15

Status: Closed
Project: Magnolia Site Module
Component/s: api, app
Affects Version/s: 1.0.2
Fix Version/s: 1.0.3

Type: Bug Priority: Neutral
Reporter: Tobias Mattsson Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1d 2.25h
Original Estimate: Not Specified

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:
Sprint: Basel 13
Story Points: 3

 Description   

Site module does not create the config:/modules/site/config/site node. Unless it's bootstrapped in by another module, such as STK or travel demo, the site-app is unusable with an empty actionbar, and also produces an error in the log

WARN  agnolia.ui.workbench.tree.HierarchicalJcrContainer: Cannot retrieve root item id's: javax.jcr.PathNotFoundException: /modules/site/config/site

This commit back in 1.0-m2 is kind of related https://git.magnolia-cms.com/gitweb/?p=modules/site.git;a=commit;h=3ab8877546a32e0f8fc991e90710d87cce97ffa0



 Comments   
Comment by Philip Mundt [ 02/Oct/15 ]

Hey tmattsson, would you mind adding a "howto reproduce" note to the description. I've been trying to get the error but I can't by

  1. using CE bundle,
  2. not installing any demo (only MTE),
  3. removing the site node (config:/modules/site/config/site) (the SiteManager then serves the NullSite!?),
  4. adding a template with renderType=freemarker and/or renderType=site & an area node configured with availability for mte:components/textImage,
  5. adding one sample component to the area and
  6. everything renders just fine (no unavailable actions in page editor).

Edit: site-app is not pages app. Rendering still works for me.

Comment by Tobias Mattsson [ 02/Oct/15 ]

It happens when I add this to magnolia-empty-webapp/pom.xml and starts it up.

    <dependency>
      <groupId>info.magnolia.site</groupId>
      <artifactId>magnolia-site</artifactId>
      <version>1.0.3-SNAPSHOT</version>
    </dependency>
    <dependency>
      <groupId>info.magnolia.site</groupId>
      <artifactId>magnolia-site-app</artifactId>
      <version>1.0.3-SNAPSHOT</version>
    </dependency>
Comment by Tobias Mattsson [ 02/Oct/15 ]

I'm not able to reproduce the rendering error I mentioned when creating the ticket and I don't have saved stacktrace from then. It's possible that I was misstaken and the cause of that was something else.

Generated at Mon Feb 12 07:12:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.