[MAGNOLIA-7412] Partially erroneous registered apps Created: 15/Nov/18  Updated: 16/Nov/18

Status: Accepted
Project: Magnolia
Component/s: None
Affects Version/s: 6.0
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Christoph Meier Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
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

 Description   

Description

In a use case with 3 CT-based apps I have observed partially erroneous registered apps.
When debugging, we can see that the name (and the registryId) of one app was wrong.

This leads to some problems / unexpected behavior e.g. on the applauncher. (That’s why I got aware of the problem).


Use case / examples
My use case was a light module with 3 CTs - each CT with a CT-based app:
=> content-type-examples (tagged version).

CT-name as defined app-name as defined app name as in registry*
tourVehicle tourVehicles-app tourVehicles-app
tourGuide tourGuides-app tourOffices-app
tourOffice tourOffices-app tourOffices-app

*) checked via debugger


 

Side problem
The „special“ thing about the use case is, that all the 3 apps are CT-based, and that on startup these CTs (and its apps) may have problems due to relations between CTs and the fact that the CTs are loaded arbitrary. (We have a ticket for this => MGNLCT-80)
To overcome this, in my use case, I usually touch all files for CTs and for apps in the appropriate order to make sure the CTs (and hopefully the apps too) are registered correctly.
When looking carefully at the log - while touching the files to enforce (hopefully) proper registration, we already can see some issues (sometimes); see gist.
Order of touching the files: 

  1. tourVehicle.yaml (CT)
  2. tourVehicles-app.yaml (app-def.)
  3. tourGuide.yaml
  4. tourGuides-app.yaml
  5. tourOffice.yaml
  6. tourOffices-app.yaml

 

Side note

The problem does not always appear, and sometimes the problem may be a bit different. (The 2nd statement is a conclusion from what I have seen on the app-launcher).



 Comments   
Comment by Christoph Meier [ 15/Nov/18 ]

Note that one of the CT-based apps mentioned above had one minor issue.
(Label instead of label in the app def{{ tourGuides-app).}}

I have added a tag to the repo with the examples; the tagged version is identical to version I was using when observing the error in the app registry. 
(https://git.magnolia-cms.com/users/cmeier/repos/content-type-examples/browse?at=refs%2Ftags%2FFOR-MAGNOLIA-7412)

Edit:
Also after fixing the above mentioned minor issues (label vs Label)

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