Logos Bible Software 4.6 Beta 1 (4.60.0.2634) YIKES!

When I open a passage guide it populates fine but when i click or double click on any volume in the list nothing happens… also high-lites are no longer functional, unless you hold down the control key. In for a penny in for a pound I tried to downgrade back to stable release only to be told that isn't possible Please reinstall latest version. I will be using it but obviously if i had a choice i would have went back to a simpler more functioning Logos…

[^o)]

-dan

Find more posts tagged with

Comments

Philana Crouch

Are you experiencing a difficulty beyond what was noted in the release notes? I haven't had a chance to use the highlighting feature yet.

JT (alabama24)

I tried to downgrade back to stable release only to be told that isn't possible Please reinstall latest version. I will be using it but obviously if i had a choice i would have went back to a simpler more functioning Logos…

Sorry for your troubles Dan. [:S] It is a good reminder, however, that betas are often buggy. Personally, I switch off of beta channel until things settle down a bit to avoid situations like this.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/382910#Comment_382910

I tried to downgrade back to stable release only to be told that isn't possible Please reinstall latest version. I will be using it but obviously if i had a choice i would have went back to a simpler more functioning Logos…

Sorry for your troubles Dan. It is a good reminder, however, that betas are often buggy. Personally, I switch off of beta channel until things settle down a bit to avoid situations like this.

Another approach is using several Mac OS X user accounts so stable and beta can be installed on one computer. Personally have Stable release in my Applications folder while Logos 4 Mac Beta is in my Documents folder.

Keep Smiling [:)]

mab

https://community.logos.com/discussion/comment/382916#Comment_382916

You might also consider using another startup drive for stable work so as not to clobber your necessary stuff. Or keep your beta testing on a Win installation [;)]

Bob

I can confirm that the passage guide WILL NOT allow any resource to open! I entered Hosea 1 into the passage guide, the Bible text appears along with one resource and any attempt to select additional resources yields nothing! I am "dead in the water" on 4.6 beta 1!

George W Raduano

https://community.logos.com/discussion/comment/382967#Comment_382967

I have found that it is only my commentaries in the passage guide, that will not open. Resources that are not in the "commentaries" sections all seem to open and function as expected.

David Ames

https://community.logos.com/discussion/comment/382910#Comment_382910

Sorry for your troubles Dan. It is a good reminder, however, that betas are often buggy. Personally, I switch off of beta channel until things settle down a bit to avoid situations like this.

Thank you, Thank you, Thank you.

Thanks to all of you that do beta testing. [Have done beta testing elsewhere and know what a pain it can be. But it is a needed step in getting a quality product. ]

Thank you for finding all the whoops so I don't see them!

Jackie Watts

https://community.logos.com/discussion/comment/382967#Comment_382967

Same here. Can we get a quick patch? Thanks!

Jackie Watts

https://community.logos.com/discussion/comment/382994#Comment_382994

No highlighting shortcuts on Bible either. I can pull up highlighter in 'Tools', but no shortcut buttons work.

Dan Francis

https://community.logos.com/discussion/comment/382995#Comment_382995

No highlighting shortcuts on Bible either. I can pull up highlighter in 'Tools', but no shortcut buttons work.

Highlights will function IF YOU HOLD DOWN THE [control] key when pushing the short cut key.

-Dan

Jackie Watts

https://community.logos.com/discussion/comment/383009#Comment_383009

Thanks - do you think that was purposeful...or a glitch that needs to be worked out?

JT (alabama24)

https://community.logos.com/discussion/comment/383011#Comment_383011

Thanks - do you think that was purposeful...or a glitch that needs to be worked out?

I remember a discussion about a similar issue a little while back. I don't know if this is a regression, or if it is because of changes necessary due to Mountain Lion coming out next week.

Jack Caviness

https://community.logos.com/discussion/comment/382989#Comment_382989

Thank you, Thank you, Thank you.

You are welcome, maybe [8-|] The cutting edge of technology is often called the bleeding edge. When I was younger, I volunteered for submarine duty in the US Navy; now I beta test L4 Mac for that same sense of impending disaster [:D]

Tonya J Ross

When I open a passage guide it populates fine but when i click or double click on any volume in the list nothing happens

There is an active case for this issue.

high-lites are no longer functional

If you are referring to highlighting shortcuts, there is an active case for this issue.

Jackie Watts

https://community.logos.com/discussion/comment/383115#Comment_383115

Thanks for the update.

Dan Francis

https://community.logos.com/discussion/comment/383080#Comment_383080

Thank you, Thank you, Thank you.

You are welcome, maybe The cutting edge of technology is often called the bleeding edge. When I was younger, I volunteered for submarine duty in the US Navy; now I beta test L4 Mac for that same sense of impending disaster

Well if you can survive submariner duty I suppose i will survive beta testing. It is only slightly in convenient needing to switch books rather than clinking on them.

-dan

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/382968#Comment_382968

I have found that it is only my commentaries in the passage guide, that will not open. Resources that are not in the "commentaries" sections all seem to open and function as expected.

Concur; unable to open any commentaries in section(s) of Commentaries, however, can open commentaries (and other resources) in section(s) of Collections

