Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Misleading button label after element duplication #980

Closed
tthalheim-at-dbfz opened this issue Apr 23, 2024 · 1 comment · Fixed by #999
Closed

Misleading button label after element duplication #980

tthalheim-at-dbfz opened this issue Apr 23, 2024 · 1 comment · Fixed by #999
Assignees
Labels
Milestone

Comments

@tthalheim-at-dbfz
Copy link

Description / Beschreibung

While duplicating an element, the duplication form offers two buttons to save the duplication:

  • copy and continue editing
  • copy

With application of copy and continue editing, a new form for the duplicated element is shown. The button are still labeled with

  • copy and continue editing
  • copy

But applying copy and continue editing again to this element, I would expect, that the original element is duplicated again, e.g. there are two copies of the original element available. However, there is one copy only and the observed behaviour of the copy and continue editing button rather corresponds to the save and continue editing procedure.

Expected behaviour / Erwartetes Verhalten

Following the button labels, I would expect to duplicate an element again and again, while applying the copy and continue editing button multiple times.

Steps to reproduce / Schritte zum Reproduzieren

  1. Create attribute labeled random_attribute and copy it to random_attribute_2 via copy and continue editing copy step 1
  2. Rename random_attribute_2 to random_attribute_3 and apply again copy and continue editing copy step 2
  3. Now, the attribute list contain random_attribute and random_attribute_3 only, while random_attribute_2 is vanished copy step 3

Context / Kontext

Occured in RDMO Version 2.1.3, Firefox

@jochenklar
Copy link
Member

Thanks for reporting, this will be fixed in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants