The import has three problems.
1. Cloning collections during import
I analyzed the import file CollectionImportExportController.php using chatgpt.
And it has no idea how to append data to the current database. So, every time it sees a collection ID, instead of appending new elements to it, it creates a duplicate collection and calls it "collection 2." It places all new elements from the import into a new category (collection).
When you're working with tens or hundreds of data units, this is a huge problem. And considering you don't have a "Move" function, that's simply an insurmountable obstacle ((
2. Example file for import.
Judging by my research, the import function has no protection against "null" and spaces... There's no protection or simplification at all. If you make any mistakes, you get nothing.
I need an example of a correct file with empty fields (which aren't used, but are present in the JSON).
3. No debug.
If it doesn't like something, it doesn't say anything. Usually, it says "Import successful," but doesn't actually load anything. Moreover, there's no information about this in the JSON response or in the console, and nothing is even written to the logs. So, understanding the problem with the import is simply impossible.
I tried adding a debug there, but that's not right! A user who paid for a component shouldn't have to add their own debug to figure out what the component doesn't like.