teqnology / alfresco-pdf-toolkit

Automatically exported from code.google.com/p/alfresco-pdf-toolkit
Other
1 stars 0 forks source link

watermark formprocessor problem #17

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi,
after submitting the watermark form for a pdf file, i get from this post call:
http://localhost:8080/share/proxy/alfresco/api/action/pdf-watermark/formprocesso
r
the following response:
....
 "status" : 
  {
    "code" : 500,
    "name" : "Internal Error",
    "description" : "An error inside the HTTP server which prevented it from fulfilling the request."
  },  

  "message" : "org.alfresco.error.AlfrescoRuntimeException: 09150005 Invalid node ref - does not contain forward slash: ",  
  "exception" : "",
....
This error occurs on alfresco 4.0.0  win or linux

Original issue reported on code.google.com by albertob...@gmail.com on 15 Oct 2012 at 9:37

GoogleCodeExporter commented 9 years ago
Did you select a destination folder?  What was the watermark type (text or 
image).  If it was image, did you select an image to use?

Any relevant information from the log file would also be very helpful.

Original comment by nmcminn on 16 Oct 2012 at 12:42

GoogleCodeExporter commented 9 years ago

Original comment by nmcminn on 16 Oct 2012 at 12:43

GoogleCodeExporter commented 9 years ago
I just installed pdf-toolkit amps on alfresco community 4.2 but i have same 
issue: if i enter a text and select type: Text without select an image file i'm 
still getting the same error message. If i load an image and select type: Text 
then the new pdf file is watermarked correctly with entered text. 

Original comment by albertob...@gmail.com on 16 Oct 2012 at 8:55

GoogleCodeExporter commented 9 years ago
Yep, that's a bug.  I'll get a fix committed for release 1.1.

Original comment by nmcminn on 16 Oct 2012 at 9:40

GoogleCodeExporter commented 9 years ago
Thank you for your prompt reply!

Original comment by albertob...@gmail.com on 17 Oct 2012 at 7:28

GoogleCodeExporter commented 9 years ago
This issue is corrected with a new form processor in 1.1.1 beta 1 or newer.  

Original comment by nmcminn on 9 Apr 2013 at 8:29