[BUGFIX] Fix handling of drop-in templates #2155
Merged
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
NamelessCoder
force-pushed
the
feature/fix-dropin-loading
branch
from
0b46939
to
10035da
Compare
Fixes a combined issue where template file paths would be wrong in BE context and the pi_flexform field would not be shown in record editing, for templates placed in the plug-and-play / drop-in directory.
NamelessCoder
force-pushed
the
feature/fix-dropin-loading
branch
from
10035da
to
1d99b7e
Compare
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.
Fixes a combined issue where template file paths would be wrong in BE context and the pi_flexform field would not be shown in record editing, for templates placed in the plug-and-play / drop-in directory.