Dake topics incomplete

Leon Bible

I am a NEW Logos user coming from the WordSearch transition….

There is ONE WordSearch book that is NOW showing in Logos desktop:

DAKE TOPICS

PROBLEM – It ONLY shows topics from the book of Genesis!

Of course there are topics from the WHOLE Bible when you open it in WordSearch.

Is this something you are still working on.

HOPFULLY you will get the DAKE NOTES done quickly since I use it every day.

I think I am going to like Logos for many years to come.

Thanks
Leon Bible

Find more posts tagged with

Comments

Donald O. Ebert

When I began to seriously study the Bible back in 1973, all I had was my Dake's Study Bible. Like Leon Bible, I can't wait for the Dake's resources to be fully integrated into Logos.

Bradley Grainger (Logos)

PROBLEM – It ONLY shows topics from the book of Genesis!

I see this problem. I've reported it to the Content team so we can make sure we bring the full content of the resource over.

Leon Bible

https://community.logos.com/discussion/comment/1119486#Comment_1119486

THANKS so much!

Darnell L. Hope Sr.

https://community.logos.com/discussion/comment/1119486#Comment_1119486

I notice that my Dake's topic has the same problem, not all the contents.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1122081#Comment_1122081

This resource hasn't been updated with the full content yet.

Jeff Frazier

https://community.logos.com/discussion/comment/1122136#Comment_1122136

It still isn't working: completely broken and useless! CS told me the issue is known, and Logos has no intentions of fixing it.

MJ. Smith

https://community.logos.com/discussion/comment/1150086#Comment_1150086

CS told me the issue is known, and Logos has no intentions of fixing it.

Sorry to be rude but I don't believe you because.... As was said by a Faithlife employee above, it has not yet been fully converted.

This resource hasn't been updated with the full content yet.

As Bradley is directly involved in the process, I would take his word for it. What is troublesome is why CS left you believing that there was no intention of fixing it. That is a serious issue for FL to review.

Kyle G. Anderson

https://community.logos.com/discussion/comment/1150092#Comment_1150092

FWIW, the updated resource is scheduled to be delivered late-February.

Jeff Frazier

https://community.logos.com/discussion/comment/1150092#Comment_1150092

CS told me the issue is known, and Logos has no intentions of fixing it.

Sorry to be rude but I don't believe you because.... As was said by a Faithlife employee above, it has not yet been fully converted.

This resource hasn't been updated with the full content yet.

Your "rudeness" doesn't bother me. What does bother me is why you felt the need to engage in this conversation at all. Do you work for Logos? If not, why waste your precious time defending them against anyone who dares to raise an issue? You've done nothing but waste my time and make Logos look like a group of elitists whose software is some fine wine to be enjoyed only by the privileged few who are cultured enough to appreciate it. I also don't care whether or not you believe me because I certainly can't believe you.

Jeff Frazier

https://community.logos.com/discussion/comment/1150099#Comment_1150099

Thank you! I hope so.

SineNomine

https://community.logos.com/discussion/comment/1150100#Comment_1150100

Do you work for Logos?

No, she doesn't. (Neither do I.) People who work for Faithlife (which was called Logos Bible Software until late 2014), like Bradley and Kyle, get that green fire logo under their names.

Joe McCune (Faithlife)

https://community.logos.com/discussion/comment/1150086#Comment_1150086

It still isn't working: completely broken and useless! CS told me the issue is known, and Logos has no intentions of fixing it.

Jeff, I have reviewed the notes from your call to Customer Support. The notes make it obvious that the employee was trying to convey to you that we were going to produce an improved version of this resource, but they were not sure how soon it would be available.

Sometimes our words fail to convey what we mean. Sometimes we misspeak without realizing it. Obviously the communication was not as clear as it should have been. But the employee did not mean to convey that the resource would never be improved.

Please accept my apologies. We'll try to do better next time.

Jeff Frazier

https://community.logos.com/discussion/comment/1150239#Comment_1150239

Joe McCune said: "Jeff, I have reviewed the notes from your call to Customer Support. The notes make it obvious that the employee was trying to convey to you that we were going to produce an improved version of this resource, but they were not sure how soon it would be available.

Please accept my apologies. We'll try to do better next time."

