[EXCONTRANS-299] After fresh install I still have ECTS group Created: 24/Sep/18  Updated: 24/Mar/20  Resolved: 01/Oct/18

Status: Closed
Project: Content Translation Extended (CTX)
Component/s: None
Affects Version/s: 2.0.1
Fix Version/s: 2.0.2

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Chuong Doan Huy
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1d
Original Estimate: 1d

Attachments: PNG File appluancher.png    
Issue Links:
relation
is related to EXCONTRANS-281 Consolidate the apps into one app wit... Closed
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:
Epic Link: Release-2.0.2
Sprint: Scrum Sprint 16

 Description   

In EXCONTRANS-281 we consolidated the apps into a single app. However, when I install the modules into a new instance of Magnolia I still see these apps in the applauncher.

Further more I don't see the consolidated app under the tools menu.



 Comments   
Comment by Richard Gange [ 24/Sep/18 ]

When making a change to a module like this you must consider 2 scenarios. The upgrade scenario and the fresh install.

If a customer had 2.0 installed previously:

  1. An upgrade task to remove the current menu from the config
  2. An upgrade task to place the new app in the tools menu

If a customer is installing fresh:

  1. Previous bootstrap files need to be removed so they are not installed.
  2. Previous apps need to be removed from the module completely.
  3. A bootstrap file needs to be created to install the new app
Comment by Trung Luu [ 25/Sep/18 ]

Hi rgange, Thanks a lot for the feedback!

As mentioned in EXCONTRANS-281 that "We merged translation apps into one app that call extendContentTranslation and The users would be able to add this app in any group like TOOLS app" I have proposed the option to add the merged app to any group. I didn't remove the old group and add this app into TOOLS group by default because I thought that users might not know where can find the app. What do you think?

I will create the upgrade scenario and the fresh install as your suggestions in release 2.0.2

Thanks,
Trung Luu

Comment by Richard Gange [ 25/Sep/18 ]

Hello-
My high level suggestion is to stay within the framework of how other modules are designed and people will inherently know how it works. Case and point, rather than call something "enabledFlag" call it "enabled". This is the term used by every other module except this one. The moral of the story is, when making a design decisions think about other modules you know (and used) and stick to those conventions.

The current translation app is already in the Tools menu so people should be familiar with that. This app has existed for a long time and that's why I suggested it be placed there, next to it.
Documentation can also explain where to find the app. Another suggestion would be to remove the word "Translation" from all the subapp labels except for the first one. The reason is having it on all three tabs makes those tabs extend further across the screen horizontally. This can lead to a bad UX experience on smaller resolutions. App should be designed to look good for 1024×768 res.

HTH

Comment by Trung Luu [ 25/Sep/18 ]

Above comments are very helpful. Really appreciate (bow) All clear now, So I will also remove the word "Translation" from all the subapp labels except for the first one in version 2.0.2. Thank you!!!

Comment by Richard Gange [ 25/Sep/18 ]

No sweat

Comment by Trung Luu [ 01/Oct/18 ]

rgangeFYI, The new version has been released and already included this issue. Thanks

Generated at Mon Feb 12 00:29:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.