• Resolved ghp123

    (@ghp123)


    Hi,

    I know it’s long overdue so I am trying to update from version 2.3.2. to version 3.3 but I can’t get it to work.

    If I try to do just the update then I don’t see any of my fields and I read somewhere to do an export and import but the export button does not do anything for me.

    Any idea how to get my to the newer version?

    Greetings,
    George

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Alex Prokopenko / JustCoded

    (@aprokopenko)

    Hi. When you upload a new version of a plugin – do you see a migration notice in your Dashboard?

    The upgrade process is something like this:

    1) Backup the database and field settings if you have them in json.
    2) Replace just custom fields plugin folder with newer version
    3) Open your dashboard – you should see a Migration notice.
    4) On Migration page you will see patches to be applied and possible problems you may have with your current fields.
    5) After migration you should see fields back.

    Thread Starter ghp123

    (@ghp123)

    Hi Alex,

    I do not get a migration notice ??

    I do not know if I have them I json either (don’t even know what that is ?? ) so I did everything you said above with the exception of option 1 (not clear how to do that).

    Any other ways of doing this?

    Thanks,
    George

    Plugin Author Alex Prokopenko / JustCoded

    (@aprokopenko)

    Unfortunately, it’s hard to comment w/o check the site.
    Can you roll back and provide me a link to admin panel to check your fields before update?
    Database access will also would be great.

    You can write to me on Skype (username ab.prokopenko). It’s not secure to post such info here ??

    Thread Starter ghp123

    (@ghp123)

    Thanks Alex, I send you the info on Skype

    Plugin Author Alex Prokopenko / JustCoded

    (@aprokopenko)

    I found the problem in your DB dump. For some reason there is an entry inside wp_options table, which used to store new fields format in versions 3+.
    That’s why plugin thinks your database is up to date.

    Solution:
    You should check an entry with option_name = 'jcf-fields'. It has serialized object inside, but if you have problems and didn’t migrated anything – it will have only empty serialized object (or object with empty post type arrays). Like this (can be a bit different, but you should not see any fields here):

    a:1:{s:4:"post";a:0:{}}

    If it’s empty – it’s safe to delete it. You should also delete an option, which indicate current JCF DB version state, which appears in v3+.

    You can use these SQL commands to delete unnecessary options:

    DELETE FROM wp_options WHERE option_name = 'jcf-fields';
    DELETE FROM wp_options WHERE option_name = 'jcf_storage_version';

    After than you should see the Migration notice and complete the migration process.

    Thread Starter ghp123

    (@ghp123)

    Thanks Alex for all your help, it now works perfect.

    It’s always nice when a developer takes the time to offer support when needed.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Upgrade from 2.3.2 to 3.x’ is closed to new replies.