have just updated typo3 calendar base extension and suddenly the typo3 backend and frontend displays disappeared and all i see is a blank display. This is the exact error I'm getting
... PHP Fatal error: require_once(): Failed opening required '/var/www/html/typo3conf/ext/cal/res/class.tx_cal_isCalNotAllowedToBeCached.php' (include_path='/var/www/html/typo3/contrib/pear/:.:/usr/share/pear:/usr/share/php') in /var/www/html/typo3temp/Cache/Code/cache_core/ext_localconf_6068a12d352941d6e5ee7dd31447d561068faea3.php on line 3617....
how do I clear this to get my typo3 back? I'm using typo3 6.2.12, my efforts of even deleting the cal extension don't work!
thanks in advance
Open the install tool and clear all caches in the "Important Actions" section. It seems there is some old code from before the update still cached. Note the path of the file doing the include, it is in typo3temp/Cache/Code/.
Related
I tried to upgrade from 10.x to 11.5.8 and nothing was working anymore. If I try to open the url I recieve the following error message:
Fatal error: Declaration of TYPO3\CMS\Extbase\Mvc\Controller\AbstractController::processRequest(TYPO3\CMS\Extbase\Mvc\RequestInterface $request, TYPO3\CMS\Extbase\Mvc\ResponseInterface $response) must be compatible with TYPO3\CMS\Extbase\Mvc\Controller\ControllerInterface::processRequest(TYPO3\CMS\Extbase\Mvc\RequestInterface $request): Psr\Http\Message\ResponseInterface in C:\inetpub\wwwroot\typo3\sysext\extbase\Classes\Mvc\Controller\AbstractController.php on line 243
So the next step was to disable all my extensions.
If I try to open the backend, I recieve the same message as above.
The next step was to use the Install Tool, which was working. But if I try to use some functions like "Upgrade Wizard", "Analyze Database Structure", "
Remove Temporary Assets", ....
But the sys_log and the log files under typo3temp are empty!
And also the firefox degugger is not showing any information.
PHP 7.4.15, no composer installation and chaches all deleted!
What should I do next?
The first error message says that there are Extbase extensions which are not compatible with v11. See https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/11.0/Breaking-92502-MakeExtbaseHandlePSR7ResponsesOnly.html
For the second error I'd recommend to look into the dev console of your browser. There you might see more information about the error when there is nothing in the logs. (Maybe there is an error when writing log?)
The mentioned file "AbstractController.php" exists only in version 10 and was removed afterwards.
So TYPO3 is using some old files, probably from the file-cache.
You wrote that you use an installation without composer-setup. Those installations have the file-cache saved in typo3temp/var/cache. This folder can be deleted completely and will be rebuilt automatically.
Afterwards TYPO3 version 11 should run and the error-message should never be shown again.
Due to my experiences with updating TYPO3 to a new mayor release, i did the following steps.
Renamed fileadmin dir
Deleted all TYPO3 dirs
Installed the new version of TYPO3
Start TYPO3 from scratch with an new database (use the ID and passwort from the final database, use the right sitename)
Rename the fileadmin dir back to fileadmin
Go into LocalConfiguration.php and switch under DB to the original database
(Maybe) enable 'debug' => true, for BE and FE and set 'displayErrors' => 1, under SYS
Try to start the BE, if failed go to the Install tool.
Start Upgrade Wizard under Upgrade
In the Install tool start the Analyze Database Structure, but be carefull. that you dont't delete any database of your extensions, which not installed yet!
Now the BE should work now and you can upgrade your extensions!
Good Look.
I'm currently upgrading an old TYPO3 6.2 Installation to 9.5. I'm also using fluidtypo3 (flux 9.3.2 and fluidpages 5.0.0). There are several pibase Extensions, that I can't get to work. One of them has the following error:
Oops, an error occurred! Code: 20200320122044742c5a45 - {"exception":"TYPO3Fluid\\Fluid\\Core\\ViewHelper\\Exception: No Content Object definition found at TypoScript object path \"tt_content.list.20.edxdownload_pi1\"
Any hints what is causing the error? Did I forget anything to register?
I added the plugin in tt_content.php, registered it in localconf.php
(\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addPItoST43('edx_download','','_pi1','list_type',0);)
and added the config in sys_template.php
(TYPO3\CMS\Core\Utility\ExtensionManagementUtility::addStaticFile('edx_download','Configuration/TypoScript/PluginSettings/', 'Edx Download Settings');)
If I make a new element using the new element wizard, I get the following error in frontend:
Content Element with uid "9887" and type edx_download_pi1 has no rendering definition!
Where do I have to set the rendering definition?
Do pibase extensions still work with TYPO3 9?
Edit:
It's working now. I put the method "addPItoST43" back into "ext_localconf.php" and now the extension is loaded. It says you should put it into "TCA/Overrides/tt_content.php", but that doesn't work for me with TYPO3 9.5.
while installing typo3 I faced some issues and now I'm stuck..
I just get the error page
"Oops, an error occurred!"
What's the best way to find the error?
Things you could do:
open typo3conf/LocalConfiguration.php and set displayErrors to 1 in the SYS section
have a look in the TYPO3 log file (see below)
go to domain.tld/typo3/install or domain.tld/typo3/install.php and check for errors there
Which TYPO3 version do you use? If it's TYPO3 8.7 or higher, you can find the error log in typo3temp/var/logs. In older versions, it's just typo3temp/logs.
I've updated a typo3 website from 4.5 to 6.2.9. Now the issues with old extensions are fixed. But now I'm facing an issue with real url extension [ver.1.12.8]. If it's disabled the front end is rendered with no issues. When the extension is enabled it shows this error
#1294587214: Configuration Error: 404 page "D:/Xampp/htdocs/project125/404-melding.html" could not be found.
Please help...
It appears, that you have the following value in your LocalConfiguration.php
[FE][pageNotFound_handling] = READFILE:D:/Xampp/htdocs/project125/404-melding.html
With this configuration, TYPO3 handles a pageNotFound event by displaying the content of the file configured (in your case D:/Xampp/htdocs/project125/404-melding.html). When the file can not be found, TYPO3 throws an exception with the code #1294587214.
Try to check, if the configured 404 HTML page exists in your filesystem and if not, create it. For further debugging purposes you could also set pageNotFound_handling to "true" or "1" to show an error message instead of an individual 404-page.
Also make sure you clear all caches and also the RealURL encode/decode cache.
I've updated my Typo3 from 4.5.5 to 4.7.0 and I get several deprecated errors:
ERROR: Content Element type "login" has no rendering definition!
call to undefined error in t3lib_div::view_array
fail to include class.t3lib_htmlmail.php
The install tool gives me "typo3/ext/ directory not writable" but I've the correct right. I've even allow all?????
When I select a CType Element in the BE it give me this warning: PHP Warning
PHP Warning: Invalid argument supplied for foreach() in /var/www/typo3_src-4.7.0/t3lib/l10n/parser/class.t3lib_l10n_parser_llphp.php line 95
The solution for 2. is to use the new class t3lib_utility_debug but what is with the other errors?
Edit: 1. http://lists.typo3.org/pipermail/typo3-english/2011-November/078129.html
Edit 2: The solution for the missing class t3lib_htmlmail is to include another class t3lib_mail_message: require_once(PATH_t3lib .'mail/class.t3lib_mail_message.php');
You solved allready: install system extension "felogin"
you solved allready: use t3lib_utility_debug
check where the error is from. Often it is helpfull to search for that file in typo3conf/temp_*.
You could check your filesystem, if your webserver is allowed to write to typo3/ext/. I guess, it is not. But you do not need to. Usually you install extensions to typo3conf/ext/.
Update your language files via the extension manager.
Well, i know it is to late now, but for all others wo think about an update: just activate the deprecation log in the isntall toll and fix that problems first!
Updating from 4.5.X to 4.7.x broke my felogin as well. The reason was that there has been a local extension installation that has been of higher priority than the system one. So if you suffer the same update issue, check for an local installation of felogin in "typo3conf/ext" - and delete it in case it is there. This solved my problem!