Deleted Collections Keep Reappearing!

I’ve duplicated a project, deleted all Collection Items, unlinked everything and deleted a number of Collections.

I save my project and publish it…

But when I log back in, all those deleted Collections are back again!

When I deleted them I didn’t receive any errors since there is no longer any Collection Items.

How can I PERMANENTLY delete Collections?


Here is my public share link: https://preview.webflow.com/preview/golden-moments-temp?utm_medium=preview_link&utm_source=designer&utm_content=golden-moments-temp&preview=82707adabb0301ce37b6af024b561847&pageId=5e78dcf2b76187457572af84&itemId=5e7a43266e9f9a211771d4b8&mode=preview
(how to access public share link)

I have this issue at the moment also.

1 Like

Thanks @tom87

Has this always been the case or a recent thing? This is the first time I’ve needed to delete Collections.

This is the first time it’s happened to me. Seems like a new thing.

1 Like

Any help Webflow team?

Bumping this thread - I am having the same issue and it is very frustrating.

2 Likes

Thanks @Max_Richter

It’s really annoying when you’ve duplicated a project with 40 Collections but now only need 5.

Makes for messy working and confuses clients.

My problem is that it thinks I’ve reached the limit of CMS items on the Enhanced Staging site plan because I can’t remove the CMS collections that are empty and not in use.

I think this is the solution…

I reached out to support who said some of the Collection pages may still have connections.

After removing these connections, I was able to delete the Collection.

This makes it even more annoying in a way… Why allow me to delete a Collection if it physically can’t be deleted?!

1 Like

You’re right. Thanks for this. Must add that this only worked by manually deleting the elements on the page that were connected to the collection. Removing them via the ‘View Connections’ list meant the collection came back again.

It seems like the message that prevents us from removing a collection with connected items has erroneously stopped appearing hence us getting the same problem at the same time.