You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using django-modelclone on several projects. It's great!
However... :-)
If I apply it to a model using DjangoCMS's Placeholder field, it dutifully clones the model instance with the Placeholder field. However, it creates an empty placeholder. This would be OK, EXCEPT that my stakeholders complain that they have to re-create (most of) the original page's content within the Placeholder field.
What would be ideal is to ALSO recusively clone the plugin instances (or I suppose to optionally do so). DjangoCMS ties plugin instances to the Placeholder field (and some plugins can have child plugins so it's not conveniently straightforward) so (unfortunately) you have to create additional records in those tables if you clone the original page.
(I realize that this is probably out of scope for this package, since not everyone using it also uses DjangoCMS, and frankly, Wagtail does a better job at storing the custom content metadata, but this is the real-world situation I'm in. I suppose I could write my own cloning function, but that would mean mostly re-inventing the wheel just to get the enhanced functionality. But perhaps there's something in the existing package I'm missing.)
The text was updated successfully, but these errors were encountered:
I'm using django-modelclone on several projects. It's great!
However... :-)
If I apply it to a model using DjangoCMS's Placeholder field, it dutifully clones the model instance with the Placeholder field. However, it creates an empty placeholder. This would be OK, EXCEPT that my stakeholders complain that they have to re-create (most of) the original page's content within the Placeholder field.
What would be ideal is to ALSO recusively clone the plugin instances (or I suppose to optionally do so). DjangoCMS ties plugin instances to the Placeholder field (and some plugins can have child plugins so it's not conveniently straightforward) so (unfortunately) you have to create additional records in those tables if you clone the original page.
(I realize that this is probably out of scope for this package, since not everyone using it also uses DjangoCMS, and frankly, Wagtail does a better job at storing the custom content metadata, but this is the real-world situation I'm in. I suppose I could write my own cloning function, but that would mean mostly re-inventing the wheel just to get the enhanced functionality. But perhaps there's something in the existing package I'm missing.)
The text was updated successfully, but these errors were encountered: