Merge from original repository#2
Open
Kleisli wants to merge 1239 commits intomonosize:localizationfrom
Open
Conversation
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
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 <claus@namelesscoder.net>
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 <claus@namelesscoder.net>
…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 an extension configuration option and corresponding Form option and option ViewHelper which allows a site to control how Flux handles inheritance of FlexForm values (specific to pages). Normally, Flux will only allow FlexForm values to be inherited from a parent page to children if the child uses the same page layout (template) as the parent page(s). This new option allows changing this inheritance mode from the default "restricted" to an "unrestricted" mode which allows FlexForm values to be inherited even if the child and parent uses different page layouts. This is useful when you have different page templates which use the same FlexForm fields (for example, a shared set of fields) and you wish to inherit such fields from parents even if you use different page layouts on the child/parent(s). There is a similar Form option which allows setting this inheritance mode on a per-template basis. Use the new ViewHelper flux:form.option.inheritanceMode for this, with either "restricted" or "unrestricted" as value. If no mode is specified on a template then the inheritance mode defined in extension configuration will be used.
And it causes breaking changes in minor revisions. Often.
Allows implementers to specify their own form data transformation routines through a proper API.
…2166) Co-authored-by: Denis Ivanov <denisivanov@o-s-i.org> Co-authored-by: Claus Due <claus@namelesscoder.net>
FileRepository is broken in BE context for FlexForm-based relations. Refs: #2139 Refs: https://forge.typo3.org/issues/104331
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 <l.muller@ameos.com> Co-authored-by: Claus Due <claus@namelesscoder.net>
Fixes flux:form.option with tag content on older TYPO3 versions.
Prevents issues with attempts to read FlexForm data structures in contexts that don't carry a ServerRequest, e.g. CLI context. Falls back to an empty array.
Adds a case that catches a defined but incompatibly-typed `colPos` value in a record when trying to read parent column positions. Some cases will pass an empty string to the function, but the current guard clause only checks if the value is undefined. So a check is added to early return in case the `colPos` value equates to an empty string. Close: #2277
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
14 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.