Thread

I use Mark Huot’s file fieldtype in a EE 1.7.1 install and if I keep the fieldtype as is, then I go ahead and do the upgrade to 2.2.2, will it halt the upgrade once it sees the fieldtype of “file” in the database table, or will it keep going without changing the fieldtype?

I ask, because since there is a native file fieldtype in ee 2, and the filedtype name in the table column is also “file”, would it just automatically sync over (I don’t care about the {filedirer_#} changes I’d have to make to the exp_channel_data table, I just want to know if that will halt the upgrade process if it sees the fieldtype “file” in a ee 1.7.1 database?

Hi bkmorse,

What happened with this site that you recently upgraded. From the thread it looked like you got there in the end. Is that not the case?

I have not had to upgrade a site with those third party fields previously so I can’t comment on that that specifically.

From reading threads after searching though most users mention converting the field to a text field before updating and then enabling the native Field field after update which looks like the route you took in your previous thread.

Does Mark have any info on how to deal with it? Did you try and contact him?

I was able to upgrade to 2.2.2 from 1.7.1, I want to know if I revert back to 1.7.1, leave the file fields as is (instead of changing them to text fields), would the 2.2.2 upgrade halt once it saw file fieldtypes in a 1.7.1 install?

Hiya,

When you say above you were able to upgrade to 2.2.2 from 1.7.1 is that another site you are referring to or the site you are currently trying to upgrade?

I only ask as you then mentioned reverting back to 1.7.1? I’m not quite following what you mean by that. Are you going to take a 2.2.2 site and somehow change it back to a 1.7.1 install?

With regards to leaving the field as is, myself like John, I don’t know what this will do. You could perhaps perform a quick test on a local install and see what happens maybe?

That said the best solution with 3rd party field-types of that nature is to convert them to text first so that the system totally recognises them. This usually gets rid of any problems then.

Is there any reason why you don’t want to convert them to text fields first?

Thanks,

Mark

The reason I want to know whether or not the upgrade will halt when it sees a file fieldtype in the database table is because if I convert to text, then I’d have to go into the database (or CP) and assign them back to file fieldtypes.

This is a 220+ channel website with many file fieldtypes, I was trying to see if I could save time by upgrading w/ the file fieldtypes not being changed to text prior to upgrade w/o it halting. I know I’ll probably have to set them to the correct {filedir_} after upgrading, but for a 220+ channel site, it’d save me a couple hours.

Hiya,

Ah okay I see your reason for asking now.

As said before I’m really not sure on this as I’ve never migrated any sites with Mark’s fieldtype in it to 2.x

Is it possible for you to do a test on a very quick localhost install and see how that goes?

As this is a 3rd party add-on though we may need to move this thread down to the Community Help forum where hopefully other users may have come across this before and can chime in to offer some help if that’s okay?

Thanks,

Mark

Yes, please move.

Was hoping to avoid testing it myself and see if anyone else had tried it and had an answer for me, thanks!

Hiya,

Okay I’ll move this on down to the Community Help forums. Hopefully someone has already done this before and can let you / us know the answer to this one.

Cheers,

Mark

I can tell you that the installer will not automatically convert third-party fieldtypes to equivalent EE fieldtypes.  So you’ll need to do something with the data.  That ‘something’ depends on what happens if you do something like make one of those custom fields “text input”.  But you’ll definitely need to play with this in a dev environment and come up with a plan to convert that data.

I’ve converted EE 1.7.1 to EE 2.2.2 with “File” type fiels from Marc Huot’s add-on.

You do need to
1) Make sure that every ‘File’ field contains only a single file name (Marc’s “File” add-on used had the possibility of multiple files in one field that has no easy equivalent with more current File add-ons) and note what file directory it’s linked to
2) Upgrade
3) change the field type and set the preferences for that field type properly to the 2.2.2 field_type, and set the settings for each field.
4) add the proper {filedir_###} to the beginning of each field

It’s not QUITE able to be scripted, because of the preference-setting necessary at step 3—or rather, that’s a little too complex for me.

TTFN
ravis

UPDATE exp_channel_data SET field_id_365 = Concat('{filedir_29}', field_id_365) WHERE (channel_id = 95 AND field_id_365 != '')

This adds the filedir_29 to the beginning of each filename in the appropriate field_id of exp_channel_data

I wonder if there is a way to remove all data after the first line in those certain fields, because of the multiple data it contains from Marc’s file fieldtype, it would make the process quicker.