Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add extension setting "childElementsEnabledOnCopy" #446

Closed
wants to merge 1 commit into from
Closed

Add extension setting "childElementsEnabledOnCopy" #446

wants to merge 1 commit into from

Conversation

pascalwittler
Copy link

If the option is set, child elements of containers are not hidden after copying or locating.

This is another proposal for #400 and adds basically the same modification as #401 but the new behavior is optional and takes effect only after a new setting has been deliberately set.

If the option is set, child elements of containers
are not hidden after copying or locating.
@achimfritz
Copy link
Contributor

i think we should not introduce an extension configuration for this case, why can we not use the value of the "original" DataHandler (passed to the Methods)?, like:

$localDataHandler->neverHideAtCopy = $dataHandler->neverHideAtCopy

@achimfritz
Copy link
Contributor

ah, now i understand, but this do not change my opinion about the extension-configuration

@pascalwittler
Copy link
Author

Thanks for your quick reply! I agree with you that an additional setting which is only valid for one extension is not the best solution. It would be nicer to have a global setting in TYPO3 that applies to all elements and all extensions.

The reason for my suggestion to introduce an extension configuration setting here is simply that I don't know of such an option that can be set for the user in the backend and that is available in this context. But I would be happy to be corrected by anyone!

@achimfritz
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants