TYPO3核心:异常处理程序(WEB):未捕获的TYPO3异常 [英] TYPO3 Core: Exception handler (WEB): Uncaught TYPO3 Exception

问题描述

我正在TYPO3中的一个网站上工作.我遇到了一些错误，我也不知道该如何解决.

I am working on a website in TYPO3. I got some errors and I don't exactly know how to fix them.

昨天我有以下错误:

The page is not configured! [type=123][]. This means that there is no TypoScript object of type PAGE with typeNum=123 configured. | TYPO3\CMS\Core\Error\Http\ServiceUnavailableException thrown in file /var/www/typo3_src_elts/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php

今天我还有另一个:

Exception while property mapping at property path "": The identity property "blabla2" is no UID. | TYPO3\CMS\Extbase\Property\Exception thrown in file /var/www/typo3_src_elts/typo3/sysext/extbase/Classes/Property/PropertyMapper.php

有人可以告诉我日志文件位于哪个文件夹中，在哪里可以看到错误?

Can someone tell me in which folder the logfiles are located, where I can see the error?

推荐答案

这是两个独立的问题.

如果您使用?type=123呼叫前端，则会发生第一个.错误消息已包含问题，未通过TypoScript配置请求的类型. 某人或某物正在使用此参数调用您的前端，而您的站点不知道该类型.或者您的网站将自己称为这种类型的地方，这将是一个实际的问题.

The first one occurs if you call your frontend with ?type=123. The error message already includes the issue, the requested type is not configured via TypoScript. Either someone or something is calling your frontend with this parameter and your site doesn't know about the type. Or your site calls itself somewhere with this type, which would be an actual issue.

我建议找到谁在呼叫该页面，例如检查Web服务器访问日志中是否包含URL中的参数的请求.检查用户代理以检查它是否可能是某种机器人. 如果您确实要配置类型，请查看官方文档:

I would recommend to find who is calling the page, e.g. check webserver access logs for requests including the argument in the URL. Check the user agent to check if it might be some kind of bot. In case you actually want to configure the type, check the official doc: https://docs.typo3.org/m/typo3/reference-typoscript/10.4/en-us/Setup/Page/Index.html#multiple-pages

第二个应该来自您安装中的扩展.更确切地说，是从扩展中的Extbase前端插件中获得的.好像有人再次用您的标识符"blabla2"呼叫您的前端.对于一个对象，这是无效的.对象始终具有一个整数作为标识符.因此，Extbase无法映射它.

The 2nd one should come from an extension in your installation. To be more precise from an Extbase frontend plugin from within an extension. Looks like someone is again calling your frontend with the identifier "blabla2" for an object, which is invalid. Objects always have an integer as identifier. Therefore Extbase is not able to map that.

这篇关于TYPO3核心:异常处理程序(WEB):未捕获的TYPO3异常的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！