So this seems like part of the intersection between the conversations on
improving the Preview Processor and the conversation on making sakaidocs
indexable by google (and/or other) bots.

= nate

On Tue, Aug 7, 2012 at 2:07 PM, Erik Froese <erik.fro...@gmail.com> wrote:

> Hey everyone,
>
> I'm hoping the folks who did the implementation for previewing sakai
> documents with wkhtmltopdf can help me out here.
>
> I'm seeing a few issues getting sakai doc previews to work in
> 1.5.0-SNAPSHOT.
>
> 1. Sakai documents are never marked sakai:needsprocessing = true.
> This isn't a huge deal as I can mark them by hand for testing.
>
> 2. The ruby PP expects the wkhtmltopdf binary to be in the nakamura
> tree. This is extra work for deployers.
> The Java PP searches the PATH environment variable for wkhtmltopdf and
> disables sakai doc processing if it can't find it.
>
> 3. The ruby PP only works with wkhtmltopdf version 0.9.9. I can't get
> anything but the static build of 0.9.9 to work.
> Is there any plan to move to a more recent version? Has anyone tried?
>
> 4. Once the PDF is generated the new PDF is posted to
> http://192.168.1.6:8080/p/CONTENT_ID/CONTENT_ID.processed.pdf
> I don't see that as being marked for processing either. What's the
> expected path to get this processed into thumbnails?
> Do those thumbnails get attached to the content item like the other items?
>
> Erik
> _______________________________________________
> oae-dev mailing list
> oae-dev@collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>
_______________________________________________
oae-dev mailing list
oae-dev@collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/oae-dev

Reply via email to