`sendaspdf` depends on `pyproxy`, but doesn't install it in Plone about collective.sendaspdf HOT 5 CLOSED

Heh! I'm using sendaspdf from a Plomino action, and deleting the portal_actions/document_actions/.
It turns out that if I install jquery.pyproxy, my usage breaks.
So it's pure luck that I ended up with a configuration that worked for me from the outset (i.e. with sendaspdf, without pyproxy).

from collective.sendaspdf.

The original idea was to be able to use sendaspdf without jquery.pyproxy (for example for one customer we used sendaspdf as a PDF generator, without the links to send a page). pyproxy was added during install to avoid import issues.
At least, that was the idea on creation, Maurit would know better now ;)

from collective.sendaspdf.

It sounds like my use case is similar to the one you mention. I'll see if I can clarify this usage in the docs.
Thanks!

from collective.sendaspdf.

Should i be included in this mail conversation? I think i am not the maurits you think i am. :)

Groet,
Maurits

On Dec 20, 2013, at 16:28, Jean Jordaan [email protected] wrote:

It sounds like my use case is similar to the one you mention. I'll see if I can clarify this usage in the docs.
Thanks!

—
Reply to this email directly or view it on GitHub.

from collective.sendaspdf.

No, the correct Maurits is mauritsvanrees.
I don't know how you got notified .. I don't see any @ notification or even the name Maurits written out in full above.

from collective.sendaspdf.