djangocms_link/djangocms_picture to djangocms_frontend migration

[aacimov]

Is there a chance there will be a migration script for djangocms_link and djangocms_picture plugins which are, by my honest opinion, most used on lots of Django CMS based websites?

At the moment I am in a process of migrating the old Django CMS v3 with mentioned plugins (amongst others) and it would be a great option to migrate those to djangocms_frontend by ease. I must point out there is lots of data in the database I am migrating and only these 2 give me headache.

If not, are there any simple steps to transfer it easily (preferably with example)?

Thanks a lot!

[fsbraun]

Currently, there is no migration script for Link and/or picture plugins. However, it may not be difficult to create them: https://djangocms-frontend.readthedocs.io/en/latest/how-to/migrate-3rd-party-plugins.html The only difficulty I see, is that djangocms-link and djangocms-frontend use the same name for the link plugin. For the migration process the original link plugin might need to be renamed.

I'd suggest to look at:

• https://github.com/django-cms/djangocms-frontend/blob/master/djangocms_frontend/management/styled_link_migration.py might be easily adaptable to create the migration rules for the link plugin

• djangocms-frontend/djangocms_frontend/management/bootstrap4_migration.py

  Lines 212 to 239 in f11feee

  	"bootstrap4_picture.Bootstrap4Picture -> image.Image": [
  	"template",
  	"external_picture",
  	"width",
  	"height",
  	"alignment",
  	"caption_text",
  	"link_url -> external_link",
  	"link_target",
  	"link_attributes",
  	"use_automatic_scaling",
  	"use_no_cropping",
  	"use_crop",
  	"use_upscale",
  	"picture_fluid",
  	"picture_rounded",
  	"picture_thumbnail",
  	"link_page -> internal_link",
  	"picture",
  	"thumbnail_options",
  	"use_responsive_image",
  	"attributes",
  	"P001",
  	"A001_picture", # fix alignment
  	"M001-m", # MarginMixin
  	"M002", # ResponsiveMixin
  	"T001_PICTURE",
  	],

  might give a good idea of the rules needed for djangocms-picture.

Just be sure to make tests on a copied database first, where data loss would not matter.

Please let me know if I can assist with specific questions! This should be doable! 🚀

[aacimov]

@fsbraun thanks!

I will definitely look into it. If I manage to do a migration process I will definitely share it.

Best regards.

[aacimov]

Ok, I think I mapped the fields right but since bootstrap4_migration.pyis a subcommand it would be very helpful to point me in the right direction on how to do it as a standalone (single) command. Just a general bootstrapping of the command itself since there are lots of different methods in different files and it is giving me a hard time switching from different files "catching" the logic. I am afraid I could miss something.

I am working in a test environment of course, but still it would be very helpful.

[fsbraun]

Hi @aacimov !

If you have a mapping, put it into a file and in your settings.py set

DJANGOCMS_FRONTEND_ADDITIONAL_MIGRATIONS = ["dotted.path.to.your.migration.mapping"]

Run manage frontend migrate and see if it works.
If you do not want the djangocms-bootzstrap4 migrations to run, remove "djangocms_bootstrap4" from you INSTALLED_APPS and they will stay unaffected.