Difference between CSV-import and CSV-import beta

Support has been upgraded!



The Support Forum is closed. Not to worry!  Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.

Premium Support

Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?

Please open a Support Ticket in your user account.

Click here to open a support ticket.

Free Support

Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.

Please open a new support topic in the WordPress support forums for Connections.

Click here to open a support topic.

This topic is: resolved

Tagged: , ,

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • 07/05/2018 at 5:19 am #466868
    Age de Jong
    Participant

    Hi,

    Just purchased the extension pack and want to use the CSV import extension.
    Noticed in the downloads there also is a beta available.

    What are the differences and which one do you recommend?

    With kind regards, Age

    07/05/2018 at 11:19 am #466893
    Steven Zahm
    Keymaster

    @ Age

    I like recommending the beta which is more of an release candidate than a beta. Poor naming on my part.

    Some of the bigger changes include but limited to:

    • Made code changes to deal with a couple of the more common issues users have had using the extension. Minor things really but do improve the user experience.
    • Improved user feedback during the import process. Failed and skipped rows are now reported vs being silently ignored.
    • Failed and skipped rows will have download links to CSV files with just those rows so they can be fixed and imported.
    • When importing really large CSV files, eg. 10,000 or more, each step of the batch import would increase as the complete file would have to be parsed to get to the correct spot to import the next batch. Now, on the mapping step the file is chunked, split into parts. These parts are preprocessed. Now, each step of a batched import will take roughly the same amount of time which reduces overall import time while greatly reducing server resource usage during import.

    Hope this answer you question thoroughly!

    07/05/2018 at 1:13 pm #466915
    Age de Jong
    Participant

    Very thoroughly! Will install the release candidate :-)

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)

You cannot reply to this support topic. Please open your own support topic.