Feature #276
closedInstall PDF_Book extension for MediaWiki
0%
Description
We're targeting this for the next version of the Commons. Please see Michael's notes on Basecamp, which detail necessary Python libraries that need to be installed on production and development environments to enable this extension.
Extension homepage: http://www.mediawiki.org/wiki/Extension:PdfBook
Related issues
Updated by local admin over 14 years ago
The only server-side requirement listed on the relevant mediawiki page is a package called HTMLDOC.
I went ahead and installed that from the RHEL repos. Just let me know if it doesn't work as expected for any reason.
Updated by Boone Gorges almost 14 years ago
- Status changed from Assigned to Resolved
- Assignee changed from CIC Michael to Boone Gorges
The extension is added in https://github.com/castiron/cac/commit/6422a130a043d2936bf870afe330e7a034975c3a
In https://github.com/castiron/cac/commit/c3dc8262811a499d7a51f050ce8bb90c64d59684 I add a small extension that I wrote to put a PDF link in the Views menu. This extension can be used for other kinds of menu manipulation in the future.
Updated by Boone Gorges almost 14 years ago
- Status changed from Resolved to Assigned
- Target version changed from 1.1 to 1.1.1
In the 1.1 upgrade I disabled both the PDFBook extension and the associated custom menu item, as the PDFs they were outputting were broken. PDFs seemed to work on cdev, so I'm a bit confused.
Updated by Boone Gorges almost 14 years ago
- Target version changed from 1.1.1 to 1.1.2
1.1.1 will only fix critical issues so I'm bumping this to 1.1.2.
Updated by Boone Gorges almost 14 years ago
- Target version changed from 1.1.2 to 1.1.3
Updated by Boone Gorges almost 14 years ago
- Target version changed from 1.1.3 to 1.1.4
Updated by Boone Gorges almost 14 years ago
- Target version changed from 1.1.4 to 1.1.5
Updated by Boone Gorges almost 14 years ago
- Status changed from Assigned to Resolved
On a lark, I reactivated the extension on the live site, and now it seems to be working great. I'm going to leave the ticket under the 1.1.5 target version, but it is actually fixed right now.