{"push_id":2069429775,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"113943c6d0d29a51ad2d3b13b4850b001fde1829","before":"f0d731dd62d9d6296991a75ac9ca841068039e2d","commits":[{"sha":"113943c6d0d29a51ad2d3b13b4850b001fde1829","author":{"name":"Benni Mack","email":"b109a028781fc6ea1b71e90ced8497151ede1325@typo3.org"},"message":"[BUGFIX] Do not force content_fallback to default page language\n\nIf a page translation is not available, the TypoScript option\n`config.sys_language_mode` has the option\n`content_fallback;listofuids` to define to which other language\ntranslations should be fallen back.\n\nHowever, if NONE of the defined page translations are available,\na fallback to the DEFAULT language is made (because the\nforeach just does not apply) which can not be stopped at all.\n\nTo define an explicit 404 when a translated page NOR its\nfallbacks are available the special keyword \"pageNotFound\" is added,\nwhich can be added to\n`config.sys_language_mode = content_fallback;3,2,pageNotFound`\nand if none of 3,2 are available, a page not found message\nis thrown.\n\nResolves: #82794\nReleases: master, 8.7\nChange-Id: I90af4e9f9685ffc7db8c562207e3df08786c0ca9\nReviewed-on: https://review.typo3.org/54426\nTested-by: TYPO3com <no-reply@typo3.com>\nTested-by: Sascha Rademacher <sascha.rademacher+typo3@gmail.com>\nReviewed-by: Georg Ringer <georg.ringer@gmail.com>\nTested-by: Georg Ringer <georg.ringer@gmail.com>\nReviewed-by: Susanne Moog <susanne.moog@typo3.org>\nTested-by: Susanne Moog <susanne.moog@typo3.org>","distinct":true,"url":"https://api.github.com/repos/TYPO3/TYPO3.CMS/commits/113943c6d0d29a51ad2d3b13b4850b001fde1829"}]}
{"actor":{"display_login":"reviewtypo3org"}}