Recommended migration path from Joomla/VM 3 to Joomla/VM 4


  • Default avatar
    stefan7    
     8 months ago
    0

    Hello Seyi,

    is there a documentation for the recommended upgrade path to Joomla 4?

    I deactivated AwoCoupon in Joomla 3 and migrated to Joomla 4. On installing AwoCoupon 4.0.1.0 over the old version I got errors, so I removed the old folders.
    I am still getting the error:
    Unknown column 'image_config' in 'field list'

    Having a migration documentation from the beginning might help to avoid any issues.

    Regards
    Stefan
  • Your avatar
    seyi    
     8 months ago
    0

    Hello,

    Your tables are not updated.  Did you do this:

    - install a fresh copy of awocoupon on the joomla 4 site
    - delete all the awocoupon tables created
    - add the old awocoupon tables
    - load the awocoupon dashboard page, which should automatically upgrade the tables
  • Default avatar
    stefan7    
     8 months ago
    0

    Hi Seyi,

    thanks for the help. It works now.

    Initially I did the first step only, including deleting all folders, but it did not install.

    This time in the test environment
    - I deleted the old tables,
    - installed version 4.0.1.0
    - deleted the tables again.
    - updated the live site from an old AwoCoupon 2 to the provided version 3.x.
    - exported the awo tables from live.
    - imported to the new installation.

    This time the migration of the tables worked.
    Inbetween I tried to use the old AwoCoupon 2 tables as I found in the live store and got a spinning wheel forever.
    So it's important to upgrade the J3 install to your latest 3.x version I guess and then use those tables.

    If you pin a documentation like that somewhere, it could help to finish this faster.

    Thanks again for your quick help
    Stefan

  • Default avatar
    niko88    
     4 months ago  last edited 4 months ago
    0

    Hi there,
    in my case, after fully deleting Awopcoupon and tables and doing a fresh installation of Awocoupon 4 (4.0.1.1), I receive a "Specified key was too long; max key length is 1000 bytes". The hint suggested on https://awodev.com/forum/thread/item/14310 did not work here, so it seems to be another table causing this issue.
    Thanks for helping and documenting.
    Regards,
    Niko

  • Your avatar
    seyi    
     4 months ago
    0

    Hello,

    Get the latest version of AwoCoupon, 4.0.1.2.  With it, the above post should work without any tweaking:

  • Default avatar
    niko88    
     4 months ago
    0

    Good morning,
    also a fresh installation of AwoCoupon 4.0.12 without any old database tables results in "Specified key was too long; max key length is 1000 bytes". Let me know which logs I can provide for your analysis.
    Regards,
    Niko
  • Your avatar
    seyi    
     3 months ago
    0

    Hello,

    You would have to manually install the tables to find out where it is dying.  The table sql can be found in

    /administrator/components/com_awocoupon/awocoupon/libarary/linstall/mysql.install.sql

    You will need to change #__ to your actual table prefix.  Use phpmyadmin to install one table at a time.
  • Default avatar
    niko88    
     3 months ago  last edited 3 months ago
    0

    Hi,
    the error happens for both #__awocoupon and #__awocoupon_history. The other statements are fine. The first two tables can be imported when I change the column length from 255 to 200 for every relevant column.

    After that, the other steps went fine.

    Regards,
    Niko