Project

General

Profile

Actions

Feature #273

closed

Install Collection extension for MW

Added by scott voth over 14 years ago. Updated over 9 years ago.

Status:
Deferred
Priority name:
Normal
Assignee:
-
Category name:
Wiki
Target version:
-
Start date:
2010-07-19
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

Once the new Wiki upgrade is in place, please install two new extensions: Collection and PDF_Book. (Hopefully they won't conflict with the other extensions we've got.) Here are the links: http://www.mediawiki.org/wiki/Extension:Collection ; and http://www.mediawiki.org/wiki/Extension:PdfBook

Thanks!


Related issues

Related to CUNY Academic Commons - Feature #276: Install PDF_Book extension for MediaWikiResolvedBoone Gorges2010-07-21

Actions
Actions #1

Updated by Matt Gold over 14 years ago

  • Status changed from New to Assigned
  • Assignee set to CIC Michael
Actions #2

Updated by Matt Gold over 14 years ago

Since it will require some additional set-up work, we're going to put PDF_Book on the slate for the next version of the Commons.

Actions #3

Updated by Boone Gorges over 14 years ago

  • Target version changed from 1.0.1 to 1.0
Actions #4

Updated by Boone Gorges over 14 years ago

  • Target version changed from 1.0 to 1.1
Actions #5

Updated by Boone Gorges about 14 years ago

  • Subject changed from Wiki extension installs to Install Collection extension for MW
Actions #6

Updated by Boone Gorges about 14 years ago

  • Status changed from Assigned to Resolved

I've enabled Collection on cdev in https://github.com/castiron/cac/commit/47c487119cb2473b9f764eff2b3e4b148084e227

Everything seems to be working right, except for the part where you try to render a page or a book as PDF. The extension appears to want to send the items to an external rendering server, but because cdev is behind a password wall (and my localhost is not accessible from the internet) I kept coming up with errors. I'm assuming that these will be fixed once we're on the live server; this is something I'll check during the 1.1. upgrade routine https://github.com/castiron/cac/wiki/WordPress-3.0-upgrade-process-and-Actions-Required

I'll mark the ticket as fixed for the moment, under the assumption that the extension will work when we go live. If it does not, I'll revisit the ticket and assign it a new milestone.

Actions #7

Updated by Matt Gold about 14 years ago

If possible, can you test this on a non-password-protected MW install so that we can learn more about the external rendering server process? Or would the differences in server environments detract from the utility of the test?

Actions #8

Updated by Boone Gorges almost 14 years ago

  • Status changed from Resolved to Assigned
  • Target version changed from 1.1 to 1.1.1

It didn't work on the live site so I disabled it https://github.com/castiron/cac/commit/000823aae98feabc78e03093484e730cc93c548f

Export process needs debugging

Actions #9

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.

Actions #10

Updated by Boone Gorges almost 14 years ago

  • Target version changed from 1.1.2 to 1.1.3
Actions #11

Updated by Boone Gorges almost 14 years ago

  • Target version changed from 1.1.3 to 1.1.4
Actions #12

Updated by Boone Gorges almost 14 years ago

  • Target version changed from 1.1.4 to 1.1.5
Actions #13

Updated by Boone Gorges almost 14 years ago

  • Target version changed from 1.1.5 to 1.1.6
Actions #14

Updated by Boone Gorges almost 14 years ago

  • Target version changed from 1.1.6 to 1.1.7
Actions #15

Updated by Boone Gorges almost 14 years ago

  • Target version changed from 1.1.7 to 1.1.8
Actions #16

Updated by Boone Gorges almost 14 years ago

  • Target version changed from 1.1.8 to Future release

I've just spent some time looking deeper into the extension. It requires an external rendering server (as I mention above). There is a publicly available rendering server, but it does not appear to work. It might be possible for us to set something up for our own use, but I'm thinking that at the moment we'll have to put it on the back burner. Bumping to future release.

Actions #17

Updated by Boone Gorges over 9 years ago

  • Status changed from Assigned to Deferred
  • Assignee deleted (CIC Michael)
  • Target version deleted (Future release)
Actions

Also available in: Atom PDF