Re: EasyPopulate 4.0 Support Thread
Quote:
Originally Posted by
gemohler
And then this happens.
Saved from open office, no changes other than a few 100k things added to the spreadsheet.
In this example, row 1 works.
Row 2 does not work.
They are functionally identical.
Is there a mistake in the above writing? The image suggests that the first does not work and the second does. As far as the csv file, I usually ensure each field's content is surrounded by double quotes when saving the csv file from the workbook. While I was able to open that CSV file in a workbook to have the data in what looks like the appropriate fields, nothing specifically stands out visually as a problem.
When I get an opportunity I'll try running that file, but may be a bit.
Re: EasyPopulate 4.0 Support Thread
Quote:
Originally Posted by
mc12345678
Is there a mistake in the above writing? The image suggests that the first does not work and the second does. As far as the csv file, I usually ensure each field's content is surrounded by double quotes when saving the csv file from the workbook. While I was able to open that CSV file in a workbook to have the data in what looks like the appropriate fields, nothing specifically stands out visually as a problem.
When I get an opportunity I'll try running that file, but may be a bit.
I may have got the text backwards, but the excel file is in the order of the import results.
Re: EasyPopulate 4.0 Support Thread
Quote:
Originally Posted by
gemohler
On the lookout for things I need to know as I relearn the ZC environment.
Im doing EP4 imports, and I have a log file getting _hammered_ with this (attached)
Gotcha, before suggesting what I just came up with, need to look to see if I have an existing solution on my development server. Mind me asking your specs? PHP version for example?
Re: EasyPopulate 4.0 Support Thread
Quote:
Originally Posted by
gemohler
I may have got the text backwards, but the excel file is in the order of the import results.
Was the issue always discovered on the first line of any import or was the issue random throughout the import of the file?
1 Attachment(s)
Re: EasyPopulate 4.0 Support Thread
Quote:
Originally Posted by
mc12345678
Gotcha, before suggesting what I just came up with, need to look to see if I have an existing solution on my development server. Mind me asking your specs? PHP version for example?
Right on..
Re: EasyPopulate 4.0 Support Thread
Quote:
Originally Posted by
mc12345678
Was the issue always discovered on the first line of any import or was the issue random throughout the import of the file?
THIS file had this issue. Everything after it failed.
I took the data from THIS spreadsheet (except the header row), and put it in another one that did work (under it's header row)...and everything was fine.
Re: EasyPopulate 4.0 Support Thread
I have this defined in the config:
User Defined Products Fields v_products_qty_box_status. (I have also tried this without v_)
I have this in my CSV:
v_products_qty_box_status
0
The one product I test this one, continues to show a qty available, which I want to set to hidden.
It seems as if I've done the right things as I've seen in a few good threads.
Re: EasyPopulate 4.0 Support Thread
Quote:
Originally Posted by
gemohler
On the lookout for things I need to know as I relearn the ZC environment.
Im doing EP4 imports, and I have a log file getting _hammered_ with this (attached)
Looks like my solution was to change the various instances of:
$categories_name_exists = false;
To an empty array:
Code:
$categories_name_exists = array(); // used for backwards compatibility
$categories_name_exists = []; // accomplishes the same as above via shortened code
Worked in PHP 8.2.9 for me. I had just come up with another idea, but it required writing more code.
Re: EasyPopulate 4.0 Support Thread
Quote:
Originally Posted by
mc12345678
Looks like my solution was to change the various instances of:
$categories_name_exists = false;
To an empty array:
Code:
$categories_name_exists = array(); // used for backwards compatibility
$categories_name_exists = []; // accomplishes the same as above via shortened code
Worked in PHP 8.2.9 for me. I had just come up with another idea, but it required writing more code.
Just change those two instances in easypopulate_4_import.php?
Simple enough. Was this having any impact other than a massive error log file?
Re: EasyPopulate 4.0 Support Thread
Quote:
Originally Posted by
gemohler
Just change those two instances in easypopulate_4_import.php?
Simple enough. Was this having any impact other than a massive error log file?
That was in part my question to you. :smile: Looking over changes I have made to push to github, that appears to be all that I needed to do to support complete import of the records that were formatted correctly. Haven't heard if the above resolved the earlier issue of the two records where the first was bypassed but the second imported. Further, didn't see a response to the question about any sort of consistency of report saying not imported because the category name was missing.
Look forward to hearing results so that I can maybe prioritize some of the patches/changes that have been made.
CORRECTION: Apparently there are responses above that I did not see/fully read. Maybe more to follow from me? :blink:
