Closed ScapersClub closed 1 month ago
some additional info
localization: {
locales: ['en', 'fr']
defaultLocale: 'en',
fallback: true,
}
...
?locale=en
in the url of the edit form is not exist, the form value shows the secondary locale content rather the the default locale. If editor clicke save button, the "en" content will be overrided by the "fr" content?locale=en
is exist and the form shows the correct locale contentpayload: 3.0.0-beta.67 next: 15.0.0-canary.74
@jentzheng I am not following, am I missing something in my screen recording?
https://github.com/user-attachments/assets/e25d6230-4283-49a1-8231-ee6e942eb8af
https://github.com/user-attachments/assets/1ad4b1f1-0e1d-47ea-a90d-913b6e4abd67
@JarrodMFlesch It seems the admin nav link is not getting the current locale and it always shows the non default locale content after first clicked.
"next": "15.0.0-canary.77",
"payload": "3.0.0-beta.68",
"@payloadcms/next": "3.0.0-beta.68"
"@payloadcms/db-postgres": "3.0.0-beta.68"
@jentzheng can you clear your node_modules, delete your pnpm-lock file, and then re-install deps? I am unable to replicate anything like this. If you want to link to a repository that I can boot up to replicate we can continue.
@jentzheng I am not following, am I missing something in my screen recording?
CleanShot.2024-07-22.at.10.30.40.mp4
I am experiencing a critical bug while using Payload CMS, particularly when editing complex pages with many fields, such as uploads and block types. The issue occurs frequently and is especially prevalent when multiple users are editing the same or different pages simultaneously. This bug results in significant data loss, as the work done is not saved and effectively "dead."
To reproduce the issue, create a complex landing page with numerous fields and blocks, similar to the payload page. When more than one user is editing a few pages, or even when a single user is working on a complex page, the bug occurs often, leading to lost work.
This issue is critical as it causes substantial disruption and loss of time when filling out content. Immediate attention and a fix would be greatly appreciated.
@jentzheng I am not following, am I missing something in my screen recording? CleanShot.2024-07-22.at.10.30.40.mp4
I am experiencing a critical bug while using Payload CMS, particularly when editing complex pages with many fields, such as uploads and block types. The issue occurs frequently and is especially prevalent when multiple users are editing the same or different pages simultaneously. This bug results in significant data loss, as the work done is not saved and effectively "dead."
To reproduce the issue, create a complex landing page with numerous fields and blocks, similar to the payload page. When more than one user is editing a few pages, or even when a single user is working on a complex page, the bug occurs often, leading to lost work.
This issue is critical as it causes substantial disruption and loss of time when filling out content. Immediate attention and a fix would be greatly appreciated.
Hey @383bd03d! Feel free to open an issue with a link to a reproduction and we can check it out š
On another note, please do not attempt to hijack other users issue threads with unrelated comments.
@ScapersClub My db initialized since Payload beta.4x, try to delete the duplicated locale
record in your db's table payload_preferences
then it should solve the issue.
Link to reproduction
No response
Payload Version
58-67
Node Version
latest
Next.js Version
recommended
Describe the Bug
When editing collections with localization, occasionally, for example, the en localization may be saved into the de localization and vice versa. As a result, the en and de localizations end up having identical content.
This may also be related to the use of upload fields (relatedTo: media), and when a file is uploaded through this field, we get an error in the Node.js console each time:
Reproduction Steps
It is not exactly known what causes this bug; it just happens from time to time.
Adapters and Plugins
db-mongodb storage-s3 richtext-slate