This is to update the main thread for EasyPopulate V4 to recognize for all using it that version 4.0.33 is considered a stable release (yes there remain some issues that are tracked in the issues area(s)), but these are relatively minor.
This version has been released/posted to the ZenCart page and are being downloaded by ZC forum visitors.
Significant modifications made include (but are not limited to):
German language has been incorporated which also allows/makes it easier for EP4 to be ported to other languages. Still looking for volunteers to translate to other languages. Specifically would like to see Italian as EP4 is used on the Italian ZC website, but I have not been permitted access to download the version that is posted/accessible from there.
The main menu offers the opportunity to see which by which filetype a file will be processed to attempt to clarify why certain imports do not provide the "expected" results. Option is available in the admin configuration settings to return to the original style.
The upload directory no longer permits entry of the admin folder name in the path. There are automated operations that will adjust the settings to be stored in the database so that the admin path does not/should not appear in the database. This could possibly be further restricted through checks for things like ../../. etc... But the intent is to prevent the common user from storing their admin path in the database.
Import code has been sanitized to use $db->bindVars.
Notifiers have been added in opportune locations to support expanding EP4 and other developers to more easily add functionality. The initial focus was to support the BookX modification being made by another zenner to merge the BookX product type with EP4.
The ability to import/export by products_id has been added with the potential ability to add additional/alternate primary keys. This has been something mentioned for a long time in the thread; however, until now had not been incorporated into this code. Generally speaking the preferred method remains to use the products_model as typical "operation"/design consideration was the import of product from a source outside of ZC which likely does not have a designated products_id. The power of using/having the products_id functionality available is that new users of EP4 do not have to have already entered unique products_model data before starting to use EP4, but can inplace update that field to provide a unique products_model and then transition over to just using products_model if they are importing from an outside source or remain using the products_id if they wish to only update/modify in cart product in mass quantity.
Many if not all of the import sections have been streamlined to allow "simple" import files to include only one column in addition to the applicable key column. Reducing the number of columns to a single column does have the potential of making future review of the import files confusing, but again this is/was a feature requested by many that perhaps haven't yet fallen into the pit-trap of trying to review what went wrong in an update...
Many of the functions have been modified to use ZC standard functions; however, the queries remain written to support the builtin error logging. This makes the program slightly more user friendly if there is an error in the import file the applicable error is readily accessible and easier to troubleshoot.
This is to update the main thread for EasyPopulate V4 to recognize for all using it that version 4.0.33 is considered a stable release (yes there remain some issues that are tracked in the issues area(s)), but these are relatively minor. This version has been released/posted to the ZenCart page and are being downloaded by ZC forum visitors. Significant modifications made include (but are not limited to): German language has been incorporated which also allows/makes it easier for EP4 to be ported to other languages. Still looking for volunteers to translate to other languages. Specifically would like to see Italian as EP4 is used on the Italian ZC website, but I have not been permitted access to download the version that is posted/accessible from there. The main menu offers the opportunity to see which by which filetype a file will be processed to attempt to clarify why certain imports do not provide the "expected" results. Option is available in the admin configuration settings to return to the original style. The upload directory no longer permits entry of the admin folder name in the path. There are automated operations that will adjust the settings to be stored in the database so that the admin path does not/should not appear in the database. This could possibly be further restricted through checks for things like ../../. etc... But the intent is to prevent the common user from storing their admin path in the database. Import code has been sanitized to use $db->bindVars. Notifiers have been added in opportune locations to support expanding EP4 and other developers to more easily add functionality. The initial focus was to support the BookX modification being made by another zenner to merge the BookX product type with EP4. The ability to import/export by products_id has been added with the potential ability to add additional/alternate primary keys. This has been something mentioned for a long time in the thread; however, until now had not been incorporated into this code. Generally speaking the preferred method remains to use the products_model as typical "operation"/design consideration was the import of product from a source outside of ZC which likely does not have a designated products_id. The power of using/having the products_id functionality available is that new users of EP4 do not have to have already entered unique products_model data before starting to use EP4, but can inplace update that field to provide a unique products_model and then transition over to just using products_model if they are importing from an outside source or remain using the products_id if they wish to only update/modify in cart product in mass quantity. Many if not all of the import sections have been streamlined to allow "simple" import files to include only one column in addition to the applicable key column. Reducing the number of columns to a single column does have the potential of making future review of the import files confusing, but again this is/was a feature requested by many that perhaps haven't yet fallen into the pit-trap of trying to review what went wrong in an update... Many of the functions have been modified to use ZC standard functions; however, the queries remain written to support the builtin error logging. This makes the program slightly more user friendly if there is an error in the import file the applicable error is readily accessible and easier to troubleshoot.