Skip to content
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

Open
christianhanvey opened this issue Dec 4, 2012 · 4 comments
Open

feedback for partial imports #42

christianhanvey opened this issue Dec 4, 2012 · 4 comments

Comments

@christianhanvey
Copy link
Contributor

christianhanvey commented Dec 4, 2012

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.

@Mark-H
Copy link
Member

Mark-H commented Dec 4, 2012

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.

@christianhanvey
Copy link
Contributor Author

I've pasted the contents from the console log file below.
I'm attempting to importing some resources I've already imported (because I know that will trigger the same error).
It fails on the first item (because of duplicate alias) and stops.
Is this what you are expecting?

So my original point was that the error message could be improved by telling the user which line to continue the import from.

/*

  • MODX Console Output
    *
  • @Date 2012-12-04 12:47:29
    */

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.
alias: 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 */

@Mark-H
Copy link
Member

Mark-H commented Dec 4, 2012

Ah okay. Gotcha!
Op 4 dec. 2012 02:53 schreef "Christian Hanvey" [email protected]
het volgende:

I've pasted the contents from the console log file below.
I'm attempting to importing some resources I've already imported (because
I know that will trigger the same error).
It fails on the first item (because of duplicate alias) and stops.
Is this what you are expecting?

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.
alias: 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 */


Reply to this email directly or view it on GitHubhttps://github.com//issues/42#issuecomment-10980947.

@KirilOkun
Copy link

Second this request.
During an import i got the same issue of duplicate aliases. The error message also stated that 20 out of 171 records were imported by didn't say which ones. This is extremely unhelpful. It should list the details of the imported records so they can be removed from the next import after the aliases are fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants