I'm using tx_news and coolUri in my project. Everything works fine except the pagination. If i want to switch away from the first page nothing happens. The URL is changing but the view doesn't.
Did someone already have this problem and would have a solution for it?
I had the same problem with tx_news and CoolUri and solved it by replacing the pagination wizard with the standard pagination wizard from TYPO3
<f:widget.paginate objects="{news}" as="paginatedNews"configuration="{itemsPerPage: 10, insertAbove: 1, insertBelow: 1, maximumNumberOfLinks: 25}">
(...)
</f:widget.paginate>
Related
I wonder how to get the editor (image manipulation / crop) in Typo3 Flexform FAL image working. How to run up the FAL inside Flexform is not a big deal, but... how to get the editor? I din't found any solution, so it would be great getting some help.
the reason why I try it in flexform, is that I want ot stay on core functions without using flux and all that horrible stuff just to prevent version chaos....
here is a similar example of how I realsied it in Flexform.
How to create a file upload field in flexform of a custom extbase extension in TYPO3 10?
anyone got a solution get the editor running?
Found a solution
https://blog.wappler.systems/typo3-fal-image-in-flexform/
BUT: how can I use the cropped image in FE?
typo3 7.6.10
news 4.3.0
I have a strange cache behaviour:
I made an extension which extends the news model with a select field "teasercolor" and a checkbox "showimage".
http://pastebin.com/ViPEemr9
In the fluid view, I use these news fields like this:
<div class="overlay {newsItem.teasercolor}">
This seemed to work. But after a while, my teasercolor class disappears from the code. Same with the checkbox value.
When I then delete the fe cache in the backend, it re-appears.
After a while it disappears again. Never seen such a behaviour again.
Has somebody an idea?
have you a clean dependency to ext:news?
do you use Resources/TCA/Overrides/....php?
https://docs.typo3.org/typo3cms/TCAReference/ExtendingTca/StoringChanges/Index.html
I tried the latest versions of flux in a fresh TYPO3 Instalaton 6.2.7 and 6.2.9.
I used the same templates for fluidcontent and fluidpages and it dont work properly.
The Page Grids dont work. (The default TYPO3 Grids are shown)
And the grids in the content elements dont work too.
Is there a solution for this?
If it shows the default TYPO3 columns, you probably did not select the fluidpages backend layout in the page record. In recent fedext/TYPO3 versions, you need to edit the properties of your root page and set both "Backend Layout (this page only)" and "Backend Layout (subpages of this page)" to "Fluidpages" in the "Appearance" tab
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.
I have started using the TYPO3 extension "news" and I would like to create in the LIST VIEW a "Facebook Like Button" for the Detail View of each enty. For this I need to fetch the URL of the DETAIL VIEW, not the whole <a> tag. How can i do this?
I tried this, but it didnt work:
<n:link configuration="{returnLast: 'url'}" newsItem="{newsItem}" settings="{settings}">
Link to detail page
</n:link>
It uses Fluid Templates, which I'm completely new with, so I don't know how complicated this actually is.
I found the solution. parameter uriOnly:
<n:link uriOnly='1' newsItem='{newsItem}' settings='{settings}'></n:link>"