Buzz: Product Feedback

Issues with a pdf showing up in Buzz (from Sara Wietbrock)

Follow
Implemented feature idea or fixed bug
Jeremy Walker

Sara was giving tests today that contain a link that allows another window to open up with the pdf of a reading passage that the students need for the test.

This test was written in BH using the Advanced Editor.  The code looked like this:

Type: MC
Score: 1
1) [HTML]<div>READING COMPREHENSION: Click <a href="[~]/2nd%20Nine%20Weeks/Stage%206/Stage6TestStory.pdf?attachment=1" target="_blank">here</a> to access the reading passage. You may keep the reading passage open for questions 1-15.</div><div>&nbsp;</div><div>Where are Caecilius and Metella going?</div>[/HTML]

This worked fine in BrainHoney, but student received an error when they tried to click on the link in Buzz.

We learned that if we eliminated this portion ?attachment=1 then it would work in Buzz just as it had worked in BrainHoney.

So, this works:

Type: MC
Score: 1
1) [HTML]<div>READING COMPREHENSION: Click <a href="[~]/2nd%20Nine%20Weeks/Stage%206/Stage6TestStory.pdf" target="_blank">here</a> to access the reading passage. You may keep the reading passage open for questions 1-15.</div><div>&nbsp;</div><div>Where are Caecilius and Metella going?</div>[/HTML]

Both versions worked fine for the teacher when previewing the test in Buzz which is why she didn't realize there was a problem.  The first version didn't work for the students in Buzz.  The second version did work for us using a test enrollment that had been created via BH.

Hope this helps,

Jeremy

Comments (4)

Sort by
Jeremy Walker

This was the error message the students were seeing.

This XML file does not appear to have any style information associated with it. The document tree is shown below.

<response code="Format" message="String was not recognized as a valid Boolean." errorId="8dfe2ae779eb444897670793471df0c3">

<detail>String was not recognized as a valid Boolean.</detail>

</response>

0 Comment actions Permalink
Brad Marshall
  • Agilix team member

We are working and looking into this.

0 Comment actions Permalink
Jeremy Walker

Thank you.

0 Comment actions Permalink
Brad Marshall
  • Agilix team member

The fix for this has been completed. We anticipate on it going live next Thursday.

0 Comment actions Permalink
Please sign in to leave a comment.