Issue 242 in bpbible: Portable Version Not Portable

0 views
Skip to first unread message

bpb...@googlecode.com

unread,
Aug 10, 2013, 3:45:45 PM8/10/13
to bpbible...@googlegroups.com
Status: New
Owner: ----

New issue 242 by Isaac...@gmail.com: Portable Version Not Portable
http://code.google.com/p/bpbible/issues/detail?id=242

What steps will reproduce the problem?
1. Install portable version of BPBible to some folder.
2. Run BPBible Portable and install a module that it doesn't already have
installed.
3. Close BPBible Portable.
4. Copy the "BPBiblePortable" folder to a different computer.
5. Run BPBible on the different computer and the newly installed module
isn't there...it got left
in "C:\PortableApps\SWORDProjectPortable\Data\settings\modules" on the
original computer.

What is the expected output? What do you see instead?
The Portable version should keep its modules inside its Portable folder.
Under the File -> Set Sword Paths... one can see it is set to put some
files into C:\PortableApps\...

What version of the product are you using? On what operating system? Is it
the PortableApps version or the standard version?
Version 0.5.2
Windows 8 and Windows 7 respectivly.
The PortableApps version.

If the problem happens with one particular module (Bible, commentary,
dictionary, or book), what module is it?
Commentary, dictionary, and "other books" were tested and effected. (Others
may be as well, but I didn't test them)

Please provide any additional information below.
Maybe change default Sword paths so they are local to Portable folder by
default.

Thanks

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

bpb...@googlecode.com

unread,
Aug 13, 2013, 9:51:47 AM8/13/13
to bpbible...@googlegroups.com
Updates:
Status: Accepted
Owner: jonmmor...@gmail.com
Labels: Type-Defect Priority-High OpSys-Windows

Comment #1 on issue 242 by jonmmor...@gmail.com: Portable Version Not
Portable
http://code.google.com/p/bpbible/issues/detail?id=242

Definitely an issue.
Not yet sure why it is this way.
Thanks for reporting it.

bpb...@googlecode.com

unread,
Aug 24, 2013, 10:39:22 AM8/24/13
to bpbible...@googlegroups.com
Updates:
Owner: chris.morganiser

Comment #2 on issue 242 by jonmmor...@gmail.com: Portable Version Not
Portable
http://code.google.com/p/bpbible/issues/detail?id=242

The PortableApps launcher configuration seems to include highly dubious
code which breaks the order of paths even if I fix it in the initial
configuration.
The logic needs to match the logic of the desktop version: all AugmentPath
records are included in reverse order, and then the DataPath is included.
So %DATADIR%\resources needs to be the last AugmentPath, not the DataPath.

bpb...@googlecode.com

unread,
Oct 15, 2013, 3:18:29 PM10/15/13
to bpbible...@googlegroups.com

Comment #3 on issue 242 by Isaac...@gmail.com: Portable Version Not Portable
http://code.google.com/p/bpbible/issues/detail?id=242

I was wondering if perhaps the 0.5.2 Portable installer should be replaced
by the last truly portable version until this version gets fixed.

P.S. I'm not complaining that this hasn't been fixed yet, you guys do it
completely for free :) and besides that I know since it's open source, it's
open for anyone to fix.

bpb...@googlecode.com

unread,
Oct 15, 2013, 3:21:01 PM10/15/13
to bpbible...@googlegroups.com

Comment #4 on issue 242 by Isaac...@gmail.com: Portable Version Not Portable
http://code.google.com/p/bpbible/issues/detail?id=242

I was wondering if perhaps the 0.5.2 Portable installer should be replaced
by the last truly portable version until this version gets fixed. (unless
of course the configuration files from the new wouldn't be read correctly
by an older version).

bpb...@googlecode.com

unread,
Oct 16, 2013, 7:40:35 AM10/16/13
to bpbible...@googlegroups.com

Comment #5 on issue 242 by jonmmor...@gmail.com: Portable Version Not
Portable
http://code.google.com/p/bpbible/issues/detail?id=242

I suspect it's been an issue for a lot longer than 0.5.2, maybe even since
0.5.
I wouldn't be keen on reverting to an older version anyway given the number
of bug-fixes in 0.5.1 and 0.5.2 (though older versions are still available
on this site).

I would gladly fix it if I could, but my investigations in August ran me
into code that I couldn't understand what it was doing or why it was the
way it was, so I gave up.
Reply all
Reply to author
Forward
0 new messages