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

Check and Remove ext_typoscript_setup.txt #67

Closed
albig opened this issue Jan 18, 2018 · 3 comments
Closed

Check and Remove ext_typoscript_setup.txt #67

albig opened this issue Jan 18, 2018 · 3 comments
Assignees

Comments

@albig
Copy link

albig commented Jan 18, 2018

IMHO the file ext_typoscript_setup.txt can be removed safely.

The only setting, which is not default is config.tx_extbase.persistence.updateReferenceIndex = 0. But this shouldn't hurt.

updateReferenceIndex = 0

@claussni
Copy link
Member

claussni commented Jan 23, 2018

What is/was the purpose of this file? It is not used anywhere in the source code. Is it some extension template leftover?

@claussni claussni self-assigned this Feb 28, 2018
@albig
Copy link
Author

albig commented Mar 1, 2018

I noticed now the setting config.tx_extbase.persistence.updateReferenceIndex is false by default. So no setting in this file changes anything. We can delete it safely.

Internally, TYPO3 manages an index of all relationships between two datasets the so-called RefIndex. Due to this index it's possible to show the number of associated datasets in the list module's column [Ref.]. By clicking on the number you get further informations about the incoming and outgoing references of the dataset. This index is automatically updated when any datasets get edited. The configuration config.tx_extbase.persistence.updateReferenceIndex = 1 effects an update when datasets get edited in the Frontend though it is normally deactivated due to its huge effects on performance.
https://docs.typo3.org/typo3cms/ExtbaseFluidBook/6-Persistence/2-configure-the-backends-inputforms.html

@claussni
Copy link
Member

claussni commented Mar 2, 2018

Resolved in #82

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

No branches or pull requests

2 participants