When a large import from a server source into the Media Library is in process and an unauthorized file type is encountered the import process stalls. It would be great to have some kind of status shown if the import process encounters an unrecoverable issue with details of why it's stopped. Even better, it would be great if it would continue with the import and provide a report when it's complete of the files it was unable to import. Having a list of the last 5 files imported that's continually updated during the process would be great as well instead of just the visual status bar.
Thanks for considering these improvements. We attempted a very large import four times before finally tracking down it was an unsupported file type that was killing the import process halfway through. We also encountered problems with what seemed to be regular PDFs, but had a very difficult time figuring out which ones because the import process just stalled without details of why.
Thanks for considering these improvements. We attempted a very large import four times before finally tracking down it was an unsupported file type that was killing the import process halfway through. We also encountered problems with what seemed to be regular PDFs, but had a very difficult time figuring out which ones because the import process just stalled without details of why.
The list of supported file types is convenient on that import page. However, if you accidentally overlook a file that isn't included in the allow list, the import stalls and doesn't give you any indication why or which file was the issue.
The PDF issue appears to be only specific PDFs. Some have a lot of vector layers or may have been created with different PDF generators. But the point on this part of the request is instead of the full import stalling without any feedback on which file caused it to fail is a less than desirable user experience
The other 10,000 PDFs we imported worked fine, but several caused our large imports to fail. The only way we could figure out what was causing it was to use PHPAdmin and review what successfully was imported. Then manually import those few files and omit them from the server import process.
That's why we're suggesting better error handling and more detailed info on what's being imported during the process.
The PDF issue appears to be only specific PDFs. Some have a lot of vector layers or may have been created with different PDF generators. But the point on this part of the request is instead of the full import stalling without any feedback on which file caused it to fail is a less than desirable user experience
The other 10,000 PDFs we imported worked fine, but several caused our large imports to fail. The only way we could figure out what was causing it was to use PHPAdmin and review what successfully was imported. Then manually import those few files and omit them from the server import process. That's why we're suggesting better error handling and more detailed info on what's being imported during the process.
- Page :
- 1
There are no replies made for this post yet.
