[MAGNOLIA-6733] RenameNodesTask only works for CONFIG workspace Created: 01/Aug/16  Updated: 30/Sep/21  Resolved: 30/Sep/21

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

Type: Bug Priority: Neutral
Reporter: Mercedes Iruela Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: y2k
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
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:

 Description   

RenameNodesTask is only working for CONFIG workspace, however it accepts workspace as parameter. This workspace it is not used, because RepositoryConstants.CONFIG is hardcoded in the construstor.

 public RenameNodesTask(String name, String workspace, String path, String oldName, String newName, String nodeType) {
        this(name, String.format("Rename all nodes of type '%s' under path '%s:%s' from '%s' to '%s'.", nodeType, workspace, path, oldName, newName),
                RepositoryConstants.CONFIG, path, oldName, newName, nodeType);
    }


 Comments   
Comment by Christopher Chard [ 15/Nov/20 ]

Hello,
this is still true - as we are experiencing.
However, the other constructor with 7 parameters (including description) can be used to be able to actually set the desired workspace.

This was frustrating to fix, could be fixed very easily.

  • Reporting based on v 6.2.3

Cheers
Chris

Comment by Marta Kobus [ 30/Sep/21 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

 

Thank you,

The Magnolia Team

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