I never said that the employee with whom I spoke said that. I am saying that Logos has no intentions of fixing it, thus the comma before "and." That call and this forum are both months old now, so I have little hope at this point of it ever being fixed or my other broken resources.

Your apology is noted, but sorry doesn't fix anything. What you should've done instead, after reviewing my notes, was determine a timeline for fixing the issue rather than trying to make me out to look like a liar or a dolt. Ironically, you made yourself look silly by failing to remember what we were all taught in third-grade English.

SineNomine

https://community.logos.com/discussion/comment/1150297#Comment_1150297

Ironically, you made yourself look silly by failing to remember what we were all taught in third-grade English.

I think he preferred to choose the possibility that you were misusing a comma over the possibility that you were asserting that his coworkers are liars.

Jeff Frazier

https://community.logos.com/discussion/comment/1150303#Comment_1150303

I wasn't the one misusing a comma. Commas go before conjuctions when they are separating two independent clauses. The exception to that rule is to omit the comma if both clauses convey the actions of the introductory clause. Moreover, I stated that CS did promise that Logos was going to fix the problem, in another forum.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/1150297#Comment_1150297

... determine a timeline for fixing the issue ...

In Nov 2005, Logos Blog publicly announced confidence about Logos for Mac version 1 shipping by June 2006, but initial public release of Logos for Mac 1 shipped in Dec 2008 (almost 2.5 years later than announced confident timeline prediction, which was disappointing to anxiously waiting Mac users). Ongoing effect is Faithlife usually does not share internal timeline estimates for customer delivery.

Thankful for Faithlife employee reply earlier in this thread: (thus hoping for Logos Research Edition delivery of Dake's topics next month)

Kyle G. Anderson">
FWIW, the updated resource is scheduled to be delivered late-February.

Nine years ago, creating a Personal Book Bible => American Standard Version 1901 - Personal Bible without Chapter and Verse #'s having Bible fields, milestones, and red letter helped me greatly appreciate tagging and typographical accuracy in Logos Research Edition resources (especially Bibles). Thankful for later Logos version having Visual Filter to hide chapter and verse numbers, which is usable in most Bibles. Thankful for Faithlife now having ASV Bible NT Reverse Interlinear and ASV Bible OT Reverse Interlinear for 1901 American Standard Version (ASV)

FWIW: hardcopy Dake's study Bible is a bit bigger than most printed study Bibles, but substantially smaller than thousands of commentary resources available for Logos & Verbum. My primary commentary set is UBS Translation handbooks => UBS Handbooks Series: Old Testament, New Testament, and Deuterocanonical Books (66 vols.) Logos Wiki Logos Resource Reviews includes UBS New Testament Handbook Series and UBS Old Testament Handbook Series

Keep Smiling [:)]

Ted Hans

https://community.logos.com/discussion/comment/1150297#Comment_1150297

What you should've done instead, after reviewing my notes, was determine a timeline for fixing the issue rather than trying to make me out to look like a liar or a dolt.

FWIW, the updated resource is scheduled to be delivered late-February.

A timeline of fixing the problem has been given by Kyle another Logos Employee.

Kind regards

MJ. Smith

https://community.logos.com/discussion/comment/1150297#Comment_1150297

I am saying that Logos has no intentions of fixing it, thus the comma before "and." That call and this forum are both months old now, so I have little hope at this point of it ever being fixed or my other broken resources.

I know you've said you don't believe me, but I assume you are aware that Faithlife has made it possible to check the status or resources and see the progress that is being made? Status of your Wordsearch Library - Faithlife Forums (logos.com)

Tim Pace

https://community.logos.com/discussion/comment/1150305#Comment_1150305

Hey Jeff

Don't be a jerk. Nobody wants to be bullied and that's the way you sound to me. But of course, I could be wrong like everyone else.

Have a great day

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/1150099#Comment_1150099

FWIW, the updated resource is scheduled to be delivered late-February.

Thankful for two Dake pre-orders "in progress" (no shipping date yet):

Noticed Wordsearch Catalog shows four other Dake resources as Logos Research Edition, which lack Logos.com PDP's.

While considering Logos 9 Library Expansion sale items => https://www.logos.com/library-feature-expansion am wondering about Wordsearch Library Expansion Bundle(s) ? The Ultimate Master Expansion Collection does not include Dake's, ... plus the Dake pre-orders do not show being in any bundles/collections.