Keep Smiling [:)]

Jack Caviness

https://community.logos.com/discussion/comment/383124#Comment_383124

Concur; unable to open any commentaries in section(s) of Commentaries,

Becoming more efficient in the use of the open command: "open Moo Romans to Rom 1.18" provides two choices because my library has two commentaries on Romans by Douglas Moo. Can then cycle through my Technical commentaries (that's a collection) on Romans 1:18 using the parallel resources button—or the right/left arrow keys.

With a little practice, this becomes an efficient operation. Still would prefer the PG, however.

Kevin A. Purcell

https://community.logos.com/discussion/comment/383132#Comment_383132

I can understand many of the obscure bugs that get through in these beta releases, but how does something like this escape the notice. That's like letting a model of a car out of the factory where none of the radios turn on. You'd think they'd find a fix for such a big feature before releasing a beta. I can understand it showing in internal builds, but not a public beta.

David Ames

https://community.logos.com/discussion/comment/383142#Comment_383142

I can understand many of the obscure bugs that get through in these beta releases, but how does something like this escape the notice. That's like letting a model of a car out of the factory where none of the radios turn on. You'd think they'd find a fix for such a big feature before releasing a beta. I can understand it showing in internal builds, but not a public beta.

Most of the time before a Beta is released it goes through internal testing [alpha testing]. That testing should include regression testing and not just testing the 'new' stuff. Logos 4 is very complex, made up of many many modules and all it takes is for one module to miss an internal testing step to make the alpha test look bad. [that is bugs passed along to the beta] [one last fix that skips the alpha testing when what should be done is restart the alpha testing from step one [but it was only a one line fix] - some developer that had a copy of the 'old' code and mixed it up with the 'new' code when trying to fix that one last thing the last day before going bata [deliberate misspelling - beta to bats]- and other whoops]

Paul N

https://community.logos.com/discussion/comment/383192#Comment_383192

Not to be pushy but eager to see this get fixed!

It is good to learn new ways to navigate though...

Kevin A. Purcell

https://community.logos.com/discussion/comment/383192#Comment_383192

I can understand many of the obscure bugs that get through in these beta releases, but how does something like this escape the notice. That's like letting a model of a car out of the factory where none of the radios turn on. You'd think they'd find a fix for such a big feature before releasing a beta. I can understand it showing in internal builds, but not a public beta.

Most of the time before a Beta is released it goes through internal testing [alpha testing]. That testing should include regression testing and not just testing the 'new' stuff. Logos 4 is very complex, made up of many many modules and all it takes is for one module to miss an internal testing step to make the alpha test look bad. [that is bugs passed along to the beta] [one last fix that skips the alpha testing when what should be done is restart the alpha testing from step one [but it was only a one line fix] - some developer that had a copy of the 'old' code and mixed it up with the 'new' code when trying to fix that one last thing the last day before going bata [deliberate misspelling - beta to bats]- and other whoops]

That's fine for something that's not as much a central part of the program. But this clearly shows that no one involved in the alpha test actually uses Logos to prepare their sermons or Bible studies. I can't imagine how such a big bug could get through if as few as 12 people tested it and any of them used it for actual Bible Study prep. The Passage Guide is as basic to Logos as turning on a radio on your car. Few people who actually use the app don't use the PG at some point I'd bet.

David Ames

https://community.logos.com/discussion/comment/383823#Comment_383823

But this clearly shows that no one involved in the alpha test actually uses Logos to prepare their sermons or Bible studies. I can't imagine how such a big bug could get through if as few as 12 people tested it and any of them used it for actual Bible Study prep. The Passage Guide is as basic to Logos as turning on a radio on your car. Few people who actually use the app don't use the PG at some point I'd bet.

Dear Logos Testing Department;

Please have that Alpha Tester that prepares a sermon using the version of Logos 4 that will be released the next day as Beta z post their procedure used so that the Beta Testers can review it. There seems to be a bug in the Alpha Test Sermon Preparation Procedure. Thanks.

[[Sent this as an email to customerservice@logos.com]]

JT (alabama24)

https://community.logos.com/discussion/comment/383829#Comment_383829

David - I can appreciate your frustration. Having gone through many beta cycles now, I have come to realize that it is best not to remain on beta channel once the release goes live, especially when you don't have multiple machines and depend upon the one. By changing your channel to stable, you should not be surprised by an unusable beta. Once the beta has been put through the ringer a little, you can switch back over.

David Ames

https://community.logos.com/discussion/comment/383850#Comment_383850

David - I can appreciate your frustration. Having gone through many beta cycles now, I have come to realize that it is best not to remain on beta channel once the release goes live, especially when you don't have multiple machines and depend upon the one. By changing your channel to stable, you should not be surprised by an unusable beta. Once the beta has been put through the ringer a little, you can switch back over.

David is not, currently, frustrated. David is not on Beta Chanel. [There must be some language where Beta is defined as ‘frustrated’] But David has done much Beta testing and knows what it can be like.

As I was an in house Beta tester I had access to the Alpha testers and working together we got a better product out the door. We also used error reports from our out of house Beta and also live customers to better our in house testing. And, as here, many of our Beta errors were because of inadequate testing to see what got broke in fixing something else. And, in our case, many of those were from so called simple one line fixes that did not get run through the entire test process [mostly fixing errors found in the test cycle and thus done at the end of the long test cycle and nobody wanted to re run all of the tests yet again – big mistake]. After several cycles they moved me to running standard tests that just looked for those errors and I did have permission to run all of those tests after the ‘last’ fix.

Which is why I am not doing Beta here [too much brain damage from banging head against wall while doing Beta testing elsewhere] but I started commenting on this thread to thank the Beta testers and got into one of their problems. [in sympathy with them]

Also, just a reminder, I happen to be a PC person but the problem here seemed to be related to testing procedures and not a mac/pc problem. If they are missing THAT on the MAC side they are most likely missing it on the PC side also.

It just looked like Your MAC beta testers needed to know that they were not alone.

So I dropped by to try to encourage them.

JT (alabama24)

https://community.logos.com/discussion/comment/383902#Comment_383902

It just looked like Your MAC beta testers needed to know that they were not alone.

So I dropped by to try to encourage them.

[:D]

Thanks for clarifying. Encouragement is appreciated. Even from a PC. [;)]

Jeff Robison

https://community.logos.com/discussion/comment/383916#Comment_383916

I am waiting for the next update. Not frustrated, not mad, not upset with Logos. Just waiting so we can report the next round of bugs to improve the product. Thanks to all of the other beta testers for finding the things that need to be fixed.

Dan Francis

https://community.logos.com/discussion/comment/383957#Comment_383957

I am waiting for the next update. Not frustrated, not mad, not upset with Logos. Just waiting so we can report the next round of bugs to improve the product. Thanks to all of the other beta testers for finding the things that need to be fixed.

Same here I am upset logos beta is broken but I am not upset with Logos itself, I am using beta software, it is expected to be buggy. I was a little upset not to be able to go back to the stable version, but again that is not Logos fault I know the caveats this version runs ok and i am glad for that as i would hate to be limited to my iPAD. I just hope beta 2 is ready soon.

-dan

Tonya J Ross

https://community.logos.com/discussion/comment/383115#Comment_383115

When I open a passage guide it populates fine but when i click or double click on any volume in the list nothing happens

There is an active case for this issue.

This issue should be resolved in 4.6 Beta 2.

Dan Francis

https://community.logos.com/discussion/comment/384689#Comment_384689

Thanks, hope beta 2 is out soon… but i do realize better to be done right than fast and buggy.

-dan

Jackie Watts

https://community.logos.com/discussion/comment/384705#Comment_384705

Space bar not working to move page? Anybody else seem to have this issue? (MacBook Retina w/Mountain Lion)

Kevin A. Purcell

https://community.logos.com/discussion/comment/383850#Comment_383850

David - I can appreciate your frustration. Having gone through many beta cycles now, I have come to realize that it is best not to remain on beta channel once the release goes live, especially when you don't have multiple machines and depend upon the one. By changing your channel to stable, you should not be surprised by an unusable beta. Once the beta has been put through the ringer a little, you can switch back over.

The problem isn't that people who use the beta a lot don't realize that its beta and will have problems.

The problem is that this particular bug was released into a public beta. Why would Logos release a public beta with such a fundamentally and universally used feature reressing? If I were the guy in charge of when the beta gets pushed out, I'd let some bugs out, but not something this big. I'd say, woops! This Alpha is not ready to go to public beta till we fix this major feature that worked fine in the previous beta.

That they didn't stop that release leads me to believe that one of two things may be true.

1. They don't really care that much when regressions slip into the beta. We'll fix it in the next cycle.

2. They don't use the software for regular sermon or Bible study prep and therefore didn't actually use the Passage Guide during this round of testing.

Either way its disconcerting and makes me wonder if Logos will continue to regress in quality as it as been over the last couple of years. The features get more interesting but the quality of the software slips, at least on the Mac side.

Jack Caviness

https://community.logos.com/discussion/comment/384894#Comment_384894

If I were the guy in charge of when the beta gets pushed out, I'd let some bugs out, but not something this big

Seems they want to push the Mac beta out along with the Windows beta whether it will work or not.

Apparently no one on the dev team actually uses L4 Mac.

Donovan R. Palmer

https://community.logos.com/discussion/comment/384922#Comment_384922

Apparently no one on the dev team actually uses L4 Mac.

How glaring bugs and regressions creep out through the various stages of development has been a mystery to me. There is a news story from last week of a young boy who boarded a plane in Manchester bound for Italy that was not discovered until the flight was in route. He ran away from home, went through various levels of security with no passport and got on the plane without a ticket. Everyone is stunned how he got that far and in the end, it was passengers on the flight that picked up that something was not quite right. http://www.guardian.co.uk/uk/2012/jul/25/11-year-old-flies-rome-manchester?newsfeed=true

I sometimes wonder the same thing about some of these bugs and regressions. How can you genuinely use the product and not notice some of this stuff before the go button gets pressed? My theory is that the development team must be maxed out with work loads.