With the new update you can setup classes in animations which will span any page: https://webflow.com/feature/reusing-interactions-just-got-way-easier
1 Like
Even after the recent “reusing interactions” post. I still observe the same issues as above.
New project
Create brand new project.
Original Page
- Add single h1, and give it a class name.
- Add interaction on page load start to set initial opacity to 0, target by class.
- Add interaction on page load done to set opacity to 100%, target by class.
Works when triggered from “Preview” button in interaction pane, preview mode (eyeball) and upon publish outside the app.
Duplicate Page
- Duplicate page
- Interactions are duplicated (others have said due to new ids)
- Reassign interactions on new page to initial set of interactions
- This should be fine because the trigger is class based and should, according to the recent post, work across pages.
- Delete old interactions
Works in “Preview” button click in interactions pane. Doesn’t work in page preview or upon publish. Only on duplicate page. Original page still functions fine.
https://preview.webflow.com/preview/interactionstest-206475?preview=a5985e146066a1d7df175ffc75929952
1 Like
Same problem here…
Not to mention the previous feature that allowed us to assign an interaction to another set of class is no more available…
Thanks for pointing this out! We’re looking into it.
Yeah we’re deprecating this re-use mechanism because it was a very manual process. Now that you can target classes it makes reusing animations a lot faster and easier.
Absolutely, you’re moving in the right direction.
The problem is for now the new mechanism is not working properly and the old one is not available anymore.
For now the solution I found is to duplicate interactions and retargeting the elements.
Keep up the good work. Webflow is still amazing 
Looks like the page duplication issue is only for Page Triggers. We’re working on a fix!
2 Likes
We pushed a fix for the Page Triggers. Let me know if you’re still affected!
Note: it will still be broken for previously-duplicated pages. For those pages you’ll need to add the page trigger and choose the animation manually.
I’m still having an issue…
For exemple : I have an interaction that automatically closes the search field if user is scrolling while leaving the field open…
You can see it working well on home page (not a duplicate page) : http://viviany.webflow.io/
Not working on a duplicate page : http://viviany.webflow.io/auxiplus/le-domaine-de-bellevue
Read only link : https://preview.webflow.com/preview/viviany?preview=c42da62c6157b57cb27552628d3c0d57
I was able to duplicate the page and the interaction worked. Wondering if you can even delete the duplicated animation and use the original one because the element is in a symbol (elements inside of symbols have the same ID no matter what page they’re on, so you can target them using “Selected Element” option for the action).
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.