My TYPO3 has broken after deactivating an extension (direct_email). I can't access my backend anymore and also I cannot deactivate the extension through the Installation tool.
This is the error that I got:
Errors after deactivating an extension sounds strange.
That only should occur if other extension do not have declared dependencies.
Aside from the PackageStates.php you should clean the caches. If you have no access to the Install_Tool (typoe/install) to clear the cache and check for broken extensions, you need to delete all caches in the cache-folders /typoe3temp/var/Cache (or similar, dependening on TYPO3 version)
You might give some more information about your installation (versions, kind of installation (composer), ..)
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 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.
I'm very new to the CMS TYPO3 and I ran into a problem after the successful installation. I cannot access the page, view and list in the navigation. My logs show the error:
Class 'Tools_action_index_7c3e344226a5508b65ddf8993fcb960b3377b0d1'
not found
So I guess I am missing the action_index, but I don't know what I should create. A php file in the root of htdocs?
I guess it could be solved very quickly, but I'm still stuck and I can't find anything online.
Any help would be appreciated. Thanks in advance!
This class name looks like a fluid template cache file which is not generated. Did you check the write permissions for your webserver? Depending on which Version of TYPO3 you have installed, the webserver need write permissions for typo3temp and var folder:
TYPO3 9.x composer install: var/ and public/typo3temp/
TYPO3 9.x classic install: typo3temp/
TYPO3 8.x classic install: typo3temp/
Directory structure
Security Guidlines: File/directory permissions
You can also check the status and potential errors inside the install tool (Admin tools):
TYPO3 9.x: http://your-domain/typo3/ -> Admin tools: Maintenance
TYPO3 8.x: http://your-domain/typo3/install -> Folder Structure
Flush all caches in backend
If write permissions dont help, click the red flush cache button inside TYPO3 backend (right top corner -> flush all caches)
Flush file cache on disk
If this also not helps, delete all files/folders inside:
TYPO3 9.x composer install: var/cache/
TYPO3 9.x classic install: typo3temp/var/cache/
TYPO3 8.x classic install: typo3temp/var/Cache/
Ok, so I finally managed to solve the problem. Thank you Steffen Mächtel for your hints with the write permissions. Thanks to that I realised that I couldn't change the write permissions of my folders (not even with chmod 777).
I am not sure, but I think the problem was that I had XAMPP as a virtual machine running so I couldn't change it. I didn't know there was a difference in XAMPP and XAMPP-VM. I solved my issue by removing XAMPP and do the whole install process using MAMP instead. Using MAMP everything works now. Thanks everyone again for the help.
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!