Can't delete collection field entry

Design help CMS
1

Hi there,

I have a very weird situation, where I can’t get rid of collection field - I have checked project page inside and out and can’t seem to find the problem.

When trying to delete it, webflow tells me ‘connection is on project page’, but doesn’t tell me where is it. I looked up everywhere and can’t seem to find it!

See screenshot below:

Screenshot 2024-09-20 at 10.34.45
Screenshot 2024-09-20 at 10.34.451008×522 34.3 KB

Can someone please help, or shall I get in touch with the suppor?

Here is the preview link

https://preview.webflow.com/preview/lucid-vision-cf?utm_medium=preview_link&utm_source=designer&utm_content=lucid-vision-cf&preview=a768144db0f9757197f6da13acc0ec2a&pageId=6553855ed5362ef4356d7482&itemId=6582d5a65943dd2a7a58903e&locale=en&workflow=preview

Here is my public share link: LINK
(how to access public share link)

2

Hi @Eugene_Soch !

Did you try clicking the arrow before the ic

on Projects Template?
It should expand and show you the connection

Like so

Screenshot 2024-09-20 at 14.01.16
Screenshot 2024-09-20 at 14.01.16938×250 6.84 KB

On hover on the connection, you’ll also get the option to disconnect (if possible) and the eye to take you to the element

Screenshot 2024-09-20 at 14.02.42
Screenshot 2024-09-20 at 14.02.42954×250 7.1 KB

3

I did and that’s the thing - it doesn’t expand! It should normally expand to show me what’s in there, but it doesn’t!

4

hmm…

did you manage to remove it? Because I can’t find Next Project field

5

I did!
It was a very weird one. In the end what I did was a bit risky, but did work out.

  1. I backed up the entire site, just to be safe.
  2. I went onto collection page and, copied entire page wrapper to clipboard
  3. Deleted everything from the collection page, but kept everything in clipboard
  4. Went on and removed the field from CMS
  5. Pasted the page back into editor
  6. Published it - it worked!

It’s a really strange one, as I have replaced layouts on the page prior to issue occuring and 100% sure new layout didn’t have that field referenced anywhere, but the error was still there! Luckily, it’s resolved :slight_smile:

Thank you for your help though! :)

1 Like
6

Good to hear that Eugene! :tada:

Sometimes things are just plain weird! :smiley:

I’d mark it as solved in case someone needs this info in the future

Cheers!!!

1 Like