Closed gchokeen closed 9 years ago
@gchokeen You can actually do this by simply specifying the CSS selector route down to the .clone
element. As you can see in the source, the cloneButton
config value is just appended to the toClone
selector. So you can do something like:
$('.clone-wrapper').cloneya({
cloneButton: 'div.card > div.card-head > div.tools > div.btn-group > a.clone'
})
Yep, that's extra effort, but it still make sense!
In the lastest plugin release 1.0.0, cloneya using child-selector for all the delete & clone button. It making us to use strict & standard structure, is it really required?
When I work accross the bootstrap form, I faced problem below structure
This one solved
Do you think it's really important to do that!