Environment:
TYPO3: 8LTS
News: 6.3.0 (also checked with 7.x)
News List View (Page) is translated
News Detail View (Page) is translated
News Record translated
Problem:
When i visit the page on language UID 1 the news record itself is translated (For example headline). In the Detail view we render the content element. This is always shown in the default language
The Problem could be fixed by switching sys_language_overlay from 0 to 1
config {
sys_language_mode = content_fallback
sys_language_overlay = 1
}
To prevent that the content elements are hidden by default you could also set
TCEMAIN.table.tt_content {
disablePrependAtCopy = 1
disableHideAtCopy = 1
}
Related
It is not a bug, of course, but i cant figure out how to solve it.
With previous version of News there was all fine.
Sorry for my language, it hard to explain.
Current Behavior
For example - I have this page title behaivor for the first time news detail page visit -
"SiteName: Some NewsRecord Title" (this is fine, how it should be).
Then when i go to list view, and again click on news to view it in detail (or just refresh the page I'm currently viewing) - page title gets look like this:
"SiteName: news" where "news" is a page title in the backend page tree, that contains newsDetailView plugin
To override this strange behavior, i use such typoscript setup (But this should not be a permanent solution to the problem, of course)
[globalVar = TSFE:id = 7]
config.noPageTitle = 2
temp.newsTitle = RECORDS
temp.newsTitle {
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 = <title>SiteName: |</title>
}
page.headerData.1 >
page.headerData.1 < temp.newsTitle
[global]
Environment
TYPO3 version(s): [9.5.15]
news version: [8.0.0]
Composer (Composer Mode): [no]
With 9.5 and the nice SEO extension you really shouldn't do such stuff anymore. Don't use config.noPageTitle and it should work out of the box as the news extension will set the title just right.
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)
I have a website with some pages, presented in a normal menu. Every page has subpages and shows them in a submenu. Except one page. This page has no subpages and should have a content menu which navigates to different content sections on the page. The thing with the content navigation is done with:
temp.contentnav = CONTENT
temp.contentnav {
table = tt_content
select {
pidInList = 7
orderBy = sorting
where = colPos=0
languageField=sys_language_uid
}
renderObj = TEXT
renderObj {
field = header
wrap= <li>|</li>
typolink.parameter.field=pid
typolink.parameter.dataWrap=|#{field:uid}
typolink.ATagParams = class="linkSubpage"
if.isTrue.field=header
}
wrap = <ul id="subMenu"> | </ul>
}
page.10.marks.MENU.2a.NO.after.cObject < temp.contentnav
but this works only if the page has at least one subpage. The workaround would be to add a subpage and hide the submenulink, but is there a better solution to show the custom submenu without adding subpages?
Use a HMENU item with the levels to generate your submenu.
Your behavior is not the right one in the TYPO3 working style. Use the rights TypoScript objects.
And remove the "a" from the "page.10.marks.MENU.2a.NO". The correct use is 1,2,3,...
http://docs.typo3.org/typo3cms/TyposcriptReference/MenuObjects/CommonProperties/Index.html
http://docs.typo3.org/typo3cms/TyposcriptReference/MenuObjects/CommonItemStates/Index.html
http://docs.typo3.org/typo3cms/TyposcriptReference/MenuObjects/Tmenu/Index.html
http://docs.typo3.org/typo3cms/TyposcriptReference/MenuObjects/Tmenuitem/Index.html
I am new to TYPO3 (6.0) and have a problem with displaying inherited content elements. I have set up the template with the slide variable:
temp.content = CONTENT
temp.content {
table = tt_content
select.orderBy = sorting
select.where = colPos = 0
select.languageField = sys_language_uid
}
temp.content_slide = CONTENT
temp.content_slide {
table = tt_content
select.orderBy = sorting
select.languageField = sys_language_uid
slide = -1
}
This works pretty well for the pages that are below the main page, AS LONG as they are not contained in a folder. When the subpages are contained in a folder, all inherited content elements are NOT SHOWN.
So:
MainPage > StandardSite1 > StandardSite2
All inherited elements from MainPage are shown in the StandardSites
MainPage > Folder > StandardSite3
NO inherited element from MainPage is shown in StandardSite3
Any idea, how to show the inherited content elements of MainPage in Standard sites, that are contained in a folder?
Thanks in advance,
Frank
I think this is not possible, because you slide up the rootline to collect the content elements. However the rootline breaks at a storage folder.