mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #14848
[Bug 984575] Re: Leap2A importer: improve robustness of <content> importing
According to the documentation here:
http://www.leapspecs.org/2A/literals#content_or_description
We should not be trying to import <content></content> as HTML (all
escaped) but rather as XHTML (not escaped)
eg, instead of this:
<content type="html"><p>&nbsp;</p> <p>a paragraph</p> <p>&nbsp;</p></content>
it should be more like this:
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">
<p> </p> <p>a paragrapgh</p> <p> </p>
</div>
</content>
where the containing <div> gets stripped on import
So on import should we take the contents of <content type="html">
unescape it, then run it thru html tidy and import it as xhtml?
--
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/984575
Title:
Leap2A importer: improve robustness of <content> importing
Status in Mahara ePortfolio:
In Progress
Bug description:
In import/leap/lib.php, function fix_artefact_reference.
If a <content> tag in a Leap2A import has more than one child node,
the importer gets confused and only imports one of them (either the
first or the last, not sure which).
E.g.:
<content type="html"><p>&nbsp;</p> <p>a
paragraph</p> <p>&nbsp;</p></content>
This is:
<content>
<p>
<p>
<p>
Which isn't handled properly. I think the leap2A spec mentions that
content like this is not a good idea, but the fix seems pretty easy.
Patch attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/984575/+subscriptions
References