Streaming live at 10am (PST)

Copying new Interactions causes "element no longer exists in your site" error

Yeah Mark,
I hear ya on this one. I luckily found out after creating a simple one and noticing it after the fact. Sorry about the work you put in, I feel ya. You can contact me if you need any help to get things finished. It’s always good to have a resource to use when you need to. I hope you can get things straightened out for completion.

As well, try to take a minute before going off online. They will definitely take this criticism and apply to future developments. Features are always a catch-22, and complicated when it comes to a wide range of consumer needs. You don’t want go low, maintain your integrity, and don’t bring bad energy on your growth - besides when you get through this - with all the challenges; you will get more satisfaction knowing the struggle it took. Looking back, your appreciation for winning despite the hurdles, will give you extreme confidence in the future! I truly believe this.

Hold back for just a bit, and let your spirit rest. You’ll be more proud of your accomplishements when all is said and done. Let’s finish the story, it’ll make you happier if you hold back.

From a fellow developer - Hang in there!
G.J. Hunter


Hi Gary,
I’m sure that’s good advice. Unfortunately, that WAS me “holding back”. You should have seen the first draft!


Ok ok, you got a point, I just read the first statement, and saw the restraint. Well I’m here to help if you ever have a question about design or dev options. I’m a community member so I don’t charge or anything.

So what’s the status now? What phase are you in with the site project? Give shout out to my profile at anytime.


I do sincerely appreciate the support. Thank you!

You got it! No prob… have a good weekend! Cya

@garymichael1313 @Mark_Stevenson @anthonysalamin @dennis @pritchettnick

New announcement indicates it’s fixed:

Haven’t tried it myself yet. If you try it, please report your results here.

Thanks, @MarkBult for letting us know.

I just tested it, and yes, it copies the interaction now properly to a new subpage. Even though I still had to re-enter the “replace with:” class. But I can live with that; it’s not too much of an effort to quickly type in the class that’s displayed above anyway.

But … now the classes get removed from the original page. So the initial problem now shifted from, the interaction not being properly copied to the new subpage, to the interaction being moved to the new subpage and removed from the original page.


Removing the interaction from original page doesn’t seem like intended behavior. @Brando can you respond to this?

@MarkBult @dennis

Thanks for pinging me on this!

You are correct — this is not intended behavior. We are pushing a fix for this soon!

I really appreciate your patience with the new interactions feature and your help in reporting the issues in this thread! You’ve all definitely helped us make improvements to this feature and we are grateful.

@Mark_Stevenson sorry to hear you had such a frustrating experience — please know that we hear your frustrations and appreciate your honest feedback. I hope the recent update of symbol support for Interactions 2.0 helps you finish up your project without anymore hiccups.

Thanks for offering support @garymichael1313 :fist_right: :fist_left:

As always don’t hesitate to reach out with any questions.

I’ll post an update about the fix we are pushing as soon as I hear back from the team on it.


@MarkBult @dennis

We just pushed a fix for this.

Now if you copy/paste an interaction with “replace elements with” and a class name set, the original will remain intact as expected.

Can you please refresh your designer and test this on your end to confirm the issue is resolved?

​Thanks in advance!


Great, thanks @Brando for getting this problem tackled so fast.

I have just done some testing. When I copy an element with an interaction to another page, everything stays intact on the original element now. The copied element also gets copied onto the new page in a way that it’s correctly functioning (including the correct “replace with” classes).

The only thing remaining now is that the interaction settings of the copied interaction are saying that the element affected by interaction does not exist on this page. If I wanted to make adjustments to the copied interaction, I would have to enter all the values of the interaction for an element again before I can modify it (screenshots below).

Not sure if that is working like it is supposed to at this moment and will be optimized at a later stage. But at least it’s possible now to build interactions and copy them to another page in a functioning matter.


1 Like

Thanks for bringing this bit up @dennis. At this point, this is expected behavior.

The reason you see the Element does not exist on this page notification is because copy/pasting elements actually creates a different node ID completely. So the original node only exists on it’s original page.

This is where the Replace element with class name comes in. The action list doesn’t show the elements being affected because the animation is no longer applied to the same element — instead it is applied to the class name associated with that element.

We are discussing this further internally to identify how we can improve this piece of IX2. I’ll keep you all posted if we start making more changes.

1 Like

I assume the obvious way is to be able to update the missing piece manually pointing it to the correct object? If similar interactions on different pages are considered different entities (I think so) that is.

No problem. Thanks @Brando for helping us out with this!

1 Like

^ I wanted to edit my comment but ended up deleting it >_<

But after looking into this behavior with reusing interactions on other pages, I think I understand the behavior pretty well now.

Although, it is a little confusing how the Warning will show up if you use the interaction on another page with the same class, but the Warning won’t show if you Duplicate that page instead. I would think that IX2 would treat both situations as different node IDs and display a Warning for both.

1 Like

It is because interactions are dependant on id only when you create them. You can totally give another object the same class and it won’t be affected. Unless you tell IX explicitly to target that class.

I assume when you duplicate a page the id’s of all the objects stay the same.

1 Like

Yeah this may be expected behavior at this point, by a Product Manager’s definition, but it’s certainly not yet resolved to be expected behavior from a user’s standpoint.

Thanks @Brando for the clear communication, but I’m chalking this one up still as WIP.

Thanks also to others for continuing to relay your experiences and suggestions.

3 Likes I hope the Webflow team will come with improvements here. You could consider this “Element does not exist ont this page” as a serious bug in my opinion. IX2 is very powerful: you can chain complex actions, but with the complexity the risk that you have to face a problem with this bug is becoming bigger. I have a typical complex interaction living on several pages in a new developed website, but today I encountered serious problems copying the interaction. I have been working quite some time on it, trying to circumvent the bug with no result. The best way is to duplicate the actions and apply the same styles on a different page to the action again.

Another remark: the interaction of the interactions 2 panel could be improved. When using a lot of (chained) actions with classes, the panel is becoming quite unclear with to much information is a tiny part of the browser window.

1 Like

Agreed. As I said before, this may be “expected behavior” only from the perspective of the Webflow internal Product team. To the users, this is confusing and consternating, and not at all how we expect this feature to work.

Hi @rich_art @MarkBult

Thanks for posting your feedback to this thread.

I have some good news for you! We have an update coming down the pipe that will address the concerns you outlined above.

I’m not able to give an exact ETA quite yet, but when pushed the update should help alleviate some of these pain points.

Thanks for your continued support :slight_smile: