Updating from beta 45 to 3.15.1 causes duplicate entries for page when publish or draft with same id

[stefanfritschej]

Describe the Bug

The project is setup with mongo db. It has some custom collections for different pages. The collections use a beforeValidate hook to add slug automatically.

After updating when exisiting page is published or saved it gets duplicated with same id. The two pages are connected - when you select one of the pages both get selected and also if you do some changes, changes are on both sites. In database there is only one entry. So it seems like it's more like a display error? Happens with all pages regardless if custom or just default pages.

Found this issue which seems like kinda same like mine. Was there any solution to this topic?
#8430

Link to the code that reproduces this issue

No response

Reproduction Steps

1. Init project on beta.45
2. Create and publish pages
3. Update to 3.15.1
4. Edit already existing page

Which area(s) are affected? (Select all that apply)

area: ui, area: core

Environment Info

Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  payload: 3.15.1
  next: 15.1.4
  @payloadcms/db-mongodb: 3.15.1
  @payloadcms/email-nodemailer: 3.15.1
  @payloadcms/graphql: 3.15.1
  @payloadcms/live-preview: 3.15.1
  @payloadcms/live-preview-react: 3.15.1
  @payloadcms/next/utilities: 3.15.1
  @payloadcms/plugin-nested-docs: 3.15.1
  @payloadcms/plugin-seo: 3.15.1
  @payloadcms/richtext-slate: 3.15.1
  @payloadcms/translations: 3.15.1
  @payloadcms/ui/shared: 3.15.1
  react: 19.0.0
  react-dom: 19.0.0
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:11 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 10

[github-actions[bot]]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@beta -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload

[DanRibbens]

Hi @stefanfritschej, I moved this from an issue to a discussion since it was already covered with #8430 that you linked.

You should be able to resave your documents and it will remove the latest: true property from the versions collection that is used to show in the list.

If that doesn't work you might need to manually update records with the same parent_id and multiple latest: true to remove one in order to solve this.

[stefanfritschej]

Thanks for the fast reply. Save alone couldn't fix the problem, but updating it manually works.