TYPO3 replacement for “top margin” and “bottom margin” in LTS 7
With TYPO3 LTS 7 and up, top margin and bottom margin are not suported by Fluid styled content.
css styles content 
My users used a lot of those margins in 6.2 LTS
How can I do to make this working again (override TCA, extension, etc)?
typo3 typo3-7.6.x typo3-extensions fluid-styled-content
asked Nov 11 at 20:56
SteveLeg
328
add a comment |
With TYPO3 LTS 7 and up, top margin and bottom margin are not suported by Fluid styled content.
css styles content
My users used a lot of those margins in 6.2 LTS
How can I do to make this working again (override TCA, extension, etc)?
typo3 typo3-7.6.x typo3-extensions fluid-styled-content
asked Nov 11 at 20:56
SteveLeg
328
add a comment |
With TYPO3 LTS 7 and up, top margin and bottom margin are not suported by Fluid styled content.
css styles content
My users used a lot of those margins in 6.2 LTS
How can I do to make this working again (override TCA, extension, etc)?
typo3 typo3-7.6.x typo3-extensions fluid-styled-content
asked Nov 11 at 20:56
SteveLeg
328
With TYPO3 LTS 7 and up, top margin and bottom margin are not suported by Fluid styled content.
css styles content
My users used a lot of those margins in 6.2 LTS
How can I do to make this working again (override TCA, extension, etc)?
typo3 typo3-7.6.x typo3-extensions fluid-styled-content
typo3 typo3-7.6.x typo3-extensions fluid-styled-content
asked Nov 11 at 20:56
SteveLeg
328
asked Nov 11 at 20:56
SteveLeg
328
edited Nov 11 at 23:46
asked Nov 11 at 20:56
SteveLeg
328
asked Nov 11 at 20:56
SteveLeg
328
asked Nov 11 at 20:56
SteveLeg
328
328
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I think you can
- install Fluid Styled Content and CSS Styled Content;
- then don't add the static typoscript of css styled content.
- modify the templates or partials of the Fluid Styled Content elements to use the new fields.
I don't know if this scenario have hidden drawbacks that I currently don't see.
Another scenario could be to use the CSS Styled Content also on version 7 and plan a migration to version 8 or 9 where they're used again, but they have become dropdown lists; plus, even the field names in database has changed: in version 6.2 they were spaceBefore and spaceAfter while since 8.7 they're called space_before_class and space_after_class.
As far as I know there are no conversion or upgrade tools between these fields.
See here and here for further details.
answered Nov 11 at 22:00
Riccardo De Contardi
1,149313
Are you saying that top margin and bottom margin are back in LTS 8? We plan to migrate to 7 and 8 in a few months
– SteveLeg
Nov 11 at 23:43
1
yes, but in a different way: See docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/… and docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/…
– Riccardo De Contardi
Nov 12 at 10:23
I've enriched my answer.
– Riccardo De Contardi
Nov 13 at 21:40
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f53253152%2ftypo3-replacement-for-top-margin-and-bottom-margin-in-lts-7%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I think you can
- install Fluid Styled Content and CSS Styled Content;
- then don't add the static typoscript of css styled content.
- modify the templates or partials of the Fluid Styled Content elements to use the new fields.
I don't know if this scenario have hidden drawbacks that I currently don't see.
Another scenario could be to use the CSS Styled Content also on version 7 and plan a migration to version 8 or 9 where they're used again, but they have become dropdown lists; plus, even the field names in database has changed: in version 6.2 they were spaceBefore and spaceAfter while since 8.7 they're called space_before_class and space_after_class.
As far as I know there are no conversion or upgrade tools between these fields.
See here and here for further details.
answered Nov 11 at 22:00
Riccardo De Contardi
1,149313
Are you saying that top margin and bottom margin are back in LTS 8? We plan to migrate to 7 and 8 in a few months
– SteveLeg
Nov 11 at 23:43
1
yes, but in a different way: See docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/… and docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/…
– Riccardo De Contardi
Nov 12 at 10:23
I've enriched my answer.
– Riccardo De Contardi
Nov 13 at 21:40
add a comment |
I think you can
- install Fluid Styled Content and CSS Styled Content;
- then don't add the static typoscript of css styled content.
- modify the templates or partials of the Fluid Styled Content elements to use the new fields.
I don't know if this scenario have hidden drawbacks that I currently don't see.
Another scenario could be to use the CSS Styled Content also on version 7 and plan a migration to version 8 or 9 where they're used again, but they have become dropdown lists; plus, even the field names in database has changed: in version 6.2 they were spaceBefore and spaceAfter while since 8.7 they're called space_before_class and space_after_class.
As far as I know there are no conversion or upgrade tools between these fields.
See here and here for further details.
answered Nov 11 at 22:00
Riccardo De Contardi
1,149313
Are you saying that top margin and bottom margin are back in LTS 8? We plan to migrate to 7 and 8 in a few months
– SteveLeg
Nov 11 at 23:43
1
yes, but in a different way: See docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/… and docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/…
– Riccardo De Contardi
Nov 12 at 10:23
I've enriched my answer.
– Riccardo De Contardi
Nov 13 at 21:40
add a comment |
I think you can
- install Fluid Styled Content and CSS Styled Content;
- then don't add the static typoscript of css styled content.
- modify the templates or partials of the Fluid Styled Content elements to use the new fields.
I don't know if this scenario have hidden drawbacks that I currently don't see.
Another scenario could be to use the CSS Styled Content also on version 7 and plan a migration to version 8 or 9 where they're used again, but they have become dropdown lists; plus, even the field names in database has changed: in version 6.2 they were spaceBefore and spaceAfter while since 8.7 they're called space_before_class and space_after_class.
As far as I know there are no conversion or upgrade tools between these fields.
See here and here for further details.
answered Nov 11 at 22:00
Riccardo De Contardi
1,149313
I think you can
- install Fluid Styled Content and CSS Styled Content;
- then don't add the static typoscript of css styled content.
- modify the templates or partials of the Fluid Styled Content elements to use the new fields.
I don't know if this scenario have hidden drawbacks that I currently don't see.
Another scenario could be to use the CSS Styled Content also on version 7 and plan a migration to version 8 or 9 where they're used again, but they have become dropdown lists; plus, even the field names in database has changed: in version 6.2 they were spaceBefore and spaceAfter while since 8.7 they're called space_before_class and space_after_class.
As far as I know there are no conversion or upgrade tools between these fields.
See here and here for further details.
answered Nov 11 at 22:00
Riccardo De Contardi
1,149313
edited Dec 4 at 15:23
answered Nov 11 at 22:00
Riccardo De Contardi
1,149313
answered Nov 11 at 22:00
Riccardo De Contardi
1,149313
answered Nov 11 at 22:00
Riccardo De Contardi
1,149313
1,149313
Are you saying that top margin and bottom margin are back in LTS 8? We plan to migrate to 7 and 8 in a few months
– SteveLeg
Nov 11 at 23:43
1
yes, but in a different way: See docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/… and docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/…
– Riccardo De Contardi
Nov 12 at 10:23
I've enriched my answer.
– Riccardo De Contardi
Nov 13 at 21:40
add a comment |
Are you saying that top margin and bottom margin are back in LTS 8? We plan to migrate to 7 and 8 in a few months
– SteveLeg
Nov 11 at 23:43
1
yes, but in a different way: See docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/… and docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/…
– Riccardo De Contardi
Nov 12 at 10:23
I've enriched my answer.
– Riccardo De Contardi
Nov 13 at 21:40
Are you saying that top margin and bottom margin are back in LTS 8? We plan to migrate to 7 and 8 in a few months
– SteveLeg
Nov 11 at 23:43
Are you saying that top margin and bottom margin are back in LTS 8? We plan to migrate to 7 and 8 in a few months
– SteveLeg
Nov 11 at 23:43
1
1
yes, but in a different way: See docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/… and docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/…
– Riccardo De Contardi
Nov 12 at 10:23
yes, but in a different way: See docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/… and docs.typo3.org/typo3cms/extensions/core/Changelog/8.6/…
– Riccardo De Contardi
Nov 12 at 10:23
I've enriched my answer.
– Riccardo De Contardi
Nov 13 at 21:40
I've enriched my answer.
– Riccardo De Contardi
Nov 13 at 21:40
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%2f53253152%2ftypo3-replacement-for-top-margin-and-bottom-margin-in-lts-7%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
