BUG: Can't click a resource in Search, only in Passage or Exegetical Guide
Hello,
I have a problem when clicking a resource which comes up in search. I can click and see a resource in any other guide or method, but search. When I try to click a resource after I search collections or anything in the library, it does nothing.
I tried to send logs here and I was unsuccessful. I have sent the logs to support via email. I am resetting channel to stable and reinstalling without the Beta.
Thanks,
Jim
http://www.patheos.com/blogs/jimerwin/ - a postmodern pastor in a digital world
Comments
-
Hi Jim
I know from other posts you are running on a Mac which is helpful to know
assuming you haven't deleted it yet can you post a screenshot of the search results and indicate what you are clicking with no response?
Graham
0 -
Jim Erwin said:
I tried to send logs here and I was unsuccessful
Believe that problem has now been fixed.
Jim Erwin said:I have a problem when clicking a resource which comes up in search.
Believe I can identify this problem; thanks for finding it. Doubt that logs will help the developers find the problem.
This works as it should
The problem occurs when clicking the title of an individual article.
As a temporary workaround, you can click the first hit and then scroll to the beginning of the article.
Graham, can you verify this problem on Windows? Or is it strictly a Mac issue?
0 -
Hi Jack
Well done on tracking this down[Y]
Jack Caviness said:Graham, can you verify this problem on Windows?
This doesn't occur on Windows so it looks like a Mac-specific issue
Graham
0 -
Graham Criddle said:Jack Caviness said:
Graham, can you verify this problem on Windows?
This doesn't occur on Windows so it looks like a Mac-specific issue
Concur Logos 5.2b Beta 3 on OS X is tantalizingly non-functional. The Blue Link has mouse pointer change to a hand, but clicking Blue Link does nothing and cannot drag Blue Link to a new tab.
Keep Smiling [:)]
0 -
Thanks for reporting this; it will be fixed in the next Beta.
Mac Developer
Faithlife0 -
-
This should be fixed in 5.2b beta 4. [:)]
0 -