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!
Related
I recently tried to create an FAQ Page with the TYPO3 extension jpfaq.
I did set up everything as it was described in the manual. But for some reason when i preview the page, it shows a bunch of different error. For example:
TYPO3\CMS\Extbase\Persistence\Generic\Storage\Exception\SqlErrorException
Table 'xxx_typo_dev.tx_jpfaq_domain_model_ttcontent' doesn't exist
When I "unbind" the FAQ database I created it shows me the correct FAQ page (just without the questions and answers). So there might be a problem with the database?
Cleared cache. Deleted and installed the extension again. Didn't help.
Sounds like the you need to fix the Database Structure.
Normally the Database Structure is fixed when you install new extensions in the Extensions module.
If you use Composer Mode the installation is done with composer and you need to fix it by hand.
This can be done in the InstallTool / Maintenance Module: Analyze Database Structure.
Or you use the commandline: vendor/helhum/typo3-console/typo3cms database:updateschema (don't forget to use composer require helhum/typo3-console)
I have the following problem:
After trying to change the entry point to my website in the backend of my TYPO3 system (by using the site config), I cannot access neither my backend nor my frontend of the website anymore. Whenever I try to access the site it says "Oops, an error occurred! The parsedUri "https://" appears to be malformed".
What I have tried, is accessing the config.yaml on my webserver to change the baseURL inside of the config, but no matter what I change it to, it doesn't seem to work, as I always get the same error message even uploading the changed config file (what I mean by that is, that the text inside the error message doesn't change to reflect the new url but stays "https://").
I hope that someone who is more experienced in TYPO3 can help me solve this issue. I couldn't really find a working solution after extensively searching so far. Thanks a lot in advance.
After changing the yaml file of the site configuration, you need to clear all caches, either via the install tool (yourdomain.tld/typo3/install.php) or by deleting all files in the directories var/cache/code and var/cache/data.
I was fixing things on a not well-maintained typo3 installation and it resulted in blank pages of frontend, backend and install tool.
I wanted to fix extensions because the powermail-extension was not working anymore even after updating to latest compatible version (tried emptying cache and database compare).
I deactivated an extension "compatibility6" to see if it was interfering and since then all pages have been blank including Install Manager. I reactivated the extension via PackageStates.php, emptied the cache but it did not change anything. I was not able to see any error messages even though I set the parameter in LocalConfiguration.php which made it hard to try to find out what is wrong. Then I restored a backup using vmware. Still, backend and frontend are blank.
I am using Apache and Typo3 7.6.23.
I do not know what might be causing the problem and would like to know what else to look for?
It means you have a PHP error there. The first thing would be to examine logs. If you see anything like "class not found", then your next action would be composer dumpautoload --no-dev.
Long time ago I had an article about blank pages in TYPO3 FE. Not up to date but still can be helpful: https://www.dmitry-dulepov.com/2009/03/blank-empty-page-in-typo3.html
Dmitry already wrote it: you have an error.
In production environment nothing is shown for not revealing any information about your system.
So the only information about the error can be found in the error log of your webserver.
What can you do to get more information about your error?
Enter the install tool and switch to develop mode. This will also enable deprecation logging into a file. Try to avoid filling your system with deprecation warnings by disabling deprecation logging.
Disable the default exceptionhandler by adding this to your typoscript setup:
config.contentObjectExceptionHandler = 0
Now you should see a call stack instead of blank screens.
Be aware that this might reveal confidential information from your system.
because of this you should use a copy of the live-system.
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 am new to TYPO3. I recently upgraded TYPO3 to 6.2 LTS from 4.5 following steps from some websites. Everything seems to be working okay.
I created a test folder and tried to edit the folder. I got INVALID VALUE("254") in Page Type. Here is the image
http://i.stack.imgur.com/h85Hx.png
I looked at logs, developers logs, and searched Google but I did not find anything relevant to the problem. Any idea on where to start?
PS: I didn't have enough reputation to add images directly. So, sorry for the link.
254 is the page type "Folder". It is very strange that this should be illegal. It's working here on a 6.2 installation.
Maybe it's a TypoScript configuration that disallows folders as subpage types at the parent page.
Have you already tried "database compare" function in your install tool? Looks for me like a update problem.