当流畅页面导致后端和前端出现错误时,如何获得对TYPO3后端的访问权? [英] How can I get back access to the backend of TYPO3 when fluidpages are causing an error on backend and frontend?

查看:115
本文介绍了当流畅页面导致后端和前端出现错误时,如何获得对TYPO3后端的访问权?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我必须在Typo3页面上工作,不得不说,关于TYPO3,我还是一开始.

I got to work on a Typo3 page and I have to say I'm at the very beginning if it comes to TYPO3.

因此,我想修复一个错误,并将插件"fluidpages"从4.1.0版(我想)更新为4.3版.这导致糟糕,发生了错误!"在后端和前端,所以我没有从那一侧访问.我仍然有该网站的FTP登录名. TYPO3的版本是8.7.18.

So I wanted to fix a bug and updated the plugin "fluidpages" from version 4.1.0 (I guess) to 4.3. That cause the "Oops, an error occurred!" in the backend and frontend, so I dont have access from that side. I still have the FTP login for the website. The version of TYPO3 is 8.7.18.

我得到的错误代码是那个:

The errorcode I get is that one:

无法分析课程:
可能未加载"FluidTYPO3 \ Flux \ Configuration \ ConfigurationManager" 或没有自动装带器?
类FluidTYPO3 \ Flux \ Configuration \ ConfigurationManager不存在

Could not analyse class:
"FluidTYPO3\Flux\Configuration\ConfigurationManager" maybe not loaded or no autoloader?
Class FluidTYPO3\Flux\Configuration\ConfigurationManager does not exist

那么有人知道我需要做什么吗?
从我的研究中,我认为我需要更新另一个插件以使其恢复工作?我可以仅通过通过FTP上传它们来更新它们吗?

So does anyone know what I need to do?
From my research I think I need to update another plugins to make it back to work? And can I update them just by uploading them through FTP?

提前谢谢!

在尝试运行旧版本的插件后,我从日志文件中获取了此错误代码:

After I tried to get the old version of the plugin running, I'm getting this error code from the log file:

2020年2月17日星期一22:59:56 +0100 [ALERT] request ="fec23f8baf6dc" component ="TYPO3.CMS.Frontend.ContentObject.Exception.ProductionExceptionHandler":糟糕,发生了错误!代码:2020021722595594039a4d-{"exception":"TYPO3 \ CMS \ Extbase \ Mvc \ Exception:无法确定扩展名\" Flux \和插件\" Page \的默认控制器.请检查TYPO3 \ CMS \ Extbase ext_localconf.php中的\ Utility \ ExtensionUtility :: configurePlugin().

Mon, 17 Feb 2020 22:59:56 +0100 [ALERT] request="fec23f8baf6dc" component="TYPO3.CMS.Frontend.ContentObject.Exception.ProductionExceptionHandler": Oops, an error occurred! Code: 2020021722595594039a4d - {"exception":"TYPO3\CMS\Extbase\Mvc\Exception: The default controller for extension \"Flux\" and plugin \"Page\" can not be determined. Please check for TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php.

推荐答案

您可以输入安装工具 .php"rel =" nofollow noreferrer> https://example.org/typo3/install.php 并从检查损坏的扩展名开始.如果那没有产生问题的扩展名,您可以随时手动更改

You can enter the Install Tool via https://example.org/typo3/install.php and start with Check for broken extensions. If that doesn't yield the extension in question, you can always manually change the PackageStates.php file and remove the extension you want to unload. Afterwards you should flush all caches through the Install Tool.

从长远来看,您应该考虑以下几点:

In the long term you should consider a few things:

  1. 使用与您的生产环境相似的本地开发环境.在部署之前,您可以在此处安全地执行所有步骤,而没有任何风险.
  2. 使用允许回滚的部署策略/工具.如果所有其他检查均失败,这使您可以快速恢复到实例的工作版本.一个简单而灵活的解决方案是 Deployer ,但是您将需要SSH.
  1. Use a local development environment which mirrors your production environment. You can safely perform all steps without any risk here before deploying.
  2. Use a deployment strategy/tool which allows for rollbacks. This allows you to quickly revert to a working version of your instance in case all other checks have failed. A simple but flexible solution is Deployer, you'll need SSH for this though.

这篇关于当流畅页面导致后端和前端出现错误时,如何获得对TYPO3后端的访问权?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