I use this TYPO3 news extension.
I want to disable paging though typoscript. The option for it is plugin.tx_news.settings.hidePagination so I tried this
plugin.tx_news {
settings.hidePagination = 1
}
But this doesn't work. However setting plugin.tx_news.settings.list.paginate.itemsPerPage to a very large value does work. But that isn't a very nice solution.
Have I missed something on how to set hidePagination?
Theres a checkbox in the tx_news plugin.
Additional -> Hide the pagination
It seems to overwrite the TS (unchecked by default).
Does
plugin.tx_news {
settings.hidePagination = 1
}
get called in your template?
You can always check this with
<f:debug><{settings}</f:debug> to see what get's parsed.
The option to hide the pagination only hides the pagination in the frontend and does not show all news entries at one page. You can only set a high number to the list View to show all entries at one page. I think, there is no other solution at this time.
To override the values set in the news plugin flexform, you have to add the field to plugin.txnews.settings.overrideFlexformSettingsIfEmpty.
To add the field in question to the news extension standard list add this to your TS:
plugin.txnews.settings.overrideFlexformSettingsIfEmpty := addToList(hidePagination)
Related
In TYPO3 9 the save and view button for tt_content and pages is missing. I tried reactivating it via user.ts:
options.saveDocView.tt_content = 1
options.saveDocView.pages = 1
Unfortunately nothing happens. Can someone help? Alternatively, is it possible to view the whole TCEMAIN config somewhere as you can with the TCA? Maybe I could go search there...
The feature you're looking for has been removed.
With TYPO3 version 9LTS a new concept for save document buttons was introduced.
See epic issue "Save Button Gate" on forge https://forge.typo3.org/issues/84751
See also concept here https://docs.google.com/document/d/1Pr85TllSeuYvy5pxUz9A2k-YFrJNW5J5FuCVpuPkYPY.
options.saveDocView will just handle visibility of the single view-button for current document.
options.saveDocView = 1 is default for TYPO3 v9LTS.
options.saveDocView.pages = 0 fx. will override defaults and disable the view-button for entries of table pages.
I am trying to make an "Infobox" with TYPO3.
In my HTML Template i have the Infobox:
<div id="infobox">
<!-- ###infobox### start -->
CONTENT from the backend
<!-- ###infobox### start -->
</div>
...
Now in my Backend, i have a content element, that keeps the content for my Infobox in the Frontend:
What i want to do is: If i disable the content element via the "disable button" in the backend, i want to change the CSS of my #infobox (adding display:none) or if I re-enable it I want to remove the display:none.
I hope I could explain my issue and hope someone can help me.
As far as I understand, you want the disabled flag of the content element to only influence the rendered output, not switch off the rendering.
I fear that this is not easily possible. The disabled column is part of TYPO3’s so-called enable fields, for which checks are added all over the place by the TYPO3 API. Due to this, "hidden" records are usually not even selected from the database, so they are also never fed to the rendering engine.
An alternative would be to use a custom content type with a custom field for your purpose, hide the "hidden" field in the form for that type and put the custom field in its place. This can all be done with standard TYPO3 core mechanisms.
What you cannot avoid however is that somebody will be able to hide/disable the content element from the page or list module. This cannot be prevented as your content needs to live in the same table (tt_content) as the rest of the content—and the settings for enable fields are global per table.
You can use an custom fluid content element
see: http://www.creativeworkspace.de/blog/artikel/eigene-inhaltselemente-im-typo3-cms-62x-und-7x/
or: https://docs.typo3.org/typo3cms/extensions/fluid_styled_content/7.6/AddingYourOwnContentElements/Index.html
or you use a custom layout
TCEFORM.tt_content {
layout {
addItems {
item1 = Name of Layout
}
}
}
after this you can get it with {data.layout} in your template
{f:if(contition:'{data.layout} == item1',then:'display:none')}
I am using TYPO3 6.2.9 CMS.I make category and assigned to page.But I don't know how to display the category when i am showing the page i want all the category assign to that page must display then after clicking that category the content which i have assign to that category must display
There is no out-of-the box solution for this.
But you can use the following :
Or create your own extension where you gather the categories of your page and render them on your page. You then can also create a sort of category menu.
You can use category collection :
http://docs.typo3.org/typo3cms/CoreApiReference/ApiOverview/Categories/Index.html
cObject RECORDS has also a categories property, so you could also use typoscript for rendering.
For this purpose you can use extensions to your website.
Catalogue extension package
Which relates to categorisers and if you want to you can customize it in your own manner.
Use of these extensions make simple in listing category.
The usage is also given in its manual ans its simple to adopt it.
Does anyone know how I can completely remove the [more] link that appears next to the subheader in tt_news items in typo3? I've tried the following, but neither removes the anchor tag that is generated:
_LOCAL_LANG.default.more =
_LOCAL_LANG.default.more >
Any help would be appreciated.
In tt_news v3 list view, use
plugin.tt_news.displayList.subheader_stdWrap.append >
With _LOCAL_LANG you can only override or clear language labels. The tags are generated in the code or templates.
In TYPO3 6.1, how do I get the tsconfig for the tx_news news extension to work?
I try to add selectable layouts to news items:
tx_news.templateLayouts {
1 = A custom layout
99 = LLL:fileadmin/somelocallang/locallang.xml:someTranslation
}
This should add the new Layout to the Type field, as in:
or did I get that wrong? Where can that new custom layout be selected?
Also, I'm trying to prefill fields in flexforms (when a new plugin is inserted):
TCEFORM.tt_content.pi_flexform.tx_news.sDEF.categoryConjunction = and
But it does not work yet.
How can this be done?
With tx_news.templateLayouts you override the flexform for the news plugin you insert on a page, not for a news record.
Your second code looks almost right, but you forgot settings: TCEFORM.tt_content.pi_flexform.tx_news.sDEF.settings.categoryConjunction = and
And even though this code is right, it will not work because of a bug with flexform fields that have a dot in their name (this is just stupid).
I think the only way to cleanly modify the flexform, is to write a small extension which overrides the default news flexform.