Keep Smiling [:)]

MWW

https://community.logos.com/discussion/comment/1152634#Comment_1152634

wondering about Wordsearch Library Expansion Bundle(s) ?

I have wondered about that myself. Surely there must be a number of people who would be interested in WORDsearch packages

MWW

https://community.logos.com/discussion/comment/1152634#Comment_1152634

wondering about Wordsearch Library Expansion Bundle(s) ?

I have wondered about that myself. Surely there must be a number of people who would be interested in WORDsearch packages

AJ Kerezy

Yes.....P L E A S E...........It's so frustrating that the Dake material isn't indexed and integrated with the Bibles (like it was in Wordsearch). It's going on a month or two months already.

Is there a TIMELINE for completing the work to bring Logos up to where Wordsearch was already at?

It seems they're pushing their new version (9), and supposed improvements while those of us from Wordsearch are stuck with next to worthless books/commentaries, etc. - and software that crashes.

PLEASE give us back the basic functionality we had all along in Wordsearch.

MJ. Smith

https://community.logos.com/discussion/comment/1153263#Comment_1153263

It seems they're pushing their new version (9), and supposed improvements while those of us from Wordsearch are stuck with next to worthless books/commentaries, etc. - and software that crashes.

It may seem that way to you ... but to longtime Logos owners it seems like the unreleased products in Logos 9 are taking a long time to appear in our libraries. Wordsearch owners still can run Wordsearch and have the functionality. Logos 9 users have no alternative. So please be patient with FL and support their ability to work without unnecessary pressures. We'll all gain in the long run.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/1153263#Comment_1153263

Yes.....P L E A S E...........It's so frustrating that the Dake material isn't indexed and integrated with the Bibles (like it was in Wordsearch). It's going on a month or two months already.

Appreciate frustration. Thankful for two Dake pre-orders "in production" (no shipping date yet):

Is there a TIMELINE for completing the work to bring Logos up to where Wordsearch was already at?

Suggest reading my earlier reply in this thread: Faihthlife Corporate lesson learned from missing an earlier public announced timeline (by ~2.5 years) is seldom sharing internal timeline estimates (guesses) with customers (includes Many Volunteer Posters like myself).

Thread => New Wordsearch books being added to Logos includes Wed 21 Oct 2020 reply about resource conversion taking longer than initially anticipated (personally not surprised due to typographical quality & tagging of Logos Research Edition resources).

Thread => WordSearch Books need major editing includes Faithlife replies on 3 Feb 2021 about Wordsearch resource updates are actively in progress at various stages plus mentioned 100 resource updates shipped recently, with many more expected in the coming weeks.

It seems they're pushing their new version (9), and supposed improvements while those of us from Wordsearch are stuck with next to worthless books/commentaries, etc. - and software that crashes.

Concur automated eBook conversion of commentary resources has opportunities for improvement. Caveat: Faithlife Corporation has over 100,000 digital resources available for purchase so wallet may cry a lot [:'(] while expanding commentary collection in library: e.g. a custom series of the Top Two Commentary Resources => https://www.bestcommentaries.com/topcommentaries/ is doable (more depth & breadth than Dake's).

Faithlife Development places a high priority on quickly fixing software crashes. Logos Help Center (LHC) includes:

Thankful for a number of active Faithlife Forum participants, who have experience troubleshooting crash issues. Thankful for Faithlife Technical Support [:D]

Keep Smiling [:)]

Mike Binks

https://community.logos.com/discussion/comment/1153263#Comment_1153263

PLEASE give us back the basic functionality we had all along in Wordsearch.

It is my understanding that you still have 'the basic functionality you had all along in Wordsearch' has your version ceased functioning?

and software that crashes.

I assume that you are referring to the Logos software rather than your installation of Wordsearch.

If the former it would be a good idea to start another thread detailing the problem. It helps to attach log (see my signature) and to tell us about your system OS version and Logos version. It might be useful to attach (using the paper clip above) a screenshot of the situation just before a repeatable crash.

There are many users here who have tackled a wide variety of problems and are likely to be able to help out with practical advice.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1154306#Comment_1154306

PLEASE give us back the basic functionality we had all along in Wordsearch.

