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

CopyView stopped to work for Snippets on Wagtail 6.1 #11940

Closed
ducolares opened this issue May 10, 2024 · 3 comments
Closed

CopyView stopped to work for Snippets on Wagtail 6.1 #11940

ducolares opened this issue May 10, 2024 · 3 comments
Assignees
Labels
Milestone

Comments

@ducolares
Copy link

Issue Summary

The copy functionality for snippets isn't working in Wagtail 6.1, although it works perfectly for pages.
I tested with a downgraded version, and it works fine.

Steps to Reproduce

  1. On Wagtail CMS, on a Index View, try to copy a snippet instance.
  2. The form fields are blank on the CopyView.
  • I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: (yes / no)
    Yes

Technical details

  • Python version: 3.9
  • Django version: 4.2.6
  • Wagtail version: 6.1
  • Browser version: Chrome 124
@ducolares ducolares added status:Unconfirmed Issue, usually a bug, that has not yet been validated as a confirmed problem. type:Bug labels May 10, 2024
@laymonage laymonage removed the status:Unconfirmed Issue, usually a bug, that has not yet been validated as a confirmed problem. label May 10, 2024
@laymonage
Copy link
Member

laymonage commented May 10, 2024

Thank you for the report! I can confirm this issue exists (and for ModelViewSet as well). It's a regression in ee57f6d and (e1728f6 for stable/6.0.x). We'll pick this up for 6.1.1.

Not sure if we'll put out a 6.0.4 release though, as it's technically out of support.

@nqcm
Copy link

nqcm commented May 16, 2024

I am testing it wit Wagtail 6.0.3 and the copy functionality is not working. It was working perfectly fine in 6.0.2

@laymonage
Copy link
Member

laymonage commented May 16, 2024

Hey @nqcm, thanks for the report. The fix was backported to the 6.0.x branch and we'll put out a 6.0.4 release along with 6.1.1, hopefully some time within the next week.

I'll close this issue for now, as the fix has been merged in #11943.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

3 participants