Merge from original repository #2
Open
Conversation
This file contains hidden or 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
development
branch
from
1b71705 to
de70f1e
Compare
NamelessCoder
force-pushed
the
development
branch
from
379ca34 to
35d4b47
Compare
NamelessCoder
force-pushed
the
development
branch
from
88236e3 to
3d45411
Compare
NamelessCoder
force-pushed
the
development
branch
from
b115805 to
f64cde9
Compare
NamelessCoder
force-pushed
the
development
branch
from
703e5ab to
546c966
Compare
Warnings may trigger if the current BE user does not have access to the language column of a record being moved. When this happens, Flux will now attempt to read the language UID from the record as stored in DB, or will default to the default language UID of zero.
#2144) Co-authored-by: Claus Due <[email protected]>
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.
Co-authored-by: Claus Due <[email protected]>
We can ignore a missing database connection at this point. We cant do anything about a missing database connection. This Scenario is possible during first install.
Co-authored-by: Claus Due <[email protected]>
…ge templates Some change in TYPO3v12's Fluid dep has caused the TemplateParser to hold on to invalid states of parsed templates. Likely has to do with the many hoop-jumps the Fluid team has had to do since declaring that shared ViewHelper instances is a totally valid use case. I'm getting really tired of TYPO3's decisions as of late.
Adds ability to avoid the fallback lookup to the TYPO3_REQUEST global.
Fixes mainly a problem with Flux in an INT uncached context where the resolved request and therefore content object data was not the expected one (returned page row from inside a content context). This fixes that problem by more consistently handing over the request to the lookup methods and using the content object data when it is availble in the content object.
"description" has been supported in <flux:field> already, but not for the single field types. This patch adds support for the attribute in e.g. <flux:field.input> Related: #1891
Co-authored-by: Luc MULLER <[email protected]> Co-authored-by: Claus Due <[email protected]>
Fixes flux:form.option with tag content on older TYPO3 versions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
15 participants
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.
Hi @monosize
Is it possible to merge the current development branch from FluidTYPO3 into your fork? I would like to test it in a current Typo3v8.7 instance.