Better feedback for incorrect Bible format
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenLP |
Confirmed
|
Medium
|
Unassigned |
Bug Description
We get a few of these every month in the support system. Someone who tries to import their Bible in who knows what format and just goes with the default format (which I am led to believe is OSIS). I know it's not our fault, but let's catch this exception and tell the user that they're using the wrong format.
--- Exception Traceback ---
Traceback (most recent call last):
File "openlp\
File "openlp\
File "openlp\
File "lxml.etree.pyx", line 2182, in lxml.etree.
File "lxml.etree.pyx", line 1778, in lxml.etree.
AssertionError: ElementTree not initialized, missing root
Changed in openlp: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
tags: | added: easy-fix |
tags: | added: beginner |
How clever does the fix need to be?
Would something like the following in bibleimportform.py, or osis.py be adequate?
`try: ons() orBox() `
someFuncti
except AssertionError as err:
displayErr
Or are you looking for something a bit cleverer?