You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My apologies, I'm the guilty here, but I noticed a bug when using the collection extension and pdfsam: the render simply crashes.
The problem is that the executed command is something like:
pdfsam-console -f /path/tmp.rl -f toc.pdf -o final.pdf -overwrite
BUT pdfsam does not recognise .rl as a pdf format (which is quite understandable) AND does not return an error so mwlib.rl "thinks" it worked, which is false and final.pdf does not exist, which causes an error afterwards.
I do not understand why when I run mw-render the temporary file is named with the right extension and when the server is used the extension is .rl
Is this really useful ? or could it be replaced by .pdf ?
The text was updated successfully, but these errors were encountered:
After a bit of research it seams that the Collection extension actually asks for a .rl file (quite odd) therefore the problem comes from Collection. Mwlib does exactly what it's been asked to :)
Note: Maybe we should move this thread to collection extension's issues, but I don't know how. Sorry.
My apologies, I'm the guilty here, but I noticed a bug when using the collection extension and pdfsam: the render simply crashes.
The problem is that the executed command is something like:
pdfsam-console -f /path/tmp.rl -f toc.pdf -o final.pdf -overwrite
BUT pdfsam does not recognise .rl as a pdf format (which is quite understandable) AND does not return an error so mwlib.rl "thinks" it worked, which is false and final.pdf does not exist, which causes an error afterwards.
I do not understand why when I run mw-render the temporary file is named with the right extension and when the server is used the extension is .rl
Is this really useful ? or could it be replaced by .pdf ?
The text was updated successfully, but these errors were encountered: