Resource bug: extra answer spaces

Barry, John D. Colossians: Being Like Jesus. Not Your Average Bible Study. Bellingham, WA: Lexham Press, 2014.

I was just checking this new resource out, thinking about the space to enter answer (standard size, export, clear, link ... issues) when I ran into answer boxes with no corresponding questions.

Find more posts tagged with

Comments

Fred Chapman

Perhaps those are there to give the user a space to record their own thoughts on each point.

Rich DeRuiter

Besides the obvious lack of question, and the corresponding bewilderment of what to do in the box, I would not agree with the premises either. In respect for forum guidelines I won't be more specific.

MJ. Smith

https://community.logos.com/discussion/comment/613541#Comment_613541

Perhaps those are there to give the user a space to record their own thoughts on each point.

Ouch you are tempting me to violate guidelines. But I'll behave. If they appeared elsewhere, I'd agree with you but this appears to be unique.

Thomas Ball

https://community.logos.com/discussion/comment/613655#Comment_613655

I agree that what is expected to be entered there is not entirely clear. Where in the book is this?

MJ. Smith

https://community.logos.com/discussion/comment/614392#Comment_614392

When Paul says that Christ was the “firstborn” of creation in Colossians 1:15, he is making two points:

    1.      Jesus is the first eternal, spiritual being made flesh and born as a human


    2.      Jesus is the head of all of creation—the one in charge.


If Christ is in charge of creation and holds a unique position, what is there to fear? How would your life look different if you fully embraced Christ as the one in charge of your life?

John D. Barry, Colossians: Being Like Jesus, Not Your Average Bible Study (Bellingham, WA: Lexham Press, 2014), 23.

NB.Mick

https://community.logos.com/discussion/comment/614480#Comment_614480

... which is at logosres:nyabs72col;ref=Bible.Col1.15-23;off=1166

Dylan Rondeau

https://community.logos.com/discussion/comment/614480#Comment_614480

To clarify: It is most helpful, when we testers ask for a location of an issue in a resource (or even in the initial report!) to:

With the resource open and the error in the panel,
Open the resource menu by clicking the cover in the top left, and
Click the "URL" button under "Copy location as" and
Paste that into the post.

Rather than having to open the resource and CTRL + F, or scroll to pages, or jump through the TOC, we can just copy/paste that URL into the Command Box and we're instantly looking at the issue you've reported.

Including these links makes our life a whole lot easier, and us being able to reproduce/verify your errors faster means we're able to report them faster. It also saves you the trouble of selecting, copying, pasting, and citing the sections; just 2 clicks and a paste! [:D]

Edit: NB.Mick did exactly what I was describing as I was describing it. Thanks! We'll get this reported. [:)]

MJ. Smith

https://community.logos.com/discussion/comment/614492#Comment_614492

Okay ....

NB.Mick

https://community.logos.com/discussion/comment/614492#Comment_614492

Edit: NB.Mick did exactly what I was describing as I was describing it. Thanks! We'll get this reported.

Dylan,

I appreciate your thanks - and I get that you like us users to provide you with meaningful information to locate the issues.

However, from my understanding, in this thread and the other one dealing with the same resource, the information in MJ's original report was sufficiently clear to locate the single place in the resource - actually it would have been faster to use Ctrl-F from you guys' side than to ask for the location here, which thus didn't come accross as very repectful for me.

My meddling in these threads wasn't meant to show MJ how to properly report bugs (she forgot more than I'll ever find, as the old song goes;-) but to help out before the issue is deflected again.

Mick

Dylan Rondeau

https://community.logos.com/discussion/comment/614503#Comment_614503

which thus didn't come accross as very repectful for me.

I sincerely apologize if I came across as disrespectful, as that was not my intention. This wasn't meant to prove a point or chastise anyone, and perhaps including it as a reply to MJ gave that impression. If so, I apologize, and perhaps this information would be more suited as a sticky thread of its own for general information. It was relevant to the discussion, and was meant as an explanation as much as information (to clarify what Tommy was asking for), so I posted here.

I also had no intention of saying "Mick did it right, MJ didn't" (though I can see how that could be interpreted, sorry [:(]). That was poor phrasing on my part. I just wanted to acknowledge your post so you didn't reply "Yeah, that's what I just did".

it would have been faster to use Ctrl-F from you guys' side than to ask for the location here

You are correct, as that is the case for this particular thread. However, when you handle bugs on the forum a lot, and you get a lot of threads that could benefit from additional information, in the long run it is a lot more efficient to clarify what information is helpful to have than ask for additional info case-by-case over time.

I get that you like us users to provide you with meaningful information to locate the issues.

And that's really the motivation behind my post. I just wanted to clarify what information will make things easier in the future, for both posters and testers. And from our end, the easier it is to understand what the issue is and get to it/reproduce it quickly, the sooner we can get it reported, and the time-savings from using a URL in the post also saves time when a dev looks at the case and tries to reproduce it themselves; It's win-win-win.

Again, I apologize if I was disrespectful in any way. I hope that I have clarified my intentions, and we greatly appreciate the effort you all put in to help us catch these issues. [:)]

Fred Chapman

https://community.logos.com/discussion/comment/613655#Comment_613655

Perhaps those are there to give the user a space to record their own thoughts on each point.

Ouch you are tempting me to violate guidelines. But I'll behave. If they appeared elsewhere, I'd agree with you but this appears to be unique.

Not sure how my theory was in any way an attempt to tempt you or Richard to violate forum guidelines in responding. I was merely suggesting the possible mindset associated with including the text boxes. Clearly from Dylan's post(s) it is in fact an editing / QA error. I will refrain from offering opinions and suggestions related to your posts in the future so as not to tempt you to violate forum guidelines.

MJ. Smith

https://community.logos.com/discussion/comment/614679#Comment_614679

Not sure how my theory was in any way an attempt to tempt you or Richard to violate forum guidelines in responding.

Sorry, my humor and my frustration got the best of me. My temptation was snide as in "they want you to think?" or theological as in "is that a 'have you quit beating your wife'" fallacy ... Please continue to tempt me.