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

Deleting origin won't delete translation and creates 'ghost' entries #2604

Closed
robdekort opened this issue Oct 7, 2020 · 2 comments · Fixed by #2623
Closed

Deleting origin won't delete translation and creates 'ghost' entries #2604

robdekort opened this issue Oct 7, 2020 · 2 comments · Fixed by #2623
Assignees

Comments

@robdekort
Copy link
Contributor

robdekort commented Oct 7, 2020

Bug Description

When you have a multisite and create a localised entry, deleting the origin doesn't delete the translation. This leaves unwanted ghost entries in your collection that sometimes you can't delete. I haven't pin pointed this yet.

If you delete this entry via the file system it will come right back if you refresh the CP until you've cleared the cache.

The remaining page still has an origin id of the deleted original.

How to Reproduce

  • Make a multisite
  • Add an entry
  • Publish a localised version
  • Delete the origin
  • Switch to secondary language view

Extra Detail

Possibly related to #1713

Here's a quick demo:
issue

You end up with:
Screenshot 2020-10-07 at 10 17 12

Download a zip of this demo here.

Environment

Statamic 3.0.16 Pro
Laravel 8.9.0
PHP 7.4.10
No addons installed

Install method (choose one):

  • Fresh install from statamic/statamic
@piljac1
Copy link
Contributor

piljac1 commented Oct 7, 2020

I also encountered the same issue multiple times and one of those times, I tried dragging the .md file directly in the trash and then when I reloaded the collection listing, I got a crash, so I went back in my file system and saw that either the Origin ID (or the ID itself, can't remember exactly) of the entry was caught in an infinite loop. I had to restart valet and I also ran composer dump-autoload (clearing the cache only like Rob did might have worked too) to get everything to work again.

@robdekort
Copy link
Contributor Author

Oh wow, that sounds like this weird thing I encountered this morning:

wtf

Maybe we're on to the source of misery here. That's nice :-).

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

Successfully merging a pull request may close this issue.

3 participants