It is my understanding that you still have 'the basic functionality you had all along in Wordsearch' has your version ceased functioning?

See the OP: https://community.logos.com/forums/p/194101/1119350.aspx#1119350

The file we converted from was incomplete, and so is the current version of the resource in Logos.

Mike Binks

https://community.logos.com/discussion/comment/1154388#Comment_1154388

PLEASE give us back the basic functionality we had all along in Wordsearch.

It is my understanding that you still have 'the basic functionality you had all along in Wordsearch' has your version ceased functioning?

See the OP: https://community.logos.com/forums/p/194101/1119350.aspx#1119350

The file we converted from was incomplete, and so is the current version of the resource in Logos.

Bradley

I understand that the Logos conversion of this resource is still a 'work in progress.

Are you indicating that the file, that was available in Wordsearch, was also faulty in the way reported so that the resource does not work in that program?

If not my point is valid, ie that nothing of the 'basic functionality (that is) in Wordsearch' has been taken away. It just has not been made available in Logos yet.

Jeff Frazier

https://community.logos.com/discussion/comment/1150326#Comment_1150326

The timeline was wrong. The resource is still broken and doesn't work, even the web app.

Jeff Frazier

https://community.logos.com/discussion/comment/1150309#Comment_1150309

... determine a timeline for fixing the issue ...

In Nov 2005, Logos Blog publicly announced confidence about Logos for Mac version 1 shipping by June 2006, but initial public release of Logos for Mac 1 shipped in Dec 2008 (almost 2.5 years later than announced confident timeline prediction, which was disappointing to anxiously waiting Mac users). Ongoing effect is Faithlife usually does not share internal timeline estimates for customer delivery.

