EasyPopulate 4.0 Support Thread

[g2ktcf]

I just wanted to take a moment and thank everyone who has worked on EP4. I have used this in so many ways just in the last few days. We wanted to add some different categories to several hundred products. I was able to create all of those links in a matter of minutes. I wanted our sort order modified to mimic the SKU numbers (helps us with orders and inventory). Again, a few formulas in a spreadsheet along with copy & paste the values back to the CSV file and I was golden!



Chris

[kernheimer]

Even though i still have problems with my EP, i could not agree with you more. The feedback and help here are amazing.

I just wanted to take a moment and thank everyone who has worked on EP4. I have used this in so many ways just in the last few days. We wanted to add some different categories to several hundred products. I was able to create all of those links in a matter of minutes. I wanted our sort order modified to mimic the SKU numbers (helps us with orders and inventory). Again, a few formulas in a spreadsheet along with copy & paste the values back to the CSV file and I was golden!



Chris

[mc12345678]

Even though i still have problems with my EP, i could not agree with you more. The feedback and help here are amazing.

@kernheimer, as you and I know, we have talked outside this forum. I would like to ask a few questions to find an answer.

In admin->Configuration->Easy Populate 4:

What are the settings for:
1. Import/Export Primary Key
2. Import Language Override

The problem described indicates a conflict.
To correct the issue I understand:
If 1. is products_id or blank_new, then 2. should *NOT* be products_model_only.
If 1. is products_model (historically the default), then 2. should *NOT* be products_id_only.

The above is for the problem described. The problem described has been, when importing a product file created by export, the system response is "No category provided for this new product".

I have more questions, but in this situation I want to slow down and address one issue at a time. Please continue to have patience.

[brittainmark]

I have just got the latest version from git hub and wanted to check if it is now a requirement that the folder in which you keep the uploaded files is under [YOURADMIN] directory.
The reason I ask is that I was having trouble with all the files showing CSV Unknow Delimiter. I tracked the code down to module easypopulate_4.php lines 438-444

$basepath = "";
  $realBase = realpath($basepath);
  $userpath = $basepath . $file;
  $realUserPath = realpath($userpath);
  if ($realUserPath === false || strpos($realUserPath, $realBase) !== 0) {
      return NULL; // return back to the function with a non-result?
  } 

The issue is that
$file /MYSERVER/HOME/EASYPOPULATELOADDIR/EasyPopulateUploadDIR/Myfile.csv
$realBase /MYSERVER/HOME/EASYPOPULATELOADDIR/MYADMIN
$userpath /MYSERVER/HOME/EASYPOPULATELOADDIR/EasyPopulateUploadDIR/Myfile.csv
$realUserPath /MYSERVER/HOME/EASYPOPULATELOADDIR/EasyPopulateUploadDIR/Myfile.csv

does not pass the test unless EasyPopulateUploadDIR is under MYADMIN
thus $file /MYSERVER/HOME/EASYPOPULATELOADDIR/MYADMIN/EasyPopulateUploadDIR/Myfile.csv

I can leave the folder under MYADMIN just checking that this is now a requirement, OR if i have set something up wrongly.

[mc12345678]

I have just got the latest version from git hub and wanted to check if it is now a requirement that the folder in which you keep the uploaded files is under [YOURADMIN] directory.
The reason I ask is that I was having trouble with all the files showing CSV Unknow Delimiter. I tracked the code down to module easypopulate_4.php lines 438-444

$basepath = "";
  $realBase = realpath($basepath);
  $userpath = $basepath . $file;
  $realUserPath = realpath($userpath);
  if ($realUserPath === false || strpos($realUserPath, $realBase) !== 0) {
      return NULL; // return back to the function with a non-result?
  } 

The issue is that
$file /MYSERVER/HOME/EASYPOPULATELOADDIR/EasyPopulateUploadDIR/Myfile.csv
$realBase /MYSERVER/HOME/EASYPOPULATELOADDIR/MYADMIN
$userpath /MYSERVER/HOME/EASYPOPULATELOADDIR/EasyPopulateUploadDIR/Myfile.csv
$realUserPath /MYSERVER/HOME/EASYPOPULATELOADDIR/EasyPopulateUploadDIR/Myfile.csv

does not pass the test unless EasyPopulateUploadDIR is under MYADMIN
thus $file /MYSERVER/HOME/EASYPOPULATELOADDIR/MYADMIN/EasyPopulateUploadDIR/Myfile.csv

I can leave the folder under MYADMIN just checking that this is now a requirement, OR if i have set something up wrongly.

Was not intended to become a "requirement". I have a fix for the above issue that retains the expected security.
It can be found at this commit: Restore import from catalog side/remove CSV delimiter warning · mc12345678/EasyPopulate-4.0@84331eb (github.com)

[mc12345678]

