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.
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 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.
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), ..)
I fumbled around with an ancient T3 installation (tried an upgrade from 4.5 to 6.2) and before the fumbling created a backup from the entire directory on the webserver as well as the database.
Now I tried to re-activate that backup (a.k.a. 4.5). The install tool works fine, DB-Connection seems to be ok, but when I try to access the backend, it tries to access /typo3/sysext/install/Start/Install.php which isn't present at the described location.
I tried to delete all caches, emptied the typo3temp folder - nothing helps. It seems there's something stuck from the upgrade process, but I have no idea where.
Any ideas?
The Problem's solved. T3 6.2 uses the PHP Opcode Cache which can't be reset in the 4.5 install tool. Something must have been stuck there. I wrote a little PHP script that clears the cache and viola, it worked.
opcache_reset();
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.