Name clash when adding multiple layout groups

Created on 24 September 2023, about 1 year ago
Updated 9 August 2024, 3 months ago

Problem/Motivation

I noticed if you add more than one layout group, the sub-groups will have the same name (and thus the sub-groups for the second layout group are not created)

Steps to reproduce

Add two layout groups, using the same layout or layouts with the same regions names.

Proposed resolution

Generate unique names for sub-groups.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Fixed

Version

1.0

Component

Miscellaneous

Created by

πŸ‡©πŸ‡ͺGermany donquixote

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @donquixote
  • Assigned to Valentine94
  • Status changed to Needs work about 1 year ago
  • πŸ‡ΊπŸ‡¦Ukraine Valentine94 Kyiv, Ukraine

    @donquixote, thank you for your report. I'll check it out

  • Issue was unassigned.
  • Status changed to Active about 1 year ago
  • πŸ‡ΊπŸ‡¦Ukraine Valentine94 Kyiv, Ukraine

    Hi @donquixote,

    Tried to reproduce it but never succeed. For test created two groups with "One column" layouts and checked the names:
    1. Group element has its unique machine name, like "group_test" and "group_test2".
    2. Subgroup element is main element machine name + region name, e.g. "group_test_content" and "group_test2_content".

    Since the main group always has unique name, the subgroup elements obviously have unique names as well.
    Please let me know if I missed anything or tested it wrong.

    Thanks

  • πŸ‡ΊπŸ‡¦Ukraine Valentine94 Kyiv, Ukraine
  • Status changed to Postponed: needs info about 1 year ago
  • πŸ‡³πŸ‡΄Norway matsbla

    I am also not able to reproduce this. Can you give steps to reproduce? And could you clarify what you mean with 'name', e.g. class name, machine name, UI name, etc?

  • Status changed to Fixed 4 months ago
  • πŸ‡³πŸ‡΄Norway matsbla

    Please upgrade to 2.0.0-alpha1, this should be fixed now.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024