4.0.3 Beta possible bug

Started by mtn, 23 June 2024, 16:08:24

Previous topic - Next topic
A financial contribution is greatly appreciated as a support, to help us to keep live the project.
If you like this project you can donate some piece of BitCoin to this address: bc1qy5tgq6tvrckac2a57unxvqcnxamrvhduve9sj9
Print
Go Down Pages1
User actions

mtn

23 June 2024, 16:08:24
After trying for hours to import a CSV file in the beta, I downgraded to 4.0.2 and successfully imported the same CSV file. I'm sorry but I couldn't find any log that displayed the actual Mysql error that prevented 4.0.3 from importing.
(I should mention that I did export the CSV file first, and used that as a template--as well as the samples files-- to import)
Sincerely
Michael
A financial contribution is greatly appreciated as a support, to help us to keep live the project.
If you like this project you can donate some piece of BitCoin to this address: bc1qy5tgq6tvrckac2a57unxvqcnxamrvhduve9sj9

mtn

#1
23 June 2024, 17:08:12
I'm sorry to have wasted your time, but after more testing I found that the successful CSV import was a fluke. I'm now concentrating on the possibility of mandatory values-- fields which cannot be left NULL.

federica

#2
11 July 2024, 20:16:45
Hi mtn,
keep in mind that import/export tool works within the same Abook version.
Some fields as "metadesc", "metadata" and "params" may be cause problems because they contain characters that could interfere with the csv structure. I suggest to left this fields empty.
Al mondo ci sono 10 tipi di persone, quelli che hanno capito il codice binario e quelli che non l'hanno capito.
Informatizzati [url="https://informatizzati.org"]https://informatizzati.org[/url]
Stacca la spina [url="https://disconnessi.org"]https://disconnessi.org[/url]
Print
Go Up Pages1
User actions