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
Actual behaviour
The folder is not processed at all.
Expected behaviour
The folder should be processed and the images should be converted into a PDF and placed in the output folder.
Additional
I don't understand Java very well but it seems to me the issue was introduced by #1282. It looks to me as there is a filter that only looks at PDFs.
Version of Stirling-PDF
0.25.1 until latest
Last Working Version of Stirling-PDF
0.25.0
Page Where the Problem Occurred
No response
Docker Configuration
No response
Relevant Log Output
No response
Additional Information
No response
Browsers Affected
No response
No Duplicate of the Issue
I have verified that there are no existing issues raised related to my problem.
The text was updated successfully, but these errors were encountered:
* fix
* cleanups!
* fix
* fix for #1552 pipeline not accepting non pdfs
* fix for #1154 font not accepting numbers etc
* Update User.java
---------
Co-authored-by: a <a>
The Problem
When using the watched folder feature in combination with the img-to-pdf stage (with
.png
input files) the folder is not processed.Steps to reproduce
/pipeline/watchedFolders/reproduction
config.json
in the folder:Actual behaviour
The folder is not processed at all.
Expected behaviour
The folder should be processed and the images should be converted into a PDF and placed in the output folder.
Additional
I don't understand Java very well but it seems to me the issue was introduced by #1282. It looks to me as there is a filter that only looks at PDFs.
Version of Stirling-PDF
0.25.1 until latest
Last Working Version of Stirling-PDF
0.25.0
Page Where the Problem Occurred
No response
Docker Configuration
No response
Relevant Log Output
No response
Additional Information
No response
Browsers Affected
No response
No Duplicate of the Issue
The text was updated successfully, but these errors were encountered: