search

PiRSquared17 / bpbible

Automatically exported from code.google.com/p/bpbible
Other
0 stars 1 forks source link

Downloaded from Portable apps and when installing new books it blows up #218

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. go to install
2. select zip file
3. error
---------------------------
Error reading books
---------------------------
An error occurred while trying to read books. Please report this issue:
 1. Press Ctrl-C to copy the error text
 2. In the BPBible menu, select Help > Report a problem.
 3. In the website that opens, click New Issue, and fill in the details
The error given was:
Traceback (most recent call last):
  File "install_manager\install_drop_target.pyo", line 28, in handle_dropped_files
  File "install_manager\zipinstaller.pyo", line 238, in find_zip_installer
  File "install_manager\zipinstaller.pyo", line 26, in __init__
  File "install_manager\zipinstaller.pyo", line 57, in open_zipfile
  File "install_manager\zipinstaller.pyo", line 113, in read_zipfile
  File "zipfile.pyo", line 696, in __init__
  File "zipfile.pyo", line 716, in _GetContents
  File "zipfile.pyo", line 728, in _RealGetContents
BadZipfile: File is not a zip file

---------------------------
OK   
---------------------------

What is the expected output? What do you see instead?
I wanted to install a bible version, I got an erorr instead

What version of the product are you using? 0.5 On what operating system? XP USB 
 Is it
the PortableApps version or the standard version? Portable apps

If the problem happens with one particular module (Bible, commentary,
dictionary, or book), what module is it? any and all modules

Please provide any additional information below.
I had an older versionand downloaded its bibles and was trying to use those.

Original issue reported on code.google.com by scott.damery on 30 Jan 2012 at 5:29

GoogleCodeExporter commented 9 years ago 
Every time this issue has been reported it turns out to be a faulty download.  
For an example with discussion, see issue 110.  I think re-downloading it 
should solve the problem.

Original comment by jonmmor...@gmail.com on 31 Jan 2012 at 9:38