On Thu, Jan 29, 2009 at 3:29 PM, schoenborno
oliver.schoenb...@gmail.com wrote:
Hello, just in case others ever need the same:
We needed to dump the trac wiki to a folder as part of deliverable on
a project (together with a hotcopy of the trac environment itself,
etc).
FYI ... I had a
I actually wrote CombineWiki for _exactly_ this reason (turning in for class
milestones).
--Noah
-Original Message-
From: trac-users@googlegroups.com [mailto:trac-us...@googlegroups.com]
On Behalf Of schoenborno
Sent: Thursday, January 29, 2009 12:30 PM
To: Trac Users
Subject:
On Fri, Jan 30, 2009 at 2:02 PM, Noah Kantrowitz n...@coderanger.net wrote:
I actually wrote CombineWiki for _exactly_ this reason (turning in for class
milestones).
It still ...
«relies on htmldoc which on Windows is a pain to install.»
isn't it ? [1]_
.. [1] Combine Wiki Pages to a PDF
Sent: Friday, January 30, 2009 11:22 AM
To: trac-users@googlegroups.com
Subject: [Trac] Re: FYI: wget of whole wiki (tickets, reports, all)
On Fri, Jan 30, 2009 at 2:02 PM, Noah Kantrowitz n...@coderanger.net
wrote:
I actually wrote CombineWiki for _exactly_ this reason (turning
On Fri, Jan 30, 2009 at 2:23 PM, Noah Kantrowitz n...@coderanger.net wrote:
Just don't use the PDF output format. For making a static copy of the wiki,
the tiddlywiki output format is very handy since it maintains the inter-page
links.
:) ... for the starting use case this should be fine ;)
Thanks for the feedback. For a simple dump like we needed, I think
wget was easier, but if we needed more control, your solution is
interesting, I wasn't aware of the XML-RPC plugin. About TRAC_ADMIN
aspect: the complete dump required less than 5 minutes, that's how
long anonymous had TRAC_ADMIN
Thanks Noah for pointing that out, it's good to know. I saw the page
for that plugin, as well as the two other related pages (PageToPDF and
TracWikiToPDF) but unfortunately, none of them even hinted about the
HTMLdoc dependency being optional, or how you would setup the plugin
if you don't want