Thankful for Faithlife employee reply earlier in this thread: (thus hoping for Logos Research Edition delivery of Dake's topics next month)

Kyle G. Anderson">
FWIW, the updated resource is scheduled to be delivered late-February.

Nine years ago, creating a Personal Book Bible => American Standard Version 1901 - Personal Bible without Chapter and Verse #'s having Bible fields, milestones, and red letter helped me greatly appreciate tagging and typographical accuracy in Logos Research Edition resources (especially Bibles). Thankful for later Logos version having Visual Filter to hide chapter and verse numbers, which is usable in most Bibles. Thankful for Faithlife now having ASV Bible NT Reverse Interlinear and ASV Bible OT Reverse Interlinear for 1901 American Standard Version (ASV)

FWIW: hardcopy Dake's study Bible is a bit bigger than most printed study Bibles, but substantially smaller than thousands of commentary resources available for Logos & Verbum. My primary commentary set is UBS Translation handbooks => UBS Handbooks Series: Old Testament, New Testament, and Deuterocanonical Books (66 vols.) Logos Wiki Logos Resource Reviews includes UBS New Testament Handbook Series and UBS Old Testament Handbook Series

Keep Smiling

Well, it looks as if they missed the timeline again, because my Dake resource still doesn't work. I cannot believe that ANYONE thinks this software is even decent, much less the Rolls Royce of bible software. All of the resources they have transitioned from WordSearch to this platform are far less functional and very poorly laid out. Nothing is integrated. My old WS app took two seconds to load and navigation within the app was instantaneous and very intuitive. Even the web version of Logos gives you the circle of death when trying to load a page.

Thank you for the info above, but I will be looking elsewhere. I have no confidence whatsoever that Logos cares nor is capable of making anything that works properly for end users.

Simon’s Brother

https://community.logos.com/discussion/comment/1152616#Comment_1152616

Hey Jeff

Don't be a jerk. Nobody wants to be bullied and that's the way you sound to me. But of course, I could be wrong like everyone else.

Have a great day

Tim ,Jeff feels last though he is the outsider being bullied. And I understand why he felt bullied and responded accordingly. Your response to him is only reinforcing his experience that if you say something negative about your experience with FL people will tell you tell you that’s not a done thing.

FL created this problem by choosing to dump auto-converted e-pub files of Wordsearch books into every ones libraries which they should have known were not going to function as well as as they did in Wordsearch and then expected users with no experience of Logos to grasp the difference of a fully formatted Logos book and understand that these cheap imitations that were dumped in their libraries would be updated at some point with no guidance as to when this would happen.

The defenders of FL who want to have a go at people like Jeff need to take of their rose coloured glasses, step back and walk in other people’s shoes if they can. Telling people they are liars or telling them about what happened with Logos 1 for MAC is not going to help someone in Jeff’s conundrum. It’s a shame after all these years some MVP’s still haven‘t learnt that dealing with an upset person is not solved by having a go at them or telling them for being upset.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1154450#Comment_1154450

Are you indicating that the file, that was available in Wordsearch, was also faulty in the way reported so that the resource does not work in that program?

No. It was complete in Wordsearch, but incomplete in Logos.

Kyle G. Anderson

https://community.logos.com/discussion/comment/1156227#Comment_1156227

The timeline was wrong. The resource is still broken and doesn't work, even the web app.

Our apologies on this. Both Dake's Topics and Dake's Study Notes are ready to go on our end but we've hit an unusual technical hurdle in making them available to you.

Jeff Frazier

https://community.logos.com/discussion/comment/1156246#Comment_1156246

Thank you. I hope they fix this.

Jeff Frazier

https://community.logos.com/discussion/comment/1156242#Comment_1156242

Hey Jeff

Don't be a jerk. Nobody wants to be bullied and that's the way you sound to me. But of course, I could be wrong like everyone else.

Have a great day

Tim ,Jeff feels last though he is the outsider being bullied. And I understand why he felt bullied and responded accordingly. Your response to him is only reinforcing his experience that if you say something negative about your experience with FL people will tell you tell you that’s not a done thing.

FL created this problem by choosing to dump auto-converted e-pub files of Wordsearch books into every ones libraries which they should have known were not going to function as well as as they did in Wordsearch and then expected users with no experience of Logos to grasp the difference of a fully formatted Logos book and understand that these cheap imitations that were dumped in their libraries would be updated at some point with no guidance as to when this would happen.

The defenders of FL who want to have a go at people like Jeff need to take of their rose coloured glasses, step back and walk in other people’s shoes if they can. Telling people they are liars or telling them about what happened with Logos 1 for MAC is not going to help someone in Jeff’s conundrum. It’s a shame after all these years some MVP’s still haven‘t learnt that dealing with an upset person is not solved by having a go at them or telling them for being upset.

Thank you. I hope they can fix it.

Jeff Frazier

https://community.logos.com/discussion/comment/1156246#Comment_1156246

The timeline was wrong. The resource is still broken and doesn't work, even the web app.

Our apologies on this. Both Dake's Topics and Dake's Study Notes are ready to go on our end but we've hit an unusual technical hurdle in making them available to you.

Thanks for responding. I hope Logos can fix this. I want to be able to buy other resources in the future and not be stuck with just what I have in my old WS library forever.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/1156228#Comment_1156228

The timeline was wrong. The resource is still broken and doesn't work, even the web app.

Our apologies on this. Both Dake's Topics and Dake's Study Notes are ready to go on our end but we've hit an unusual technical hurdle in making them available to you.

Thanks for responding. I hope Logos can fix this. I want to be able to buy other resources in the future and not be stuck with just what I have in my old WS library forever.

From past experiences with Faithlife Corporation, am anticipating fix, but not know how soon from user perspective: possibly Dake's will need software change(s) so will have a minimum release level for usage (could be 8.17 SR-# & 9.#)

Wallet warning is Faithlife offering over 100,000 digital resources (so library can have lots of resources, which is useful for topical searching). Base Packages tend to have the best discount per resource.

I cannot believe that ANYONE thinks this software is even decent, much less the Rolls Royce of bible software.

One Rolls Royce feature is Visual Filter highlighting, which allows me to "see" range of nuanced Greek verbal expression in English & Greek (also usable in any resource having Logos Greek Morphological tagging, which includes Bibles having Greek Reverse Interlinear)

1 Thessalonians 5 has the most imperative mood verbs in one New Testament chapter. When learning Greek, remember teacher explaining imperative mood using an example with dogs: when we command a dog to 'SIT', we use imperative tone of voice (mood) while expecting dog to SIT (hear & obey). A lesson learned doing my own stilted literal translation of Jude from Greek to English is Greek verbal action intensity is typically lacking in English verbal expression (primary English focus is time of action, which is secondary in Greek verbal focus of action intensity & time).

Logos Wiki => Extended Tips for Highlighting and Visual Filters includes:

Examples of visual filters

Thankful for Faithlife enabling the free sharing of User Documents, which includes Visual Filters. Thankful for free Logos 9 Basic & Verbum 9 Basic with Lexham Intro Collection (5 vols.) being able to freely use Logos Greek Morphology visual filters. Following Faithlife group Logos Visual Filters allows Visual Filter documents to be copied (from Logos Visual Filters Group) using Docs menu: click to select Visual Filter followed by clicking "Add to your docs"

Years ago, Thankful for Logos 4 Mac alpha & beta releases => Mac Release Notes and History that seemed like opening Christmas gifts every couple weeks as Faithlife enabled Mac User Interface for Logos Bible Software capabilities (took about a year for stable usable Logos 4 Mac implementation followed by two more years for 99% feature parity between Windows and Mac).

My old WS app took two seconds to load and navigation within the app was instantaneous and very intuitive.

Logos & Verbum are library database applications, which take awhile to load (so have had to learn to click once & wait, which is an ongoing annoyance). Personally not like the search show-off default in Logos & Verbum that wants to do lots of searches while causing user interaction with interface to wait: e.g. opening a Bible that has many visual filters (searches running & being combined) so changing verse waits to pop-up menu to appear (several times my typing of a new location has been ignored). After visual filter highlights have populated, navigation is noticeably quicker.

Another Rolls Royce feature is quickly finding topical information in a digital library: e.g.

([field heading,largetext] software) WITHIN 33 WORDS (library,fast)

took 0.51 seconds to search a digital library that has Logos 9 Ultimate (includes Verbum 9 Ultimate) & Ultimate Master Expansion Collection (3,395 Resources) & Master Journal Bundle 5.3 (2,345+ vols.) plus Challies Recommends Best New Testament Commentaries (20 vols.), March Matchup winners, free Perseus Collections, free Book of the Month, ..., which are useful for forum & Faithlife discussions.

Winter 2007 review included three Bible Software choices with one still in business nearly 14 years later:

OT: Bibleworks ceases operation as of June 15, 2018 with Faithlife CEO posting => Faithlife and Logos Bible Software: Here for the long haul!

Thread => Gramcord discussion mentions Gramcord web site has 2010 copyright (lacks active development for over a decade).

Thank you for the info above, but I will be looking elsewhere. I have no confidence whatsoever that Logos cares nor is capable of making anything that works properly for end users.

Respectfully disagree about Faithlife caring and making software that works (albeit does a learning curve for effective use). For me, other software choices lack ability for me to "see" nuanced range of Greek verbal expression (Accordance can quickly find imperative mood verbs, but cannot combine thousands of search results for simultaneous display).

Thread started on 22 Jul 2010 => Accordance, Bible Explorer, Biblesoft, BibleWorks, Laridian, Olive Tree, Quickverse, WORDsearch... mentions software alternatives by name (plus cognizant relatively few still having active development in 2021).

Thread started on 23 Mar 2015 => Logos Original Language Improvements Vs Accordance 11

Thread started on 31 Aug 2017 => Accordance for Windows vs Logos 7 (includes links to several Bible software comparison threads)

One more Rolls Royce aspect is Faithlife forums for interaction with Faithlife and users around the world. Thankful for many friendly forum and Faithlife discussions: have learned a lot plus have a lot to learn.

Keep Smiling [:)]

