This is strange, we use the same method as before.
Let me have a look and tell you then.
Thread Starter
mtxz
(@mtxz)
Hello,
yes, I’ve just discovered this behavior. Before, it was working as expected and stored string in the database.
If you need further tests or Infos on my side, just let me know.
@mtxz,
OK I think I have just disovered the problem.
Update to the last version and tell me if all goes ok.
Thread Starter
mtxz
(@mtxz)
@javier Carazo,
I just updated and test: It works great 🙂 Fields are now saved as text.
I still have an issue with the textarea field “description” as you can see on new screenshots, is always empty but provided, and seen on the export success page.
There are also many warnings, but I guess it’s ok for me as the import worked in the end.
Thanks a lot for the quick fix and answers. Please send me a donation link 😉
https://ibb.co/gzF3RCP
https://ibb.co/rFQ2zb6
https://ibb.co/60nNYSz
@mtxz,
The error appears because I have made something wrong there.
Is this working with the error messages or it fails and it does not update it?
Thread Starter
mtxz
(@mtxz)
Well the screenshots are the results after import.
So, the fix for string fields is OK. But as you can see, the textarea field is empty in the database, but is visible on the import success page.
So the import work (with the warnings from the screenshot), but the textarea field is not saved in DB, but displayed in the import result table (as seen on capture).
I have redone all this part.
Could you update again and check?
