Open mvdesign opened 7 years ago
Did you ever get this resolved? I ran into the same basic issue today.
@sburris777 I didn't get an actual fix in the module itself, but I did find what seemed to be triggering it: a required relationship field.
When I turned off the "required" setting on the relationship field, the error message went away and the entry cloned as expected. You might also need to clean up the database a little bit first to remove the problematic rows in exp_category_posts
.
Hope that helps!
Apologies @sburris777 I am working on a rather large issue with SC at the moment so I will try to bundle a fix in with the next update
Thanks @mvdesign and @ThorntonStuart appreciate the feedback. I'll try those couple of fixes and see if that does the trick.
I have one channel that does not clone when requested (or generate an error message for the first attempt). This is the same channel as my previous issue. When I then try a second time to clone the same entry, I get the following error message:
Entry 78 already exists (in a different channel that doesn't use that category group). When I look at
exp_category_posts
, it has created new rows for entry 78. When I remove the new rows for 78 and try to clone the entry again, it adds the rows back intoexp_category_posts
. When I try to clone the entry yet another time, I get the Duplicate entry error again.Entry 78 is the most recent entry created on the site. When I create a new entry in another channel, the Duplicate entry error (and the database) indicates that SimpleCloner is trying to create the categories for the very newest entry.
If it helps, this channel has two category groups and the following field types:
Here is the stack trace for the error message: