1

I am in process of upgrading EE2 site to EE5.

One of the fields is Content Elements, and since it does not seems to be available for EE3/4/5, I'm thinking that best approach would be to convent it to Fluid field.

Has anyone went through the process before? Maybe there is some script that can be used? If not, what would be the best approach here (other than manually copy/pasting each entry)

  • Hey Yuri, did you have any success? Do you have any insights you can share (i.e. SQL code) ;-) – Adam Rifat Mar 3 at 13:30
  • I've ended up manually copying content, as it appeared only few entries were actually using that field – Yuri Salimovskiy Mar 3 at 18:25
2

I have done this sort of migration a couple of times and it is doable but not straightforward. Broadly you have to first get your old site to dump out the content of the field for each entry concerned in a format you can work with (i.e. some kind of structured file) and then create an appropriately capable fluid field and write some SQL to insert this information into your database using the new fluid field definition.

Because the fluid field is relatively new there are no utility add-ons available to make this process easier, and so you have to construct your approach to processing this as a custom exercise.

Whether it is worth the effort depends very much upon how many entries you are seeking to migrate... and how complex each entry is likely to be.

So, in summary, doable but non trivial.

HTH

| improve this answer | |
  • Any recommendations for exporting the original field into "format to work with"? – Yuri Salimovskiy Jul 9 '19 at 6:42
  • It depends a bit on what you prefer when it comes to building the templates to construct the new fields, but for want of something better html_encoded CSV works OK. – JCOGS Design Jul 9 '19 at 9:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.