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

Cloning modules breaks page module positioning #3309

Closed
leedavi opened this issue Nov 18, 2019 · 4 comments
Closed

Cloning modules breaks page module positioning #3309

leedavi opened this issue Nov 18, 2019 · 4 comments

Comments

@leedavi
Copy link
Contributor

leedavi commented Nov 18, 2019

Description of bug

When cloning a module from another page the other modules on the page, of the same type, are also moved into the pane that the new clone is added to.

Steps to reproduce

  1. Clear page.
  2. Add a html module.
  3. Create another page.
  4. Add a html modules to the top pane.
  5. Add an "Existing module", select the first page and first module. Then position into the content pane.
  • When selecting a module to clone, ensure you have unchecked "copy module"

Current result

The module in the top pane and the new clone are BOTH added to the content pane. i.e the top pane module is moved from the top pane to the content pane.

Expected result

Only the newly add clone should be in the content pane.

Additional context

We're not sure if it's related, but the import of a page with modules (previously exported) also seems to break the page.

Affected version

v9.4.1 release

@valadas
Copy link
Contributor

valadas commented Nov 18, 2019

Duplicates #2289

@valadas valadas closed this as completed Nov 18, 2019
@leedavi
Copy link
Contributor Author

leedavi commented Nov 19, 2019

I still get this issue in DNN9.4.1 ??

@Timo-Breumelhof
Copy link
Contributor

@leedavi it's closed because it was already logged see #2289

@leedavi
Copy link
Contributor Author

leedavi commented Nov 19, 2019

@Timo-Breumelhof Ah! yes, I saw the "Close" on 2289 at the bottom and wrongly assumed it had been closed, it'as actually been reopened.

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

No branches or pull requests

3 participants