Jeff Frazier

https://community.logos.com/discussion/comment/1156318#Comment_1156318

The Logos web app even struggles to load pages. I am very disappointed that they turned something very simple and easy to use into a fragmented mess that will not load properly half of the time. The Logos 8 app was extremely slow and clunky. Who cares which features it has if it fails to perform basic functions well?

Simon’s Brother

https://community.logos.com/discussion/comment/1156318#Comment_1156318

There are lots of great features of the software but these are only as good as the tagging of the resources. FL dumped poorly prepared Wordsearch resources into the software which is going to leave previous WS only users with a bad experience of their preferred resources until FL updates them and that is happening on a weekly basis but with no knowledge of when particular resources will be updated. This weekly release means their libraries will be re-indexing potential every week creating another negative experience of the software.

Rolls Royce features are useless without properly tagged resources.

MJ. Smith

https://community.logos.com/discussion/comment/1156324#Comment_1156324

The Logos web app even struggles to load pages. I am very disappointed that they turned something very simple and easy to use into a fragmented mess that will not load properly half of the time. The Logos 8 app was extremely slow and clunky. Who cares which features it has if it fails to perform basic functions well?

What on earth are you trying to run it on? What are your specs? Or do you live on the outskirts of the boondocks where connectivity is questionable? (don't laugh -- I have relatives that do). Most of us have no problem with it loading, and do not find the app slow and clunky. We do find it sloppy and inconsistent but that's a far different story.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1156327#Comment_1156327

The Dake resources, in particular, because they were automatically converted from Wordsearch have over 1MB of content in a single "article" (named "Title Page"); this is likely not going to perform well in the web app.

This will be fixed in the updated version of the resources that are ready to publish. We almost resolved all the issues that stopped them being published today, but ran into one final snag. I'm hopeful that can be fixed tomorrow.

Kyle G. Anderson

https://community.logos.com/discussion/comment/1156335#Comment_1156335

Updated versions of Dake's Topics and Dake's Annotated Reference Bible were published this morning.

Jeff Frazier

https://community.logos.com/discussion/comment/1156414#Comment_1156414

Updated versions of Dake's Topics and Dake's Annotated Reference Bible were published this morning.

Thank you. It is finally working! Also, thanks for actually helping to fix the issue rather than giving me the troll answers I've been getting from others who ignore everyone else who has been saying this resource was broken.

Jeff Frazier

https://community.logos.com/discussion/comment/1156327#Comment_1156327

The Logos web app even struggles to load pages. I am very disappointed that they turned something very simple and easy to use into a fragmented mess that will not load properly half of the time. The Logos 8 app was extremely slow and clunky. Who cares which features it has if it fails to perform basic functions well?

What on earth are you trying to run it on? What are your specs? Or do you live on the outskirts of the boondocks where connectivity is questionable? (don't laugh -- I have relatives that do). Most of us have no problem with it loading, and do not find the app slow and clunky. We do find it sloppy and inconsistent but that's a far different story.

Please see the conversation below. The issue, which was real, has been resolved. It had nothing to do with my OS nor my Internet speed. It was a known issue, and it has finally been resolved. In the future, it would behoove you to enlighten yourself of facts such as those rather than making assumptions. In this case, all of your assumptions were incorrect, and you would've known that had you done a little research of your own rather than firing off pithy remarks to me.

Jeff Frazier

https://community.logos.com/discussion/comment/1156335#Comment_1156335

The Dake resources, in particular, because they were automatically converted from Wordsearch have over 1MB of content in a single "article" (named "Title Page"); this is likely not going to perform well in the web app.

This will be fixed in the updated version of the resources that are ready to publish. We almost resolved all the issues that stopped them being published today, but ran into one final snag. I'm hopeful that can be fixed tomorrow.

Fixed! Thank you for helping rather than blaming me for the issue.

MJ. Smith

https://community.logos.com/discussion/comment/1156435#Comment_1156435

Please see the conversation below.

I did when it was posted. If you had said that a particular resource rather than the entire app had a problem, I would have given a very different response -- much more similar to Bradley's.

Jeff Frazier

https://community.logos.com/discussion/comment/1156467#Comment_1156467

Please see the conversation below.

I did when it was posted. If you had said that a particular resource rather than the entire app had a problem, I would have given a very different response -- much more similar to Bradley's.

What are you talking about? I did say that it was this particular app. In fact, this entire forum is about the Dake resource. It wouldn't run on any computer nor on the web app before, but now it is fixed.

Mike Binks

https://community.logos.com/discussion/comment/1156591#Comment_1156591

I did say that it was this particular app. In fact, this entire forum is about the Dake resource. It wouldn't run on any computer nor on the web app before, but now it is fixed.

Good morning Jeff (at least that is what it is here in the UK)

It seems that there are some cross wires due to understanding of terms. For most users here would have this understanding

App = the Logos Engine

Forum = the "Wordsearch Bible Software" forum and all the "threads" therein.

Thread = the list of posts on one particular subject with the same heading (in this case "Dake topics incomplete".

Resource = a particular publication (In this case 'Dake topics'.

I do wish James had been more specific about email when he wrote about the use of the tongue but hey ho.