Typo3 tt-news categories - typo3

My client wants to update an old tt-news installation version 2.x. Unfortunately the former maintainer of the site quit the job and let me do his job and although there is a huge category tree of news none of the categories are selected in the plugin configuration dialog at several locations. This seems to work with an older Typo3 4.1.3 but not when I update to a newer version. My question is it possible the tell tt-news with Typoscript or with a constant the current news category and how?

plugin.tt_news {
categorySelection = 2,3
# show only selected categories
categoryMode = 1
}
Details about this: http://typo3.org/documentation/document-library/extension-manuals/tt_news/3.1.0/view/1/4/

Related

Fetching all base URLs from site config in TYPO3

In an extension we build for TYPO3 8 we check if a URL entered by a user is a local URL by checking the domain against records in the sys_domain table. We're now updating that extension for TYPO3 9 and 10. sys_domain has been deprecated in TYPO3 9 and removed in 10. It has been replaced with settings in the site configuration.
Is there an easy way to fetch all known base URLs (including variants and languages) from the site configuration without parsing and looping through the site configuration myself?
Yes it is possible. You need to use the PHP API: Accessing Site Configuration
here is an example:
$siteFinder = GeneralUtility::makeInstance(SiteFinder::class);
$allsites = $siteFinder->getAllSites();
This is the results
Best regards

Typo3 Exception - No suitable request handler found

so i was on vacation for 5 Days and when i came back our Website (Typo 3 - 7.6.25) was "broke".
If i try to go on the page i get the following Error:
#1205414233: No suitable request handler found.
TYPO3\CMS\Extbase\Mvc\Exception thrown in file
/html/typo3/typo3_src-7.6.25/typo3/sysext/extbase/Classes/Mvc/RequestHandlerResolver.php in line 83.
Neither me nor anyone else in my company changed something on the Typo3 Website in the past 5 Days.
I've tried to search for Solutions but neither of them helped.
Sadly we have no Backups (This will be Priority 1 after this).
I've also found a Typo3 Website talking about that problem here: https://wiki.typo3.org/Exception/CMS/1205414233
but i dont know where to include the code given by this Site.
Does anyone know what I can do with this Error?
Thanks.
first of all TYPO3 7.6.25 is from 13.03.2018. The last free release is 7.6.32 from 11.12.2018. There are many security updates since your version. If you buy ELTS you can download and install 7.6.41 ELTS (28.01.2020) Maybe this will help with your problem.
Other things you can check: Hosting Provider changes php version or mysql? I really think you should try update to TYPO3 8.7 and test again. Backup your site befor update.
It seems this can have different reasons. In my case (in TYPO3 8.7) the problem was triggered from comments in TypoScript. I've used a (valid!) multi line comment:
plugin.tx_myplugin {
settings {
firstsetting = 1
/*secondsetting = 2
thirdsetting = 3*/
}
}
In the "TypoScript Object Browser" there was a warning, it seems TYPO3 had problems parsing TypoScript due to this comment.

TYPO3 REST Extension setup

I'm trying to setup the REST-Extension v2 in TYPO3 8.7 following this tutorial. I included the 2 templates called Virtual-Object-Page and Virtual-Object-Content in my template. I made a new extension using Extension Builder 8.7 from Github with a simple model. I installed the new extension and made some Instances of my model in the List View on my start page. In the Typoscript of my template I added:
plugin.tx_rest.settings.paths {
1 {
path = me-kinder-child
read = allow
write = allow
}
}
Me is the Vendor, kinder my extension key and child is my model.
When I'm calling http://localhost/rest/ I get The requested URL /rest/ was not found on this server.
What am I missing?
The path in the setup is explained being possible with several options, so perhaps try different configuration, possible is also all.
I don't see a fault in your setup, so the fault might be related to the server-file .htaccess or the extension realurl respectively the combination of both perhaps.
If you try it already with realurl or cooluri then disable that to get it running without first.
The htaccess file you can disable first too and enable it later again to adjust all requirements to each other.
The problem was not about RealURL was missing in any way. I just did not clear a cache that got cleared while installing RealURL. I guess that the "Clear all caches"-button in the Install-Tool would do it too.

Is it possible to publish versions of a page/asset in AEM?

For a regulatory requirement, we are supposed to show the previous versions of a page/asset (state of page as of particular date) at publish instance. So when an end user searches an asset, and if the asset had multiple versions, he should be able to hit any version from the search result.
I managed this to solution from author instance wherein I included the versionId in query param or selector and a custom filter picked this version in url, used version manager to return the respective version of page.
When it comes to publish, from 6.1 AEM has made ACLs stricter in accessing /jcr:system. I tried to publish a revision say /jcr:system/jcr:versionStorage/1f/4f/d1/1f4fd128-b9e3-43cc-9d8a-9335bb34c3ae from activation tree and it didnt publish either.
With this requirement how can we publish versions of a page/asset?

TYPO3 news list PID redirect to other link, with EXT: News System KEY: news VER: 2.2.1

Im running TYPO3 v. 6.1 with FLUID/EXTBASE.
I have setup the News plugin and have added the PID for the news list as ID 4 and it gives me this.
Link 1 working fine but the link "Alle" is not activ, so if I want that to be activ the real link is this Link 2 so my question is.
Where can i tell the TYPO3 setup, this if im going to a PID = 4 (codem.dk/oevelser/) then it need to rederict me to codem.dk/oevelser/itemCat/alle/ so i dont need to make changes in the Hmenu/Tmenu.. can I do this in "Web" -> "List" -> "Domain" or can i do it a better way ?
I suppose you are using the realurl extension on your site to make the URLs pretty. There is a documented feature called "valueDefault" which you may use to set your default category.