OER in Education:TODO

Higher level EWTE/issues remaining.

Wiki Issues

Task	Description	Priority	Assignment
Overall, the wiki is still slow		High
Gateway timeouts	E.g. upload two files at the same time, 1 and 2, gives a gatway timeout. Script for load testing added here: OER:TODO/Gateway	High
Rename print options in sidebar menu "Print"	Given that OCG is working poorly, could we change the order of the links, and the text for pdf link? E.g. add experimental after pdf? Print/export Create a book Download ready-made PDF Download ZIM Printable version Download as PDF (experimental) Download as Plain text Then On the "Rendering" page for PDF, after the sentence: "This page should automatically refresh every few seconds. If this does not work, please press your browser's refresh button." could we add (in big writing): "Note that PDF export is highly experimental, and for many pages may not give usable output." "Download ready-made pdf" should point to a page OER:PDF where we explain the situation, and link to a ready-made PDF. The "Download ZIM" should link e.g. to OER:ZIM, where we explain, and link to the ZIM.	High
(ZIM/Parsoid) In the ZIM and for parsoid: Section numbers (with page, e.g. 1.2.3, 1.2.4, etc.) are not preserved...	Example: [1]	High
(ZIM/Parsoid) Appearance of SMW::off... in paroid output		High
Adjust css for visual editor	Font needs to be a bit bigger, increase line spacing
Parsoid output shows numerical IP address	E.g. http://oer.educ.cam.ac.uk:8000/oer/OERGS%2FG1, shows numerical IP address.	Low
For User:Bjoern Special:Preferences has a different skin from the main namespace	I can not reproduce that problem Kelson (talk) 14:18, 26 February 2015 (CET)	Low
In the ZIM, the semantic markup for lesson objective and success critieria is visible, i.e. [[intent: .... ]] shows.	Marked as low, because we can work around this with css. (Has been fixed with work-around.)	Low

Solved

printonly class

Why does this not work? User:Bjoern/noprint, MediaWiki:Vector.css. Solution: See MediaWiki:Vector.css, MediaWiki:Print.css, and (waiting for ZIM integration) MediaWiki:Offline.css

Done

See also https://sourceforge.net/p/kiwix/feature-requests/883/

Collection of issues

Parsoid

Paroid output does have blue background

This is something to tweak with the CSS, not a parsoid issue. Kelson (talk) 23:40, 30 March 2015 (CEST)

Bugs for ZIM

reported

• Removal of "SMW::on/off". (see e.g. [2]). They need to be removed. Parsoid produces links like this:
  • <a rel="mw:WikiLink" href="./SMW::off" title="SMW::off" data-parsoid="{"stx":"simple","a":{"href":"./SMW::off"},"sa":{"href":"SMW::off"}}">SMW::off</a>
  • <a rel="mw:WikiLink" href="./SMW::on" title="SMW::on" data-parsoid="{"stx":"simple","a":{"href":"./SMW::on"},"sa":{"href":"SMW::on"}}">SMW::on</a>
  • This is a Parsoid problem which is reported here

Handling of direct links to files in ZIM

We need to think about how to make external resources accessible, such as

• PDF files / word / ppt linked from sessions (and normally stored within the wiki) (might also apply to images, where the full resolution image would be useful to have)
• Videos (that are presently stored outside the wiki)
  • (1) Migrating video to Mediawiki (2) Support of multimedia by Parsoid.

We need an example here. Kelson (talk) 13:25, 4 April 2015 (CEST)

Bugs reported

Zim reader on OS X has no keyboard shortcuts for forward/back.	https://sourceforge.net/p/kiwix/bugs/822/ - shortcuts are cmd-left, cmd-right
Parsoid output does not deal with arrays defined in templates.	Example: User:Bjoern/arrayinclusion . From https://phabricator.wikimedia.org/T87157: Parsoid doesn't support stateful extensions / parser functions at this time. In this case, it looks like your extension relies on state that has been setup earlier in the page. Parsoid calls into the mediawiki API to expand parser functions and templates, and there is no page state available at that time. That is why the #arrayprint call inside the template works as expected (because PHP parser sees the array setup and that state is accessible to the following #arrayprint function). But, the second #arrayprint in the page doesn't have access to page state since it is a fresh call into the API. The existing stateful extensions (like Cite) are supported by having native implementations inside Parsoid (as special cases that are used very widely). LST is another one that will be implemented. We do have plans for native Parsoid extensions and being able to register them. But, we haven't implemented that yet. A possible work around in our case is to re-call the array in the main body of the page, which then makes it available.	https://phabricator.wikimedia.org/T87157