-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feedback for partial imports #42
Comments
If an import fails it'll stop processing and dump info from the core on screen...if you encountered situation where it didnt thats a bug and will need more info on what failed. |
I've pasted the contents from the console log file below. So my original point was that the error message could be improved by telling the user which line to continue the import from. /*
Attempted to set execution time to infinite. Max execution time currently: infinite. Running pre-import tests on submitted data... No errors in pre-import found. Preparing import values... No errors found while checking the import values: 2 items found. Running import... Error: uri: Resource 962 is already using the URI products/broadcast/radio-transmission/exciters/exciters-professional-series-ptxlcd/ptx100lcddsp.html. Please enter a unique alias or use Freeze URI to manually override it. /* EOF */ |
Ah okay. Gotcha!
|
Second this request. |
Add some feedback to improve the user experience...
When an import partially works, it would be nice to have some feedback on the resources that were imported. For example, when you get a message like:
'XXX' could not be imported because a resource with alias 'XXX' already exists
its not immediately clear that some resources were imported, and some were not.
I think it would be good to provide feedback here on which lines of the import were done, (or which were not - which is probably what the user cares more about).
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: