I use TYPO3 version 8.7.10. I am trying to remove "copy 1" text when I copy the content.
I have tried:
TCEMAIN.table.pages {
disablePrependAtCopy = 1
disableHideAtCopy = 1
}
TCEMAIN.table.tt_content {
disablePrependAtCopy = 1
disableHideAtCopy = 1
}
Not successfully
Did you enter those values to Typoscript-Setup or the Page TSConfig of the Root Page? It belongs to the TSConfig in the page configuration.
Related
Why showPermaLogin property (felogin) is not working on TYPO3 9.5.4 ?
I have tried to add these code
plugin.tx_felogin_pi1.templateFile = fileadmin/pricingdesign/resources/private/layouts/logintest.html
plugin.tx_felogin_pi1.showPermaLogin = 2
plugin.tx_felogin_pi1.showForgotPasswordLink = 2
All code in Typoscript file
# Default PAGE object:
page = PAGE
page {
10 = CONTENT
10 {
table = tt_content
select.orderby = sorting
}
includeCSS {
screen = fileadmin/pricingdesign/resources/private/assets/css/signin.css
screen.title = display
screen.media = screen
bootstrap = fileadmin/pricingdesign/resources/private/assets/css/bootstrap.min.css
}
bodyTag = <body class="text-center">
}
plugin.tx_felogin_pi1.templateFile = fileadmin/pricingdesign/resources/private/layouts/logintest.html
plugin.tx_felogin_pi1.showPermaLogin = 2
plugin.tx_felogin_pi1.showForgotPasswordLink = 2
This has just only showed 'Forgot your password?' on result page and no something like 'Remember login'.
enter image description here
Assuming your template contains the correct parts, there are 2 common reasons why the checkbox might not be shown:
$GLOBALS['TYPO3_CONF_VARS']['FE']['permalogin'] is not 0 (allowed, off by default) or 1 (allowed, on by default). -1 will disable it completely, 2 will force it enabled.
$GLOBALS['TYPO3_CONF_VARS']['FE']['lifetime'] is set to 0 (or less). This will set the cookie lifetime to 0, which will delete the cookie when the session ends, so perma login will do nothing and it will not be shown.
Also you don't have to set plugin.tx_felogin_pi1.showPermaLogin to 2. This variable is boolean, so should be 0 or 1 (in your case 1). This should not affect the result though as 2 is also seen as true.
TYPO3 7.6.15
Powermail 3.18.0
The date picker field does not open the popup calendar. I have narrowed down the cause being because the necessary CSS files are not being included for this feature. Is there an error in my setup? How do I have them included automatically?
This is what I have in my TS Setup:
plugin.tx_powermail {
view {
templateRootPaths >
templateRootPaths {
0 = {$plugin.tx_powermail.view.templateRootPath}
1 = fileadmin/template/mysite/powermail/Templates/
}
partialRootPaths >
partialRootPaths {
0 = {$plugin.tx_powermail.view.partialRootPath}
1 = fileadmin/template/mysite/powermail/Partials/
}
layoutRootPaths >
layoutRootPaths {
0 = {$plugin.tx_powermail.view.layoutRootPath}
1 = fileadmin/template/mysite/powermail/Layouts/
}
}
_LOCAL_LANG.default {
datepicker_format_date = d/m/Y
datepicker_format_time = H:i
datepicker_format_datetime = d/m/Y H:i
}
}
The only way I have found to make it work correctly is by manually adding it like this:
page.includeCSS {
file4 = EXT:powermail/Resources/Public/Css/Basic.css
}
in the Documentation ist a hint:
https://docs.typo3.org/typo3cms/extensions/powermail/ForAdministrators/Installation/Index.html#addbootstrapclassesandcsstopowermail
you should
add the static template Add classes and CSS based on bootstrap (powermail)
There the css is included
You need to tell powermail to load the JavaScript libraries by setting a constant in your TypoScript template:
plugin.tx_powermail.settings.javascript.addAdditionalJavaScript = 1
See https://docs.typo3.org/typo3cms/extensions/powermail/Faq/Index.html#datetimepickernotworking for more information.
Adding the static template file would result in a TypoScript like
plugin.tx_powermail.settings.BasicCss
=EXT:powermail/Resources/Public/Css/Basic.css
this should load everything.
The datepicker styles are originally located in https://github.com/einpraegsam/powermail/blob/develop/Resources/Private/Sass/_DatePicker.scss
I am trying to create a custom menu element by using this in the Page TSConfig:
TCEFORM.tt_content {
menu_type.addItems.101 = My Menu
}
And this in Setup:
temp.my_menu = HMENU
temp.my_menu {
special = list
special.value.field = pages
1 = TMENU
1 {
wrap = <ul> | </ul>
NO = 1
NO.wrapItemAndSub = <li>|</li>
}
}
tt_content.menu.20.101 < temp.my_menu
But I get 'Oops, an error occurred!' where the menu should be.
It will render fine if I remove the Fluid includes in the template but then all the other content elements give errors.
Is there any way to have a typoscript menu element at the same time as fluid styled content?
Or if I really have to, how do I add a custom fluid menu template?
You need to move the line with the copy operation down to the bottom, otherwise the configuration is not copied, because it is not there yet.
The exception happens, because there is no rendering definition for the menu (because you never copied the configuration).
To see the real error instead of the exception, switch to the development preset in the install tool oder add the following line to your TS setup:
config.contentObjectExceptionHandler = 0
I noticed this :
TCEFORM.tt_content {
menu_type.addItems.101 = My Menu
}
as far as I know should be this :
TCEFORM.tt_content.menu_type {
types {
menu{
addItems {
101 = My Menu
}
}
}
}
I had to 'tweak' the special menus (typo3 7.6) and this worked:
Add special menu and add class="active" in TYPO3
I'm stuck in a TS problem related to a special browse HMENU. I'm using TYPO3 7.6.11.
Site Structure:
/ Page 1
// Page 1.1
// Page 1.2
// Page 1.3
/ Page 2
/ Page 3
I'd like to integrate a Previous / Next navigation for the first navigation level. On Page 1, you can switch to Page 2. On Page 2, you can switch to Page 1 or Page 3. I used following code and it works on the first level:
lib.newsletter = COA
lib.newsletter {
10 = HMENU
10 {
special = browse
special {
items = prev
}
1 = TMENU
1 {
NO.ATagParams = class="prev"
}
}
20 < .10
20 {
special.items = next
1.NO.ATagParams = class="next"
}
}
When I open a page of the second level, I'd still like to browse on the first level. So when I'm on Page 1.2 and click on the "Next" button, "Page 2" should open.
I've tried to set an entry level in combination with a treeLevel condition but the entryLevel has no effect.
Do you have an idea? Your help is really appreciated.
Thanks in advance,
Tom
entryLevel won't work here because it's relative to the current page. You can however set .special.value to another page id to make it relative to that page. This property supports stdWrap so you can be creative with things like
.special.value.data = leveluid:1 (page in first level of the root line)
See TypoScript reference
This is probably very basic, but I'm stuck.
In TYPO3 6.1.x with tx_news, I have configured the news detail view to appear on the same page as the list view as taught on http://docs.typo3.org/typo3cms/extensions/news/latest/Main/Tutorial/IntegrationWithTs/Index.html
Also, I have pulled in the news'header as h1 as such
temp.h1 = COA
temp.h1 {
10 = TEXT
10 {
value = <h1>{page:title}</h1>
insertData = 1
}
10 = RECORDS
10 {
if.isTrue.data = GP:tx_news_pi1|news
dontCheckPid = 1
tables = tx_news_domain_model_news
source.data = GP:tx_news_pi1|news
source.intval = 1
conf.tx_news_domain_model_news = TEXT
conf.tx_news_domain_model_news {
field = title
htmlSpecialChars = 1
}
wrap = <h1>|</h1>
}
}
What I couldn't solve yet is that the plugin element has a title (in the regular "header" field). I need to display this header only in the list, but hide that plugin's header field in detail view.
How / where can I do that via page TS?
This is probably not even in the plugin, but in css_styled_content?
Something like this...
[globalVar = GP:tx_news_pi1|news > 0]
plugin.tx_news.stdheader >
[else]
But how?
A plugin is always using this prototype object:
tt_content.list
Therefore you could delete the header of this object like that
tt_content.list.10 >
But if you have other plugins on the same page, their headers would also be deleted. So that would be a bad idea.
I would suggest you use the header_layout field. By default it has an entry called "Hidden" that will hide the header of your plugin. If you don't have it, check the Page TypoScript configuration. You can add own items by using:
TCEFORM.tt_content.headerLayout.addItems.99 = My Header Layout
Then you can then define the rendering of your own layouts in
lib.stdheader.10
(it's a CASE object)