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)
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!
As the title says. I was working on my typo3 site and tried installing the mmc_slideshow extension from the typ03 website. After clicking install an error appeared and now i can no longer access the live site. When I try to look at the /typo3 backend it is just the same error. It looks like the site is wiped. Is there anything I can do to get it back? I was able to see the files by looking into /typo3conf but it doesn't give me any editing options. The only thing i can think of is getting in through the hosting server.
Aside from the editing of typo3conf/PackageStates.php, which Mathias mentioned, you may need cleaning the cache (I don't remember the folder for sure, something like typo3temp/Cache/Code/? In doubt you may delete everything from /typo3temp/.)
Another option could be the Install-Tool where you might be able to disable failing extensions.
I use a PostgreSQL database on my local computer. I always import csv files via right-click to the relevant table and choosing the Import/Export Dialog. However, when I opened the pgadmin last time, there was no import/export option in the options. I do not know what happened to it. I, once, took a backup of files and use this backup file to migrate the database to another version of Postgres. I am not sure but I want to ask might one of the options that I selected or did not select cause this trouble?
I also tried to go in an alternative way by using copy from 'C://path/data.csv method and it did not work. then I tried \copy from 'C://path/data.csv but it did not even recognize the \ symbol and gave an error.
I wonder what happened to Postgres or pgadmin and how can I find a solution to import my data to the Postgres database?
I had the same issue, looked everywhere but nothing came up on WHY this happened or HOW to fix it.
RESOLUTION: I was able to resolve this by downloading the latest version of pgadmin4.
After downloading, the Import/Export dialog reappeared.
Hope this helps you too!
Import/Export Dialog - Resolved
I have two different TYPO3 9.5.20 installations.
The problem is: In one of both I'm not able to download the German language packages, while on the other it works fine. Both seem to have the same configuration and folder structure.
The not-working installation is telling me 1 language pack not available while trying to download for a single extension.
I tried disabling all non-core extensions except for the ones I want to download the language packages, but that didn't help either.
I was able to download translations for the core-extensions, but all others don't seem to work.
Any ideas where I could look for the problem and compare the two installations or what could cause the problem?
The problem was the enabled feauture newTranslationServer in my LocalConfiguration.php.
This caused TYPO3 to use the translationBaseUrl https://localize.typo3.org/xliff/ instead of https://extensions.typo3.org/fileadmin/l10n/ what resulted in a 404 for all non-core extensions.
I don't know how the configuration got there, but it wasn't on purpose so I disabled it. Maybe this can help someone else.
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.