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

Writer field content deleted, when renaming page slug #6507

Open
FynnZW opened this issue Jun 25, 2024 · 4 comments
Open

Writer field content deleted, when renaming page slug #6507

FynnZW opened this issue Jun 25, 2024 · 4 comments
Labels
type: bug 🐛 Is a bug; fixes a bug

Comments

@FynnZW
Copy link

FynnZW commented Jun 25, 2024

Description

When a page slug is renamed, the last writer field on the page gets it's content deleted.
Saving then will lead to content loss (very possible if that field is out of view).

Screenshots

342869783-6d0d6bbd-7c86-488d-a654-be54bcd8d1b7.mp4

To reproduce

  1. Rename a page slug on a page with a writer field

Your setup

Kirby Version
4.3.0 (also tested with 4.2.0 and 4.1.0.)
Tested with a fresh kirby plainkit and no plugins.

Your system (please complete the following information)

  • OS: macOS 14.5
  • Browser: Chrome Version 126
  • local server: Laravel Valet 4.7.1 (4.6.1 also tested)

Additional context
Might be connected to #6506

@FynnZW FynnZW changed the title Writer field content deleted, when page slug is rename Writer field content deleted, when renaming page slug Jun 25, 2024
@medienbaecker
Copy link
Contributor

medienbaecker commented Jun 27, 2024

Possibly related to these issues: #6351 and #5659

We also have a similar issue with the Markdown field: fabianmichael/kirby-markdown-field#164

@FynnZW
Copy link
Author

FynnZW commented Jul 2, 2024

Interesting, really seems to only happen on very fast connections, must be some kind of race condition. I'm also seeing my bug locally using Valet as a dev server (I'll add that in the bug description), doesn't seem to happen on a real production server so far.
Edit: Just updated my Valet installation from 4.6.1 to 4.7.1, bug still present

@distantnative
Copy link
Member

I can reproduce this. For me it seems to happen so far always to the last writer field on the screen. Is this something you can confirm from your experience too @FynnZW?

@distantnative distantnative added the type: bug 🐛 Is a bug; fixes a bug label Jul 21, 2024
@FynnZW
Copy link
Author

FynnZW commented Jul 21, 2024

I can reproduce this. For me it seems to happen so far always to the last writer field on the screen. Is this something you can confirm from your experience too @FynnZW?

Yes, it seems to be always the last writer field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug 🐛 Is a bug; fixes a bug
Projects
None yet
Development

No branches or pull requests

3 participants