ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Upgrade problem with nGen file field

May 10, 2011 12:48am

Subscribe [5]
  • #1 / May 10, 2011 12:48am

    roryrabbitfield

    320 posts

    I just upgrade from EE 1.x (I think it was 1.6.8) to 2.1.3. The site had been using the nGen file field fieldtype. Now, my site doesn’t work at all, I get this message when I got to my site:

    Error
    Unable to load requested field type file:  ft.ftype_id_1.php.
    Confirm the fieldtype file is located in the expressionengine/third_party/ directory

    I have some sense that the old nGen file field stuff needs to be converted to the new, native file field, but I have no idea how to do this. Please help!

  • #2 / May 10, 2011 10:33am

    Sue Crocker

    26054 posts

    Hi, Rory. I’d convert the 1.x site to use a textfield for now then convert to either File or SafeCracker File when you get over to EE2.x.

    Make sense?

    I’ve never used nGen, so this is a best guess. You could also talk to Brandon about what he recommends converting to.

  • #3 / May 10, 2011 6:36pm

    Sean C. Smith

    3818 posts

    Rory,

    On twitter I linked to my blog where the last paragraph essentially says the same thing Sue said - convert the ngen field to a text field.

    One of the keys to success was that all ngen file fields had to be converted to text fields before the upgrade as did any other non-standard EE field. Once the upgrade was completed, I then enabled all addons and went into the field settings and reset all fields to the correct field. Once that was done the upgrade was completed. Not getting that step done resulted in having to revert to EE1.6.x and redo the upgrade several times before I finally got everything nailed down.

  • #4 / May 10, 2011 9:57pm

    Sue Crocker

    26054 posts

    Thanks for the assist, Sean.

    Rory, does the info from Sean help?

  • #5 / May 15, 2011 12:36pm

    roryrabbitfield

    320 posts

    Very helpful. I read Sean’s post, which should be required reading for anyone doing a 1 > 2 upgrade! I got some help from someone on twitter who bailed me out, and it was not necessary for me to revert back to the 1.x setup in order to fix it since he did some magic stuff (my way of saying I don’t know what he did). So, I’m all set.

  • #6 / May 15, 2011 1:57pm

    Greg Salt

    3988 posts

    Hi Rory,

    Excellent, glad that you got this figured out.

    Cheers

    Greg

    @Sean, thanks for the help.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases