mahara-contributors team mailing list archive

[Aaron Wells <1605071@xxxxxxxxxxxxxxxxxx>]

Patch for master: https://reviews.mahara.org/#/c/6055/

This patch adds the "JSON" flag to blocktype.ajax.php, so that
errors.php will print a JSON-encoded error response instead of trying to
render the normal "Site unavailable" error page.

This isn't the cleanest option, but it's an improvement over the current
state of affairs. It makes it clear to the user that something is wrong
with that block, and it doesn't mess up the display of other blocks.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1605071

Title:
  Display something more error-like when an AJAX block errors out

Status in Mahara:
  In Progress

Bug description:
  Spinning this bug off from Bug 1544424 (Endless JS loop if there's an
  uncaught exception in an ajax block) since patch
  https://reviews.mahara.org/6055 has taken much longer than
  https://reviews.mahara.org/6054 to get merged.

  We no longer get an endless loop when an Ajax block errors out, but it
  still looks pretty bad. See the attached screenshot. Because the file
  "blocktype.ajax.php" doesn't have the "JSON" header at its top, when
  it errors out, Mahara tries to print the full error page with the
  navigation headers and the message "Mahara: Site unavailable", and
  then ajaxblocks.js tries to display it in the little iframe reserved
  for that block.

  This looks confusing to the user, and it can spill over out of that
  block's space and cover up adjacent blocks. It would be better if we
  printed something that more obviously indicates that just this one
  block is broken, and that doesn't break the display of other blocks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1605071/+subscriptions