Agilix Backpack

There is a way to link content to the Blackboard server that causes the download from Blackboard to Backpack to fail. This method is called Xythos, which uses link ids called xlinks. This method probably allows the content to be linked and utilized in a more efficient manner by the server, overall. However, this new method does not work with Backpack, so if the school changes to this linking method then instead of seeing the content in Backpack you will see errors like this:

………………………………………………………………………………..

Document Not Downloaded (Error)

Start (59.4 KB) was not downloaded because of the following server error: Moved Temporarily (Found)

To try to download it again now, click the “Download Now” button below.

………………………………………………………………………………..

Unfortunately, when you click the Download Now button you simply end up in a cycle. The content never shows up.

You can tell if your school is using Xythos by looking at the links to content. If they use Xythos the links will and in xlink ids (something like “xlink_id=XXXX”).

The only solution to this problem at the moment is for the school not to use the new linking method.

Some of you may find when working in discussion boards that Backpack appears to lose the “read” status for previously read discussion board posts. Unfortunately, this is caused by a bug on some Blackboard servers. Some versions of Blackboard server ignore the read/unread status sent by Backpack.

I’m afraid there is not much you can do about this. Agilix has reported the problem to Blackboard, Inc., but it has not yet been resolved.

This is what happens (this all happens within 1-2 seconds):

1. You read a post in Backpack; Backpack marks it as “read”
2. When you sync with your Blackboard account, Backpack sends the “read” status to the server
3. The server accepts the status without returning an error to Backpack
4. The server then drops the status for some unknown reason (so it retains its “unread” status for the post)
5. Backpack immediately attempts to re-sync with the server, requesting updates for all statuses
6. The server sends the “unread” status back to Backpack (because it ignored the “read” status)
7. Backpack changes its “read” status back to “unread” because that is what the server told it to do

There is no fix and no work around for this bug. Backpack will always sync to match what the server shows. So, for instance, if you were to go online to read the posts, they would change to “read” online. Then, when you sync Backpack with the server again, the status will change from “unread” to “read” in Backpack to match the server.

Trust me – Agilix knows how frustrating this bug is. It is frustrating to them, too! Unfortunately, the fix must be made on the server side by Blackboard, Inc.