-
Notifications
You must be signed in to change notification settings - Fork 5
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
Not working with clone field #2
Comments
I got a bit further, I looked into the problem and found out that the keys (field.data.key) needs to be different. Changed script.js: ` if(acf){
} ` |
Back again with my own solution to the problem. I figured it out now completly. |
I have a similar problem that your fix doesn't help with. If I hide a flex layout that contains only one clone field, the following fields are "messed up" or show values from the previous field. I couldn't put together an easy to understand test scenario yet. Hope to deliver this in the next days. |
@mjot we have pushed the latest changed that should fix this issue with cloning fields. |
@harunbleech Thanks for the notification, I will test it tomorrow and give you Feedback here. |
@harunbleech Are you sure that your latest push is fixing problems with cloning fields? I can see that there are just some CSS changes in your commits. |
@mjot The clonefield fixes were fixed done before this release I think. |
You have any console errors? |
Sorry, I removed my comment, since it was more on topic for issue #1 |
I called a collegue of you today and he said to me to put it here.
We have set up the flexible content to be used on pages. We reuse this with a clone field on posts and other post-types. But it seems it doesn't work on clone fields.
Somewhere / somwhouw it doesn't save / load the rows.
I realy want to use this plugin, but at the moment I can't because of this. Can you guys take a look at this?
The text was updated successfully, but these errors were encountered: