41.1 (41.1.006) is now available
The Logos Bible Study application version 41.0 is now available to all users.
To immediately update to the current stable version, enter Update Now into the command box. Otherwise, the app will automatically update the next time it is scheduled to check for updates.
Comments
-
Hmm, I would still love not to be getting AI promotional stuff shoved in my face when using the software as a Logos 10 user. I expect better from other companies, so I think a reportedly Christian enterprise should be held to a higher standard. Thanks for the bug fixes anyways.
0 -
Brody, you might want to update your terminology as there is no Logos 10 software since the last release 10 Oct 2022 although there are still legacy libraries sold under that name. I have my Logos/Verbum release 41 set up with almost no promotional materials. If you start a thread specifying what promotional materials you are seeing, we can probably tell you how to turn it off.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Sorry to hear that. To better help you. I'd recommend creating a separate post in feedback with specifics (images, etc) and details to give our product team a good understanding on your experience.
0 -
Hopefully Brody will return to confirm what exactly he's referring to, but I think it may be the new Smart Search bar on the Dashboard. I have no issues with Logos's AI and I don't view the search bar as promotional, but I do see it as intrusive.
The search bar has been on my dashboard for about a week now and we are not co-existing happily; I'm looking forward to Logos making it optional.
0 -
The option to not show the Smart Search bar would be consistent with the rest of the Dashboard. Recent updates (e.g. drag and drop) indicate that the intention is to make the Dashboard more customizable, not less. Even if this option doesn't come for a little while, it would comfort some to know it'll come eventually.
1 -
The "Smart" search bar also serves as a precise search bar … if we change our vocabulary it ceases to be promotional and is merely left as intrusive. I would like to see it changed to a card format rather than appearing so uniquely.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Not by me!. I ran several times "update" but it doesn't come the new version. Or is this because I'm on beta?
Thanks.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
Or is this because I'm on beta?
@Fabian Correct.
2 -
Use
set update channel to stableinstead.Dave
===Windows 11 & Android 13
1 -
As a side note: This only works if the UI language is in English.
I found it easier to download it directly and replace the other one. (I'm on Mac).
Thanks for the infos.
Χριστὸς ἐν ὑμῖν, ἡ ἐλπὶς τῆς δόξης·
0 -
For what it's worth, this is only a one-way street. Once you update your machine to the beta build. You'll have to do a fresh install if you want to go back to the stable build.
>set update channel to stable0 -
Or, if the issues someone is having in a beta are not debilitating, you can wait until the stable version has a version number > the stable version (including the build - like 41.1.6, the 6 matters). Once that happens, then you can set update channel to stable and get back without doing a full reinstall.
I do this many times - run on the beta versions; once the next stable release comes out, if there is a service release (like 40.1), that will not be on the beta channel, so I go back to stable and stay there until the first beta. Then I get any service releases.
0 -
I was under the impression that once a beta user sets update channel to stable, service releases would be skipped until the next major update, at which point the user would switch to the stable channel without the need for a fresh install.
0 -
See my post - it's all about full version numbers. If there is a version number > than what you are running on your currently set channel, you'll get the update. If not, you won't. Once on stable, the beta user will get the service releases because they will be a later version number than the last beta version number (which will match the pre-service release version on the stable channel)
1 -
This is generally true (and a good reminder: with the exception of rare unique circumstances, beta versions should not be used if people need their software to be reliably supporting their work e.g. as a pastor).
However, there is the situation where people can leave the beta easily (and this command simply works for that): when the beta version has become a Release Candidate and has shipped to stable and thus the stable version is identical to the beta version - and also, when there has been a Service release to stable and not yet a new beta (so stable is a higher/newer version).
This window of opportunity to switch from beta to stable closes with the arrival of the first beta of the next version.
Have joy in the Lord!
1 -
However, there is the situation where people can leave the beta easily (and this command simply works for that): when the beta version has become a Release Candidate and has shipped to stable and thus the stable version is identical to the beta version - and also, when there has been a Service release to stable and not yet a new beta (so stable is a higher/newer version).
People will usually want to leave beta immediately rather than wait for an RC to be shipped to stable! And why wait even longer for a Service Release as you seem to imply (SR 41.1.6 will be higher than the user's Beta for v.41 but that is irrelevant)..
In general, any new beta (higher version) is ignored after the switch to stable and any stable version cannot be higher than a current Beta version (by definition) i.e. current stable SR 41.1.6 vs. current beta 42.0.359.See my post - it's all about full version numbers. If there is a version number > than what you are running on your currently set channel, you'll get the update. If not, you won't. Once on stable, the beta user will get the service releases because they will be a later version number than the last beta version number (which will match the pre-service release version on the stable channel)
Just to clarify. If a user remains on the beta channel after the beta version has been released to stable, they can switch to stable (see below) and they will receive all stable releases, which will have a higher version number.
===================
The command
set update channel to stableworks as follows:If running a beta you shouldn’t receive an update until FL release a version greater than your beta (incl. RC's) to the stable channel. The version is the full numeric descriptor e.g. 42.0.359 (current beta).
If running a stable version (i.e. not running a beta) you stay on the stable channel. If a new beta is released you can switch to the beta channel (
set update channel to beta) or directly download the beta version.** A Release Candidate (RC) is a beta version until shipped to stable. Updates to stable versions are called Service Releases (SR's).
Dave
===Windows 11 & Android 13
0
