The Team Behind DealByEthan.com | Curating unique finds for a discerning community. Committed to a seamless and inspiring shopping experience. Connect with us: https://linktr.ee/dealbyethan
I did have plans; however, as life is/goes, they got affected. Between personal health issues, significant health care needed for a loved one, subsequent loss of their life, care and consolation to family members, then further issues experienced in executing ZC 2.1.0 code to support retrieving testing results, verification of changes across both sets... All before finding out that the primary issue above was not using the currently latest available version.
I haven't properly prepared an uploadable version meeting what I perceive the ZC requirements are for submission to the site. Considering the level of effort I see necessary to make that possible, I instead (contrary to whatever a recent poster unnecessarily felt to do) have been keeping the github location up-to-date as/where/when it seems necessary/appropriate. I have a major concept change I want to incorporate and have had to keep it side-lined so as not to fully break operation.
The recent issue had been related to a configuration "issue" I caused in implementing a feature. Some data did not get processed in the modified version.
If you still have interest (knowing that other program has issues also), the current version of EasyPopulate can be found at: GitHub - mc12345678/EasyPopulate-4.0 at v4.0.39.ZC which has a URL of: https://github.com/mc12345678/EasyPo...ree/v4.0.39.ZC
That address will change when the next version is loaded/created.
To note, I've tried to implement installation for either of both ways of use, as software installed directly to one's store and also as a zc_plugin. Under current ZC code operation, I do not suggest installing by both methods and generally speaking, I don't recommend using the zc_plugins directory for anything less than ZC 2.1.0. There's possibility of it working in previous versions; however, there may need to be some code changes to incorporate all currently existing features.
Lastly, as always has been the case, use at one's own risk. Run a test case in a development location before using on your live site. Use whatever product you wish. Generally, I've updated this because I care about the specific code and how so many have perhaps developed their own modifications off of it. I know some have generated unethical modifications; however, open-source code has that possibility and even commercial code can be abused.
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
Hello,
the CSV import works fine, but the data in the database does not change.
What could be the problem?
Thank you.
There are a number of possibilities of what the issue is, could be that the file uploaded but hasn't been imported, could be the file doesn't contain any headers applicable to the data to be imported.
It helps to be at clear and complete as possible from "start to finish".
How was the CSV generated? What file name did it have? What is the first row in the file, where I expect the field names to be captured by double quotes, what version was installed, what are the settings in the admin's configuration menu?
I expect the problem to be identified amidst response to that as, if a record in the file matches a unique field's record value, the associated data for that record of that file should get updated even if the update is the same value as it last was.
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
It's already working now. I had to use the German version.