Product Import via csv file - limitations for long description field?

[Wade C]

I am new - newbie probably is an huge understatement, and wanted to first say thank you for all the hard work that has gone into Prestashop, and all of the help available here on the forums. Everyone here has been very helpful with their posts. I have learned very much from reading and searching.

I have battled my way through most of the import "hoops" but am getting stuck on one specific area: The Long Description when trying to import products. I have a rather large list of products which makes using the import feature almost a necessity...

I have built my csv file, and have nearly everything working correctly other than the long descriptions. I am not "programming" literate, so likely much more naive than most everyone here.

Is there some sort of limit for the long description in the .csv file when prestashop imports it? I have tested very short "long descriptions" and they work, as well as blank long descriptions. But when I include all the data I want to include, I get "hack attempt" errors.

I am guessing it is one of two things, improper characters in the long description field or a character limit.

Is there any "specifications" for allowable characters in the import fields or character limits? I saw in my search a limit supposedly on the meta fields but could find nothing on the other fields.

Thanks in advance.
Wade

[prestabase]

I do not see any limitation on the long description. How many characters are in your long description that isn't working? Do you have any specific characters or words that are not allowed in your description?

[Wade C]

I havent been able to isolate the long descriptions that are causing the problem due to the quantity of items with long descriptions. I have pasted the longest description I have entered.

Keep in mind that I use "@" as a place holder for a comma. I replace all of the initial "," with ";" for the import and then replace the "@" with "," in word pad prior to importing. Shy of the "@" symbol, the only other characters that come about are " ( ) and occasionally a "#" but I have replaced all of the "#" thinking that was causing the problem but it did not change the situation.

Pasted exactly as it is in the excel file I build the CSV from:

The public offering jig is a production version and each one is just like the other@ it is not custom in any way other than when the jig was designed it was customized specifically for reproduction.  It is NOT perfect@ nor does it have the same surface finish that comes on the Custom Jigs.  This is on purpose.  If you have questions feel free to contact us regarding the differences between the public jig and the custom jig.  The public offering version is a good starting point for your own soundboards. This jig is a learning tool@ and not a jig designed to give a finished product.  This jig will help you LEARN how to make calls@ it will not make calls for you.  There will be a light scribe line of both sides of the jig.  This scribe line is a starting point for you to reference when locating the end of your tone channel.  It is not a "set in stone" dimension@ only a guide to help you get started.  There are 4 tapped holes on the bottom of the jig (same hole pattern as on the flat and custom jigs).  The intend purpose of the tapped holes is to allow for mounting of the jig to a more solid base and to allow for positioning of the keg inside the jig.


As the entire entry shows in the .csv when opened in wordpad: Mind you I havent replaced the "," with ";" yet or the @ with ",".

The Header row is: (and omitted from the import - ie Skip "1" line)
ID,Active (0/1),Name,Category,Price,Tax,Wholesale price,On Sale (0/1),Sale $,Sale %,Sale start,Sale End,Ref#,Sup Ref,Suplier,Manf,EAN13,Eco,Weight,Qty,Short Desc,Long Desc,Tags,Meta-title,Meta Key,Meta Desc,Text In stock,Text out stock,IMG URL,Feature


56,1,Public Jig - .625" Bore,2@14,110.00,2.9,,0,20.00,,,,PJ1,,,,,,.8,10,WEBFoot's Public Duck Call Making Jig,The public offering jig is a production version and each one is just like the other@ it is not custom in any way other than when the jig was designed it was customized specifically for reproduction.  It is NOT perfect@ nor does it have the same surface finish that comes on the Custom Jigs.  This is on purpose.  If you have questions feel free to contact us regarding the differences between the public jig and the custom jig.  The public offering version is a good starting point for your own soundboards. This jig is a learning tool@ and not a jig designed to give a finished product.  This jig will help you LEARN how to make calls@ it will not make calls for you.  There will be a light scribe line of both sides of the jig.  This scribe line is a starting point for you to reference when locating the end of your tone channel.  It is not a ""set in stone"" dimension@ only a guide to help you get started.  There are 4 tapped holes on the bottom of the jig (same hole pattern as on the flat and custom jigs).  The intend purpose of the tapped holes is to allow for mounting of the jig to a more solid base and to allow for positioning of the keg inside the jig.,,Duck Call Making Jig,Call making parts@call making tools@duck call@goose call,WEBFoot Call Making Tools and supplies,In Stock!,Out of Stock - More on Order!,../../jigs/pubjig4_96x100.jpg



I have verified everything else in the file... if I delete the contents of the Long Description cells, it imports fine, so at least I have it narrowed down that far. Its just getting that part sorted out that is gonna hurt a lot if there is some sort of "acceptable" and "unacceptable" characters or number of characters.

Thanks again
Wade

[Tewet]

More than cca 3400 - 3900 characters in utf8 split long description to other columns and that makes erors in csv import. Have anyone solved this problem?