I have a plain naked TYPO3 8 lts installation.
But I cant login with the backend user.
Install Tool works fine
When I create a new BE user in install tool it does not work as well ...
any ideas?
Check in Localconfiguration the [BE][loginSecurityLevel] and change it to normal if it is rsa
For me the solution was deleting the cookies from the browser, then login form works good.
I ran to a problem where I couldn't login to backend, even if I had [BE][loginSecurityLevel] set to normal. Nether did it work on a unix system or windows. The reason I found out was, because the extension 'sv' was disabled (not in PackageStates.php array).
So I went to PackageStates.php and added following to the array:
'sv' => [
'packagePath' => 'typo3/sysext/sv/',
],
Before that happened, I downgraded TYPO3 from 9 to 8. I was able to log in first, but not the next day, after the first logout.
This extension contains core default services.
Use the Debugger for your browser, e.g. Firefox Developer, and check if an error is given there.
Loading failed for the <script> with source “http://www.my-typo3-website.de/typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-3.2.1.js”.
If you copy and past the above url into a web browser, you will see this outpu:
The requested URL /typo3/sysext/core/Resources/Public/JavaScript/Contrib/jquery/jquery-3.js was not found on this server.
The file name jquery-3.2.1.js has been abbreviated into jquery-3.js!
It can happen that the jquery used by the login form is not included as needed. This can happend by a Rewrite rule in the .htaccess file which transforms the filename jquery-3.2.1.js into a smaller name jquery-3.js which will not be found, because it simply does not exist on the file system.
At least you should try out the original .htaccess file named "_.htaccess" which is shipped with TYPO3.
Related
I am starting the process of updating TYPO3 to higher versions (from the base 6.2.X version). The process of updating to version 7.6.X was ok. Being logged in 6.2 version, I switched to version 7.6 and updated elements in InstalTool, plugins etc. The problem appears when I log out. After entering my login address, I have a blank page - white page without any code. I can log into InstallTool but unfortunately not to BE.
The [FE] page works fine after the update. Any ideas what went wrong or where is the problem?
first: blank page normally means: there is an error but all error information was disabled.
If you just changed the source it might be a mismatch between cache and source: clear all caches in Install Tool.
Also your first step should be look into the server log.
If that does not give enough hints enable all debugging and error information in the Install Tool.
If that still gives no clue: disable all extensions (remove from PackageStates.php and don't forget to clear caches afterwards, maybe manually too)
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 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 developed my TYPO3-Project using a local Vagrant-Machine. Now I bought some Webspace and wanted to migrate it there but I keep getting Errors.
Whenever I try to call the URL, TYPO3 is giving me the "Ops, an error occurred!".
I can, however go to the back-end and install tool and everything looks fine there! All the pages with all their content are editable.
Now for the weird part:
Whenever I try to open a Sub-Page from the Backend, It wants to load it with the base-url of my Dev-Server. I migrated the Database correctly and Installed the TYPO3-Installation accordingly.
So basically this is whats going on:
My development enviroment has its own Database and is working perfectly fine
I exported the Database via terminal and imported it via PHPMyAdmin to the new Hoster
I set up my TYPO3 Project and Changed the Localconfiguration.php
I added the new URL to the TYPO3 Project
--> Everytime I open a link I either geht the Blank Page with the "Oops, an error occurred! Code: 20171002194119799d9c1b" or it tries to open the wrong URL.
I used:
Homestead as my Vagrant Box
Composer to install TYPO3 and the extensions
Realurl (latest Version)
TYPO3 8.7.7
My RealUrl setup in my page.config looks like this:
absRefPrefix = /
tx_realurl_enable = 0
linkVars = L(0-3)
index_enable = 1
index_externals = 1
Thanks in advance! I know this is quite something to read but I've struggled for the last 5 hours with this problem and I don't know where to ask but here.
Did you changed the domainrecord?
Open the rootpage in list mode and modify (or add) the domain record to match the current domain.
I am using CKeditor via cdn //cdn.ckeditor.com/4.5.8/full/ckeditor.js.
I wish to enable a preset plugin and do not know how to go about it. i need clear code example.
I have seen this tutorial on using the cdn but it talks about local plugins.
Code snippet is one of the plugins I want to enable.
Working locally with CKeditor in laravel 5.2 is a lot of headache. I keep have this error SyntaxError: illegal character when I inmport my javascript files. My laravel view uses blade template engine. I do not have this issues with CDN imports.
I resolved the issue after many days. all the javascript(not only Ckeditor or Tinymce) files I imported in laravel always gave the syntaxError: illegal character like this
I notices that in every response a header information was automatically pasted as well as a funny character. I solved this using two major steps.
I opened all the javascript files using notepad++ and deleted the first line (usually comments) using backspace and type it back manually, then saved the files.
I realized the header info HTTP/1.1 200 OK was some how related to the server configuration. I switched form using the in-built server php artisan serve to virtual host on xampp. And everything works well.
NB: This problem has nothing to do with Laravel 5.x. I personally think that this problems arise due to the copying and pasting, and downloading of files from the server.
To benefit from the advanced features of a full flesh server, I decided to use virtual host in xampp for development.
I am very happy. Hope it helps!