I have a similar issue that has been highighted on this thread, but mine is not because of a rotated page.
I have a route that needs to recognise whether the PDF is 230mm x 317mm by crop box. The attached PDF however has a media box that contains the crops ( I think generated by Adobe Illustrator) that is bigger than the crop box, and I THINK thi is causing problems.
Bearing in mind any fixes I do to this PDF will also have to be done to all the other pdfs that I am sending through to this workflow, which unfortunaely is a replica of one I have "converted" from Process Manager. Because we are replacing PM with FFCore I need to keep the logic more or less the same and I am dealing with hundreds of existing legacy PDFs that will have this same issue!
Does anybody have any ideas how I can get FFCore to recognise that the crop box is 230x317 and therefore route correctly?
I have tried the following unsuccessfully by creating kfpx's in Callas and importing into Freeflow:
• setting media box to crop box = does not work
• derive the geometry boxes from the crops if missing > remove objects outside of the trim that are registration in colour > setting media box to crop box = The problem I have with this method is that all files I send to the workflow will be effected.
Hoping somoene with superior knowledge to me on the constructs of this PDF and how FF reads it can help, Process Manager read it fine by just looking at the crop box size, but FF goes a lot a deeper I think and is more "fussy" (rightly so) about the pdf's structure.
Thanks for your help
I was not able to upload the PDF? Not sure how anyone can help if I cannot attach the problematic PDF..am I missing something on how to attach to the post?!
No problem. Here is a screen snap of what I see. The "attachments" at the bottom should be visible on your browser.
I have tried 3 different browsers, each one does not show that window. However when trying my second browser it did show and I chose a file, it then threw an error "Access denied/premission type error" I unfortunately did not get a screen shot.
Now whenever I hit reply I do not see the file upload section on any browser I have tried....Chrome, Safari, Firefox on MAC OSX. Very frustrating!
I thought it might be a browser issue but now think not? I am not sure what to do next to be able to upload a file to this Post!
Thanks for your help
So after trying EDGE, same result ...no file upload window available. I go back to chrome and lo and behold the file upload window appears, I chose a file from my desktop and then I get the above error, I have full access rights to the file this end. When logging back in and clicking reply, the File upload windows does not appear. This is flaky and is not browser specifc.
We are a Mac based company so unfortunately we do not run Windows10 Clients here as a default therefore Edge is not available to me in th normal run of things. I do have 1 x VM using it and have tested it and as mentioned the file upload does not appear.
Can we escalate this to Xerox? How do we push this to the forum sys admin team?
Thanks for your patience.
Ok Turns out only admin users can upload PDFs!
Anyway here is an update to where I am with this issue, which is now growing.
My initial idea/solution for the specific PDF which has a media box not equal to crop box was to do a check and on error, route that way. That would be fine however, some of the other PDFS I am testing do not have crop boxes. I am fast understanding that doing anything with crop boxes is a bad idea, the problem being that we have so many legacy PDFs that are malformed!
So...Screen shot here of the check I have made in FF.
This worked OK for the problematic PDF and I built this test workflow to fix the issues with the PDF.
The above is lacking adding the correct trims back in, which I THINK could possibly be done like so..
But for a PDF that has NO Crop box, it also errors and goes down the route of being fixed, this is the resulting preflight parts that indicates there is no crop box:
<page id="PAG1" nr="1" mediabox="0.0/0.0/907.087/1275.59">
I will continue to work on this, but now looks like I will have to build a preflight check in Callas First.?....to see if there is a crop box and if there is NOT, route accordingly.
To put this into context here is a screen shot of the main workflow I am trying to work with and the problematic route highlighted...maybe I may need to re think the whole thing? I dont want to because as mentioned before I am transferring Process Manager to FFCore here and am dealing with legacy/old ideas and methods and old PDFs.
If anyone can assist or have any ideas on how best to deal with these I would be most grateful.