I have upgraded a TYPO3 installation from 11.2.0 to the latest version of today 11.5.0.
After changing my symlinks to the new TYPO3 source files, cleaning all caches, performing all upgrade wizards successfully and without errors, I get 2 new error messages that I haven't seen in previous TYPO3 installations. One in the backend and one in the frontend.
Frontend:
503 - Resource paths must start with "EXT:" and must reference Resources/Public
and in the Backend:
503 - TYPO3.CMS.Form.mixins.formElementMixins.FormElementMixin does not exist within the configuration
I am currently finding out the source of the problem. Since Google has no content about these new issues, I thought it would be a good idea to create this thread.
Does anyone have similar problems upgrading to TYPO3 11.5.0?
I found the answer to the frontend error message Resource paths must start with "EXT:" and must reference Resources/Public myself after looking deeper into the error messages.
I included a SASS file for the bootstrap_package like this in my setup:
page{
includeCSS{
custom = EXT:my_package/Resources/Private/Scss/style.scss
}
}
After I changed "Private" to "Public", the error message disappeared.
page{
includeCSS{
custom = EXT:my_package/Resources/Public/Scss/style.scss
}
}
Conclusion: Apparently TYPO3 now makes sure that your resource paths are named the right way and do NOT point to any other directory.
Related
I am setting up a new TYPO3 Project for my company, this project is based on a previously existing Project, as the customer asked us to take it over. So I started with my company's kickstarter to create an empty but working Project. I then started adding the "old" content as well as the extensions used. Here I came across a problem: I added the news extension by Georg Ringer via composer and the frontend of the website showed the following Error:
(1/1) #1476045117 TYPO3\CMS\Extbase\Persistence\Generic\Exception\InvalidClassException
Could not find class definition for name "GeorgRinger\News\Domain\Model\DateTime
This could be caused by a mis-spelling of the class name in the class definition.
I found nothing about this online, checked my entire \ext-folder and didn't find anything related to this. I un- and reinstalled the news extension via composer but that didn't solve the problem either. I also have an issue, where I can't use the backend or the command line to flush my caches, so naturally I deleted the var\cache-folder and upon reloading my frontend I was prompted with another Error:
(1/1) #1580056272 TYPO3\CMS\Extbase\Persistence\Generic\Mapper\Exception\NonExistentPropertyException
The type of property GeorgRinger\News\Domain\Model\NewsDefault::eventStart could not be identified, as property eventStart is unknown to the TYPO3\CMS\Extbase\Reflection\ClassSchema instance of class GeorgRinger\News\Domain\Model\NewsDefault. Please make sure said property exists and that you cleared all caches to trigger a new build of said TYPO3\CMS\Extbase\Reflection\ClassSchema instance
I can still access the install tool as well as the backend. Clearing the cache doesn't change anything and my colleagues advised me to ask the TYPO3 community. This Project runs on TYPO3 version 10.4.12. Any and all help is appreciated, thank you. I am still very new to TYPO3, so please bare with me.
It turns out that there were two rogue DateTime's hiding in one of the non-composer extensions that were missing the \ before them. I also had to add to my ext_emconf.php the following:
'suggests' => [
'news' => '7.3.0-0.0.0',
],
Which also fixed the issue of me not being able to clear my cache, and upon reloading my frontend I saw content again.
Thank you everyone on here and Slack for the help!
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.
I'm currently running TYPO3 version 8.7.18 and running a site_package that was made by using the site package builder: link
Whenever I try to add a form by using the default backend forms module I get the default message Oops, an error occurred! along with that the following error
TYPO3\CMS\Form\Domain\Configuration\FormDefinition\Converters\AddHmacDataConverter not found
Searching for the issue I get several hits on the Gitlab but these do not provide any solution.
Along with this setup, I've added the forms module as a static include in my top-level template.
do you have a composer installation or an extension manager build up?
If a class is not found you may need to rebuild the autoloader information.
My error turned out to be caused by a corrupt installation. I've had to upload the file AddHmacDataConverter.php in the following path /public_html/typo3/sysext/form/Classes/Domain/Configuration/FormDefinition/Converters. A very weird error indeed.
For those that came here with the same error, make sure to check that folder. Apart from that add the news as a static inclusion in your top domain. You could also follow #Bernd Wilke's idea which s to disable the extension, clear all system caches (and additionally remove typo3/temp/autoload and then active the extension again.
I've migrated from typo3 4.1 to 4.5 LTS now I got this error.
The page is not configured! [type= 0][]
I've checked DB analyser and fixed the table issues any ideas. Please revert
Apparently TYPO3 can't find TypoScript use Web > Template tool and check if record exists, also if it includes TS from external files, make sure the files exists.
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.