BUG: Morphy query builder documents don't return all of Romans

If you create a Morph Query Document and search within "Romans", you'll only get results for Romans 1-10 or so. Romans 11-16 will be missing.

A search for just the definite article within Romans only returned chapters 1-6.

I haven't tested this on other books to see if a similar type of error occurs.

Find more posts tagged with

Comments

Fr Devin Roza

If I search for Romans 1-8 I only get results from Romans 1-4.

Philana R. Crouch

Fr. Devin,

Can you provide a screenshot of what your search document looks like?

Fr Devin Roza

https://community.logos.com/discussion/comment/860427#Comment_860427

Fr. Devin,

Can you provide a screenshot of what your search document looks like?

Sure. Here are three examples of this type of bug.

1. For this search here:

I only get results displayed for Romans 1-12, even though the number of results and verses counted in the search results is correct for Romans 1-16.

2. If I limit myself to Romans 1-8, same thinig, but now only results for Romans 1-4 are displayed:

3. If I search for simply a definite article, like this:

...then I only get results displayed for Romans 1-6.

Dave Hooton

https://community.logos.com/discussion/comment/861009#Comment_861009

I can reproduce your results for these cases!

Scott Fleischman

https://community.logos.com/discussion/comment/861020#Comment_861020

Thanks for the report. We'll fix it.

Philana R. Crouch

https://community.logos.com/discussion/comment/861009#Comment_861009

Fr. Devin,

Can you provide a screenshot of what your search document looks like?

Sure. Here are three examples of this type of bug.

Fr. Devin,

Thanks for providing this. I'll do some investigating, and I hope to get back to you after the weekend.

Philana R. Crouch

If you create a Morph Query Document and search within "Romans", you'll only get results for Romans 1-10 or so. Romans 11-16 will be missing.

A search for just the definite article within Romans only returned chapters 1-6.

I haven't tested this on other books to see if a similar type of error occurs.

This should be fixed in 7.2 Beta 4