EasyPopulate 4.0 Support Thread

[marcopolo]

I figured out why the test site failed! I had to edit my MYSQL my.cnf and comment out the following line:

#sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

restart mysql

then the import worked just fine.

[mc12345678]

I figured out why the test site failed! I had to edit my MYSQL my.cnf and comment out the following line:

#sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES

restart mysql

then the import worked just fine.

Two questions to confirm/understand, which issue(s) were corrected by the mysql change, and was EP4 upgraded as part of the process?

[marcopolo]

Two questions to confirm/understand, which issue(s) were corrected by the mysql change, and was EP4 upgraded as part of the process?

I upgraded to latest version of EP4 first, which did NOT solve the issue. I then applied the fix mentioned above and that fixed both issues.

[mc12345678]

I upgraded to latest version of EP4 first, which did NOT solve the issue. I then applied the fix mentioned above and that fixed both issues.

Again need specificity, by latest, which version?

[marcopolo]

Again need specificity, by latest, which version?

Easy Populate 4.0.30 - Beta 06-27-2015

[mc12345678]

Easy Populate 4.0.30 - Beta 06-27-2015

Ahh, okay I think (and am still trying looking into it) that the salemaker issue was resolved in 4.0.31, but there is still a minor issue or two to post to that. Meanwhile I have 4.0.32 prepped, but I want to test it a little more before publishing. Have a few different things going on and don't want to negatively impact any users...

[mc12345678]

Ahh, okay I think (and am still trying looking into it) that the salemaker issue was resolved in 4.0.31, but there is still a minor issue or two to post to that. Meanwhile I have 4.0.32 prepped, but I want to test it a little more before publishing. Have a few different things going on and don't want to negatively impact any users...

Hmm... Took a quick look at 4.0.31 and maybe the one thing missing is the longstanding error in the import file that there is one occurrence of $v_manufactureres (notice that misspelt) which occurs at the admin log entry line (1020) for when the manufacturers (notice correctly spelt) name is updated.. This is something that has existed since the first inclusion of the ZC 1.5.4 functionality... Only caught in the last month or so... 10-11 months of not being noticed...

There are a few other minor things (do not affect functionality) that would be nice to include there, but they are in 4.0.32 which is as I said just around the corner...