I am facing problem with tt_news in typo3 version 6.2.11.
I can not set date above 2020 year. I can set till 31.12.2020 and after that all dates are disabled.
I have taken 2 screenshot of it. Any hint or solution would help me.
Thanks
enter image description here
tt_news has a hardcoded maximum for the end date, which in the version you're using is 31-12-2020. The best advice is to upgrade. TYPO3 6.2 isn't supported anymore.
However, if you need a quick fix, you'll need to change it in the TCA file of tt_news. You can find that in typo3conf/ext/tt_news/tca.php or typo3conf/ext/tt_news/Configuration/TCA/tt_news.php depending on which version of the extension you're using.
This file contains an array with the configuration of the fields for this table. For the field endtime it should contain something like this:
'range' => [
'upper' => mktime(0, 0, 0, 31, 12, 2020)
]
You'll need to change that date.
The range-array occurs twice in tca.php. The first occurrence should be updated
$TCA['tt_news']['columns']['endtime']['config']['range']['upper']
At the next one you can do as well
$TCA['tt_news_cat']['columns']['endtime']['config']['range']['upper']
My fault was to change the latter one without effect.
Related
TYPO3 9.5.15
When I edit an existing category and than click the "+new" button inside the edit form, i will get the error:
#1534710048 TYPO3\CMS\Core\Exception\SiteNotFoundException
No pseudo-site found in root line of page 17
Page 17 in this case is absolute incorrect - this is the uid of the sys_category from which editing form I came from. the categories were saved on pid:6
I can do the same task from other category edit-forms, but not from all. I cannot figure out what is the difference of the categories where it doesnt work.
The basic site-configuration is configured and working, there is only one language, no workspaces.
Has anyone ever had a similar problem?
Side note: It still "works" for records which have the same uid as a pages record. It also "works" for L>0 records because they still fall back to 0.
However, this is not a core bug but a misuse of the internal DisplayCond by 3rd party extensions.
E.g. in the latest tt_address this is already fixed, see: https://github.com/FriendsOfTYPO3/tt_address/commit/4501d1f30f3381a235e447567018e6d5646ec069
So changing the TCA DisplayCond of the sys_category slug in my own extension did the trick in my setting
'displayCond' => 'VERSION:IS:false',
Since updating from Flux 6.0.2 to the newest Flux TER-Release (7.0.0) I have the problem that all my defined flux:field.select items are switched. I have them defined as an array like this items="{0: {0: 'value shown as a CSS class in the frontend',1: 'value shown in BE'},}". But now I get the BE value in the frontend template.
Also all my content elements from my provider extension are shown twice (without a title) in the backend and the fields defined in the 'Configuration' section of my content element are shown twice.
There's also a RTE field shown at the bottom of my content element that has not been there before.
BE Output: view
Code on Pastebin: http://pastebin.com/CNcphn2k
Any help deeply appreciated.
EDIT:
I just set up a fresh instance of TYPO3 6.1.9 (blank package) and installed my extension with the above mentioned content elements. Dependencies were resolved automatically as it should (newest versions). Via the content wizard I tried to create a new element and I get the same result as in my existing install I first noticed this bug in.
EDIT2:
I was able to narrow it down to the flux:form.container tag. This duplicates the output in the BE. The select values are still switched though.
It is possible that you missed this official announcement:
http://fluidtypo3.org/blog/news/new-colpos-value.html
Failure to run the update script before letting TYPO3 change the type of the colPos value will result in the symptoms you describe. There is, unfortunately, no way to restore this (since your SQL will have cropped off all negative values and made them zero without any backup).
Restore from a backup and run the script and you should be fine.
I'm running TYPO3 V6 and the latest version of tx_news (not tt_news) and when I attempt to change the order of sorting for the LIST display, the settings in the plugin are not overriding the Typoscript settings. There doesn't seem to be a way to change to sort order of articles in the list view. I am aware that flagging a news record as "top news" will float it to the top of the list, but none of my records have that flag set.
Has anyone else had this problem?
I got the same problem: My listview always showed the oldest news on the top. I've been searching for a solution for hours. As i wanted to start to change the extension files manually, I found the "setup.txt" in the configuration folder. From there I copied the following code into my Typoscript. The problem is solved now.
plugin.tx_news{
settings{
overrideFlexformSettingsIfEmpty = cropMaxCharacters,dateField,timeRestriction,orderBy,orderDirection,backPid,listPid,startingpoint,recursive
orderBy = datetime
orderDirection = desc
orderByRespectTopNews = 0
orderByAllowed = sorting,author,uid,title,teaser,author,tstamp,crdate,datetime,categories.title
list{
paginate {
itemsPerPage=4
insertBelow=TRUE
lessPages=TRUE
#forcedNumberOfLinks=3
pagesBefore=1
pagesAfter=1
}
}
}
}
You can ignore the pagination lines. Important is the orderby stuff.
Typo3 Version: 4.7 (not my fault :D )
News System Version: 2.3
Found the solution to this one - basically I had been loading the TS setup code from an external file, which was overriding the default TS setup from the Typoscript template setup field, or rather, it wasn't. I duplicated the TS code in the Typoscript template and the external file and finally it is being recognised and the fields can be sorted.
I'm building a Typo3 website with the TT_NEWS extension; now I want to create a TT_NEWS list/latest view with a certain date range, but I cant find a way to do so.
I can't use the ARCHIVE function because I need a specific data range.
I hope that one of you knows the magic answer :-)
You can try setting an exact date range for the archive with TypoScript:
plugin.tt_news.amenuStart = 1.2.2003
plugin.tt_news.amenuEnd = 4.5.2006
This is assuming you only need one date range. For more than one range, maybe news categories would do the trick, but you'd need to assign them manually.
For tx_news use this in TypoScript:
1.settings.timeRestriction = 01.02.2003
1.settings.timeRestrictionHigh = 04.05.2006
The content element file-links now accepts 10 files max. How to increase them ?
Typo3 Version: 4.4.8
There is an extension that solves your problem here:
http://typo3.org/extensions/repository/view/icti_ext_filelinks/current/
TYPO3 Backend Modul "Admin Tools" select "configuration".
Select "TCA" in the select box at the top. Then you can see the Typo Configuration Array.
Select (click on the small arrow) "tt_content", then "columns", then "media" then "config".
Now you can see the "maxitems". If you now click on the entry "maxitems" you will get an php code ($TCA['tt_content']['columns']['media']['config']['maxitems'] = 10;)
TYPO3 4.5 or newer: change the value and save, before 4.5 you need to do the next two steps:
Copy this code, change the value and insert into typo3conf/extTables.php
check if $typo_db_extTableDef_script = 'extTables.php'; is set in your localconf.php
Now you should be able to just change any TCA entry.
Have fun:)