Added support for importing link #51
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The parserParams can be used by the FPDI PDF-Parser to handle encrypted files (more to this here: https://manuals.setasign.com/fpdi-pdf-parser-manual/v2/protected-pdf-documents/).
|
@Webklex Can you check this pr? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since FPDI 2.4.0 it's supported to import external links but it has to be activated by a parameter. This PR sets this parameter to true by default as I don't see any reason to not import the links - alternatively I can also make this configurable per pdf (if you wish).
Additionally I added support for the new parserParams - at the end this is currently only be used by the FPDI PDF-Parser to handle encrypted pdfs. More about this can be found here.