Here I have tt_news 3.0.1 and a TYPO3 4.3.1. There are tt_news articles translated. If I look into the database (tt_news_cat_mm) than in the default language there are the categories 1,2,6,8 assigned. If I look on the translated article it only has the category 1 assigned.
In my opinion the translated article should have the same categories as the one in the default language. If I look into the backend I can only change the categories in the default language. There is no option available in the translated article.
Is that an error for the old tt_news extension?
Update:
It seems that the categories are only taken for the first translation. If you change the categories later they don't get updated in the translated version. Very annoying ...
Related
"fallbackType: free" in the config.yaml seems not to work with displaying sys_categories in the frontend. Backend works as expected, but in the frontend default and foreign language are shown together.
My news template shows a list of categories to filter news by categories. With "fallbackType: strict" this works fine, but not with "fallbackType: free": In the default language the list is shown in the default language, as expected. But in the foreign language we get a list of all translated categories and additional all categories in the default language. In single view of news i get the category list bound to the news always in the default language, never translated.
Is this a feature or a bug? How can i work around? I need "fallbackType: free" because my client wants to publish news in the foreign language without a news in the default language. So i can't simply switch back to "fallbackType: strict".
(TYPO3 10.4)
Thanks!
I am working on a TYPO3 v10 LTS website with integration of the news extension v8.3.0. Many news are assigned to multiple categories and they are displayed on different detail pages according to their assigned categories. Now I would like to define one categories as master and use this category for the generation of canonical links to avoid duplicate content problems. On an older version of the website (TYPO3 v7 LTS) I used the solution explained here: https://www.typo3.net/forum/thematik/zeige/thema/116056/
I'm not so experienced with TYPO3 v9/v10 LTS yet, but I think that there must be a solution with routeEnhancers.
Any hints are welcome.
You need no route enhancer, just use the basic configuration of EXT:news.
one solution would be: for detail-view (show) always use one page. in this way each news will have a unique url. (problem: you can't ´return´ to the former list view with a hard link[1], as you don't know from which list you came)
2nd: configure a show-page with your news-categories: this page will be preferred for detail view (it always will be the first category) and each news will always be shown on this category detail page. (no ´return´ to the original list as above)
[1] you can't use a page as link target, but you can use javascript:history.back()
After upgrading an installation from TYPO3 8 to TYPO3 9.5.5 and switching language configuration to sites (no more config.*language* in TypoScript), I do get some internationalization errors, mainly records displayed in the wrong language:
For a table which has a relation to categories, I do get some records displayed in translated form for a page in default language.
Powermail (upgraded from 6.2 to 7.2) shows a similar behaviour I think: Some field labels are shown in their translated versions (and, contrary to the category relation, no labels at all are loaded in the non-default language).
I have tested settings config.sys_language_overlay to 0, 1 and hideNonTranslated and config.tx_extbase.persistence.consistentTranslationOverlayHandling to 0 without success.
After multiple days of debugging and stepping through code I still do not have any idea where the error could be or which settings I should look into; any hints in that direction would be appreciated. I am also a bit unsure about what multilingual M:M relations (for the categories) should look like in the database and how they are supposed to work in ExtBase, but the behavior on 8.x was fine.
I'm using tx_news with imported news entries from tt_news.
The import worked well, but some news contain "old" links in the body field of this form
/index.php?id=10&tx_ttnews[tt_news]=123&tx_ttnews[mode]=single&tx_ttnews[backPID]=2&no_cache=1
Can these links be "mapped" somehow to work with tx_news?
Using Typo3 7.6.12
In short, this is not possible. However there are several options I am thinking of. In general those links should be defined by using the EXT:linkhandler
1) Convert manually: Sounds sad but if not too many links are there, it is certainly the fastest one.
2) Use one of the hooks of TYPO3 which are used during the bootstrapping and do custom redirects. E.g. $GLOBALS['TYPO3_CONF_VARS']['SC_OPTIONS']['tslib/index_ts.php']['preprocessRequest'].
3) Hook into the error handling and redirect right before showing any error page. One example to check out could be an ext I did: https://github.com/georgringer/fast_redirect. It must be certainly modified to fit your needs.
What you can actually do as well, which I did for a big import a while ago: Remove all news records again, truncate the table and use any PHP script and fill up the table tx_news_domain_model_newswith the same amount of news entries found in tt_news and set the uid to the one of tt_news and set the import_source field to TT_NEWS_IMPORT and the import_id field as well to the uid of the tt_news uid. After that, the import will pick the dummy tx_news_domain_model_news record, found by findOneByImportSourceAndImportId() and will enrich it with the regular data. You will end with news records having the same uid.
I am using the news plugin to simulate the classic page content elements but with previews. Now I would like to be able to manually set the order of the articles just as I would in the page module for the standard elements. But there seems to be no such option in the list module. How would I achieve such functionality?
There is an extension that adds a sorting field to tt_news so you can order the news entries in the list view. It has not been maintained for quite some time, but since it works on TCA and FlexForm level, it should still work with never versions. Check it out:
http://typo3.org/extensions/repository/view/mpossnewssorting