I have just got the latest version from git hub and wanted to check if it is now a requirement that the folder in which you keep the uploaded files is under [YOURADMIN] directory.
The reason I ask is that I was having trouble with all the files showing CSV Unknow Delimiter. I tracked the code down to module easypopulate_4.php lines 438-444

$basepath = "";
  $realBase = realpath($basepath);
  $userpath = $basepath . $file;
  $realUserPath = realpath($userpath);
  if ($realUserPath === false || strpos($realUserPath, $realBase) !== 0) {
      return NULL; // return back to the function with a non-result?
  } 

The issue is that
$file /MYSERVER/HOME/EASYPOPULATELOADDIR/EasyPopulateUploadDIR/Myfile.csv
$realBase /MYSERVER/HOME/EASYPOPULATELOADDIR/MYADMIN
$userpath /MYSERVER/HOME/EASYPOPULATELOADDIR/EasyPopulateUploadDIR/Myfile.csv
$realUserPath /MYSERVER/HOME/EASYPOPULATELOADDIR/EasyPopulateUploadDIR/Myfile.csv

does not pass the test unless EasyPopulateUploadDIR is under MYADMIN
thus $file /MYSERVER/HOME/EASYPOPULATELOADDIR/MYADMIN/EasyPopulateUploadDIR/Myfile.csv

I can leave the folder under MYADMIN just checking that this is now a requirement, OR if i have set something up wrongly.

Was not intended to become a "requirement". I have a fix for the above issue that retains the expected security.
It can be found at this commit: Restore import from catalog side/remove CSV delimiter warning · mc12345678/EasyPopulate-4.0@84331eb (github.com)

I can't seem to "properly" edit the previous post and it is not a "timeout" issue, the original content just doesn't appear in the editor.

Anyways, the above is to be incorporated into the next version which I'm near completing for forum posting but had some things to work out/on.

[brittainmark]

Thats great. Thanks. If i find anything else shall i post here or raise issue on git-hub.

[kernheimer]

@kernheimer, as you and I know, we have talked outside this forum. I would like to ask a few questions to find an answer.

In admin->Configuration->Easy Populate 4:

What are the settings for:
1. Import/Export Primary Key
2. Import Language Override

The problem described indicates a conflict.
To correct the issue I understand:
If 1. is products_id or blank_new, then 2. should *NOT* be products_model_only.
If 1. is products_model (historically the default), then 2. should *NOT* be products_id_only.

The above is for the problem described. The problem described has been, when importing a product file created by export, the system response is "No category provided for this new product".

I have more questions, but in this situation I want to slow down and address one issue at a time. Please continue to have patience.

Dear mc12345678

What are the settings for:
1. Import/Export Primary Key. - Products_model
2. Import Language Override. _ Language_code _only

[mc12345678]

Dear mc12345678

What are the settings for:
1. Import/Export Primary Key. - Products_model
2. Import Language Override. _ Language_code _only

Ok, I *tried* to ask for information about the settings that are involved with this, I missed one setting.... Although I did not ask for one setting, I received information that is/was helpful.

The settings I was *really* interested in were:
1. Import/Export Primary Key
2. Import Language Override
3. Export Language Identifier

The default settings for these in 4.0.37.13 were:
1. products_model
2. language_code_only
3. id

The problem with some of those defaults (as discussed several times before) is that when importing data that is language dependent, trying to import only fields with the language_code means that the field likely does not exist. Because the specific field does not exist then the data does not exist for the program. Why would the field not exist? Because when exporting the data, the language dependent field(s) only ended with the language_id.

So, to more accurately state the necessary conditions:

If 3. (Export Language Identifier) is id when exporting the file, then 2. (Import Language Override) should *NOT* be language_code_only.
If 3. (Export Language Identifier) is code when exporting the file, then 2. (Import Language Override) should *NOT* be language_id_only.

The above is for the problem described. The problem described has been, when importing a product file created by export, the system response is "No category provided for this new product". Why? because, if the code is looking for categories_name_en, but it only contains categories_name_1, then it is true that the category is considered to be missing.

So, in summary, may I suggest changing the setting for Import Language Override to ANYTHING other than language_code_only. Generally speaking, I would suggest changing it to language_id_only to keep things "simple". :)

[waterbender]

Hi,

I tried updating the image and description of existing categories using the CategoriesMeta-EP file. The file import was complete and the image and description were inserted. However, there is an error:
"An SQL error has occured. Please check your input data for tabs within fields and delete these. If this error continues, please forward your error log to the Easy Populate maintainer"

The debug error log shows:
MySQLi error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '
categories_id = 10387,
language_id ...' at line 1
When executing:
INSERT INTO zen_meta_tags_categories_description SET ,
categories_id = 10387,
language_id = 1

How can this error be fixed please?
Thanks