[NPMCLI-1] Glitches found during first testing Created: 05/Apr/16  Updated: 22/Aug/16  Resolved: 05/Apr/16

Status: Closed
Project: Magnolia CLI
Component/s: None
Affects Version/s: None
Fix Version/s: 0.0.1

Type: Bug Priority: Critical
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: Not Specified
Original Estimate: 0d

Issue Links:
dependency
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 38

 Description   
  • extracted apache-tomcat does not contain logs folder leading to startup being aborted as Tomcat tries to create catalina.out inside the non existing logs folder
  • user must manually chmod 755 *.sh (*.bat) or Tomcat cannot be started
  • add-availability and add-component throw an error due to Cannot find module 'yamljs'


 Comments   
Comment by Tomáš Gregovský [ 05/Apr/16 ]

"add-page home new template is not visible and must be added manually to /modules/travel-demo/config/travel/templates/availability/templates"

  • isn't that only in EE Pro ? other versions of Magnolia should accept all pages with renderType:freemarker
Comment by Federico Grilli [ 05/Apr/16 ]

I guess this has changed in 5.4.5 due to MGNLSITE-41. But prolly just need to make the template visible:true Nope, doesn't work. Apparently now one needs to add the template to the site template availability

Generated at Mon Feb 12 04:45:34 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.