Ghost field in Templavoilà
up vote
0
down vote
favorite
I'm using this bit of Typoscript to generate some text.
field_test is created via TemplavoilàPlus.
# If field_test is filled in by the redactor,
# its content will be displayed in the frontend.
10 = TEXT
10.if.isTrue.field = field_test
10.value.field = field_test
I'm using several FCE from TV+ and I have many more fields handled via Typoscript. For some FCE, I didn't set field_test in TV+ and thus, it is not displayed in the frontend at all since the redactor can't fill it in in the backend. This is the normal behaviour.
However, for one the FCE, field_test is displayed anyway. This field is not set in TV+ and I can't find it in the XML. It is not displayed in the backend and then can't be filled in.
But it has existed at some point, and has been filled before it was removed from the TV+ FCE.
Now I have its ghost displayed in the frontend. How can I find it and delete it for good?
typo3 typoscript typo3-7.6.x templavoila
asked Nov 19 at 11:01
CCR
45115
add a comment |
up vote
0
down vote
favorite
I'm using this bit of Typoscript to generate some text.
field_test is created via TemplavoilàPlus.
# If field_test is filled in by the redactor,
# its content will be displayed in the frontend.
10 = TEXT
10.if.isTrue.field = field_test
10.value.field = field_test
I'm using several FCE from TV+ and I have many more fields handled via Typoscript. For some FCE, I didn't set field_test in TV+ and thus, it is not displayed in the frontend at all since the redactor can't fill it in in the backend. This is the normal behaviour.
However, for one the FCE, field_test is displayed anyway. This field is not set in TV+ and I can't find it in the XML. It is not displayed in the backend and then can't be filled in.
But it has existed at some point, and has been filled before it was removed from the TV+ FCE.
Now I have its ghost displayed in the frontend. How can I find it and delete it for good?
typo3 typoscript typo3-7.6.x templavoila
asked Nov 19 at 11:01
CCR
45115
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm using this bit of Typoscript to generate some text.
field_test is created via TemplavoilàPlus.
# If field_test is filled in by the redactor,
# its content will be displayed in the frontend.
10 = TEXT
10.if.isTrue.field = field_test
10.value.field = field_test
I'm using several FCE from TV+ and I have many more fields handled via Typoscript. For some FCE, I didn't set field_test in TV+ and thus, it is not displayed in the frontend at all since the redactor can't fill it in in the backend. This is the normal behaviour.
However, for one the FCE, field_test is displayed anyway. This field is not set in TV+ and I can't find it in the XML. It is not displayed in the backend and then can't be filled in.
But it has existed at some point, and has been filled before it was removed from the TV+ FCE.
Now I have its ghost displayed in the frontend. How can I find it and delete it for good?
typo3 typoscript typo3-7.6.x templavoila
asked Nov 19 at 11:01
CCR
45115
I'm using this bit of Typoscript to generate some text.
field_test is created via TemplavoilàPlus.
# If field_test is filled in by the redactor,
# its content will be displayed in the frontend.
10 = TEXT
10.if.isTrue.field = field_test
10.value.field = field_test
I'm using several FCE from TV+ and I have many more fields handled via Typoscript. For some FCE, I didn't set field_test in TV+ and thus, it is not displayed in the frontend at all since the redactor can't fill it in in the backend. This is the normal behaviour.
However, for one the FCE, field_test is displayed anyway. This field is not set in TV+ and I can't find it in the XML. It is not displayed in the backend and then can't be filled in.
But it has existed at some point, and has been filled before it was removed from the TV+ FCE.
Now I have its ghost displayed in the frontend. How can I find it and delete it for good?
typo3 typoscript typo3-7.6.x templavoila
typo3 typoscript typo3-7.6.x templavoila
asked Nov 19 at 11:01
CCR
45115
asked Nov 19 at 11:01
CCR
45115
asked Nov 19 at 11:01
CCR
45115
asked Nov 19 at 11:01
CCR
45115
asked Nov 19 at 11:01
CCR
45115
45115
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
you need to identify those CEs which have set field_test and where this field should be empty.
You could edit every CE, change it's type to a type where the field id visible, check for empty and change type back to origin.
or you do some immediate SQL queries in a tool like phpmyadmin:
select * from tt_content where field_test!='' and (CType = ...)
answered Nov 19 at 14:52
Bernd Wilke πφ
4,6611724
add a comment |
up vote
0
down vote
accepted
I've found a workaround for my problem.
I simply recreated field_test in TV+, went to the backend to empty the content of that field (which was filled even though the field had been deleted).
Conclusion: When you delete a field in TV+, the content of that field still exist somewhere…
answered Nov 19 at 15:03
CCR
45115
that is 'usual' behaviour of flexform data in TYPO3 as the data is stored as XML in one database field. The XML is extracted as an array, data is modified/added and stored back as XML. in this way no XML field gets deleted. If you write new data (array) to the field the array is merged with the existing. to clean up the XML (delete unused fields) you need to explicit clean up the `pi_flexform' field (overwrite with empty string) and then write the array with active data.
– Bernd Wilke πφ
Nov 20 at 6:43
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
you need to identify those CEs which have set field_test and where this field should be empty.
You could edit every CE, change it's type to a type where the field id visible, check for empty and change type back to origin.
or you do some immediate SQL queries in a tool like phpmyadmin:
select * from tt_content where field_test!='' and (CType = ...)
answered Nov 19 at 14:52
Bernd Wilke πφ
4,6611724
add a comment |
up vote
0
down vote
you need to identify those CEs which have set field_test and where this field should be empty.
You could edit every CE, change it's type to a type where the field id visible, check for empty and change type back to origin.
or you do some immediate SQL queries in a tool like phpmyadmin:
select * from tt_content where field_test!='' and (CType = ...)
answered Nov 19 at 14:52
Bernd Wilke πφ
4,6611724
add a comment |
up vote
0
down vote
up vote
0
down vote
you need to identify those CEs which have set field_test and where this field should be empty.
You could edit every CE, change it's type to a type where the field id visible, check for empty and change type back to origin.
or you do some immediate SQL queries in a tool like phpmyadmin:
select * from tt_content where field_test!='' and (CType = ...)
answered Nov 19 at 14:52
Bernd Wilke πφ
4,6611724
you need to identify those CEs which have set field_test and where this field should be empty.
You could edit every CE, change it's type to a type where the field id visible, check for empty and change type back to origin.
or you do some immediate SQL queries in a tool like phpmyadmin:
select * from tt_content where field_test!='' and (CType = ...)
answered Nov 19 at 14:52
Bernd Wilke πφ
4,6611724
answered Nov 19 at 14:52
Bernd Wilke πφ
4,6611724
answered Nov 19 at 14:52
Bernd Wilke πφ
4,6611724
answered Nov 19 at 14:52
Bernd Wilke πφ
4,6611724
4,6611724
add a comment |
add a comment |
up vote
0
down vote
accepted
I've found a workaround for my problem.
I simply recreated field_test in TV+, went to the backend to empty the content of that field (which was filled even though the field had been deleted).
Conclusion: When you delete a field in TV+, the content of that field still exist somewhere…
answered Nov 19 at 15:03
CCR
45115
that is 'usual' behaviour of flexform data in TYPO3 as the data is stored as XML in one database field. The XML is extracted as an array, data is modified/added and stored back as XML. in this way no XML field gets deleted. If you write new data (array) to the field the array is merged with the existing. to clean up the XML (delete unused fields) you need to explicit clean up the `pi_flexform' field (overwrite with empty string) and then write the array with active data.
– Bernd Wilke πφ
Nov 20 at 6:43
add a comment |
up vote
0
down vote
accepted
I've found a workaround for my problem.
I simply recreated field_test in TV+, went to the backend to empty the content of that field (which was filled even though the field had been deleted).
Conclusion: When you delete a field in TV+, the content of that field still exist somewhere…
answered Nov 19 at 15:03
CCR
45115
that is 'usual' behaviour of flexform data in TYPO3 as the data is stored as XML in one database field. The XML is extracted as an array, data is modified/added and stored back as XML. in this way no XML field gets deleted. If you write new data (array) to the field the array is merged with the existing. to clean up the XML (delete unused fields) you need to explicit clean up the `pi_flexform' field (overwrite with empty string) and then write the array with active data.
– Bernd Wilke πφ
Nov 20 at 6:43
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
I've found a workaround for my problem.
I simply recreated field_test in TV+, went to the backend to empty the content of that field (which was filled even though the field had been deleted).
Conclusion: When you delete a field in TV+, the content of that field still exist somewhere…
answered Nov 19 at 15:03
CCR
45115
I've found a workaround for my problem.
I simply recreated field_test in TV+, went to the backend to empty the content of that field (which was filled even though the field had been deleted).
Conclusion: When you delete a field in TV+, the content of that field still exist somewhere…
answered Nov 19 at 15:03
CCR
45115
answered Nov 19 at 15:03
CCR
45115
answered Nov 19 at 15:03
CCR
45115
answered Nov 19 at 15:03
CCR
45115
45115
that is 'usual' behaviour of flexform data in TYPO3 as the data is stored as XML in one database field. The XML is extracted as an array, data is modified/added and stored back as XML. in this way no XML field gets deleted. If you write new data (array) to the field the array is merged with the existing. to clean up the XML (delete unused fields) you need to explicit clean up the `pi_flexform' field (overwrite with empty string) and then write the array with active data.
– Bernd Wilke πφ
Nov 20 at 6:43
add a comment |
that is 'usual' behaviour of flexform data in TYPO3 as the data is stored as XML in one database field. The XML is extracted as an array, data is modified/added and stored back as XML. in this way no XML field gets deleted. If you write new data (array) to the field the array is merged with the existing. to clean up the XML (delete unused fields) you need to explicit clean up the `pi_flexform' field (overwrite with empty string) and then write the array with active data.
– Bernd Wilke πφ
Nov 20 at 6:43
that is 'usual' behaviour of flexform data in TYPO3 as the data is stored as XML in one database field. The XML is extracted as an array, data is modified/added and stored back as XML. in this way no XML field gets deleted. If you write new data (array) to the field the array is merged with the existing. to clean up the XML (delete unused fields) you need to explicit clean up the `pi_flexform' field (overwrite with empty string) and then write the array with active data.
– Bernd Wilke πφ
Nov 20 at 6:43
that is 'usual' behaviour of flexform data in TYPO3 as the data is stored as XML in one database field. The XML is extracted as an array, data is modified/added and stored back as XML. in this way no XML field gets deleted. If you write new data (array) to the field the array is merged with the existing. to clean up the XML (delete unused fields) you need to explicit clean up the `pi_flexform' field (overwrite with empty string) and then write the array with active data.
– Bernd Wilke πφ
Nov 20 at 6:43
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53373193%2fghost-field-in-templavoil%25c3%25a0%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
