Leap2a export results in error message display

Bug #1850737 reported by Rangi Daymond on 2019-10-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Status tracked in 20.04
Lisa Seeto

Bug Description

- Code/Gerrit: latest 19.10 master ***this bug also present in 19.04_STABLE
- Browsers tested: Firefox & Chrome
- Theme: Firefox=Modern & Chrome=Primary School


1. Site is not running in production mode ( config.php file has the following line $cfg->productionmode = false; ).
2. Attached content page (here as Leap2A) is present.
Note: The error #2 is displayed when importing the file. If you set up content from scratch, set up 2 journal entries with tags and add the tagged journal entries block to the page. It is not yet clear whether error #1 is related to this or not.
3. Site is not set to export to queue.

Test steps:

1. PersonA is logged in and selects Main menu -> Manage -> Export -->Leap2a format and All (or just select the target page).
2. The export is generated.
Expected result: The export file can be downloaded.
Actual result: The export file can be downloaded but a debug message is displayed saying: "Not providing an export-relative link for [artefact number]" (see attached screenshot "Export error messages displayed")

3. Log in as PersonB and import the attached Leap2A file (or your own) via Main menu -> Manage -> Import.
4. Display the page.
Expected result: The tagged journal entries block displays the journal entries that were tagged.
Actual result: "Error during block configuration" is displayed (see screenshot "Imported page displayed with block error message")

Rangi Daymond (rangid) wrote :
Rangi Daymond (rangid) wrote :
Rangi Daymond (rangid) on 2019-10-31
description: updated

The "export-relative link" may be unrelated to the error seen in tagged journal entries. Since lots of blocks are on the page that wasn't quite clear.

description: updated

The tagged journal entries issue is in bug #1855349. This bug here is for the "export-relative link" problem.

Lisa Seeto (lisaseeto) wrote :

After some investigation, it was discovered that artefact 5287 from the debug message refers to an image in the export. The image was in several places in the export but appeared in a Text Block titled "Text Only Block" on page "AAA Mixed Block Page: Move "Add comment" and "Details" into modal with "Comments" " in an attempt at an embedded image. The resulting image was a broken link though it isn't clear what part of it should be producing an error as creating a similar link with the same image (though a different src) produces a correct image. The text block displayed with the alt text of the image when the page was displayed. I found that I couldn't see the debug message no matter what steps I followed though Rangi could. She exported the page and saw the debug message. She then edited the Text block to have a working embedded image and exported the page again and this time didn't see any warnings but got the successful export outcome.

Let's not investigate this further as it seems to have been a rogue element.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers