I have made a contact form but upon submitting it I get the error: Oops, an error occurred! Code: 201905310232036dfcc153.
I would like to get more information so I can start debugging. So my question is: How do I enable error reporting in TYPO3?
You have to add this line in your TypoScript
config.contentObjectExceptionHandler = 0
After setting to 0, you will see detailed errors in frontend when an exception
is thrown.
To reset it, simply delete the lin or set to 1.
here is a blog post from me about it (in German): https://www.naderio.de/oops-an-error-occurred-komplette-fehlermeldung-anzeigen/
In the directory typo3temp/var/logs/ there should be a file named typo3_somehash.log. Search this file for the error code.
Go to Install Tool and configure SYS|displayErrors = 1
This enables the debug exception handler and you will get a stacktrace instead oops an error occurred.
You can also write it directly in your typo3conf/AdditionalConfiguration.php or typo3conf/LocalConfiguration.php:
$GLOBALS['TYPO3_CONF_VARS'][SYS]['displayErrors'] = 1;
See also: https://docs.typo3.org/m/typo3/reference-coreapi/master/en-us/ApiOverview/ErrorAndExceptionHandling/Configuration/Index.html
Related
PHP Fatal error: Uncaught Exception: User Error: Some transactions have not been committed or rolled back in /var/www/html/vype/vendor/magento/framework/DB/Adapter/Pdo/Mysql.php on line 3981 in /var/www/html/vype/vendor/magento/framework/App/ErrorHandler.php:61
There are two ways to figure out the cause:
check your log file to see the real error
change your magento to developer mode and enable debugging.
Add this to your index.php and pub/index.php
ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(E_ALL);
Then try to reproduce the error again and you should see more information now.
For example I got this message:
TypeError: Argument 1 passed to
Amasty\AdminActionsLog\Observer\HandleModelSaveBefore::prepareProductOptionsDataAsArray()
must be of the type array, null given
So for me the third party extension Amasty\AdminActionsLog caused the bug.
I'm trying to create a webpage using TYPO3 8.7, but when i go to Localhost/index.php it says "Oops an error has occured".
The only way i can see my webpage, is through the TYPO3 backend login apperently.
This is the error that it logs in the backend of TYPO3:
>
Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to undefined >function TYPO3\CMS\IndexedSearch\mb_strcut() | Error thrown in file >/var/www/html/typo3_src-8.7.0/typo3/sysext/indexed_search/Classes/Indexer.php in >line 1314. Requested URL: Localhost/index.php
And my line 1314 is this:
$bodyDescription = mb_strcut($bodyDescription, 0, $maxL, 'utf-8');
I'm very new to this. So far i've been able to sort all bugs with the help from these forums and others, but unfortunately I can't find any solution to this one.
Any help is greatly appreciated.
Let me know if i need to provide some additionel information.
This error means that mbstring php extension is not enabled. You should install it, if you have Ubuntu you should execute
sudo apt-get install php-mbstring
Read more about installation of this PHP extension here
I'm completely new to ipython/ jupyter, I literally just typed in me first example and went to save it. I'm not getting the error above?
Error: Load failed, save is disabled
Also I don't know if it is related but I can't left click into cells? I have to right click and then press escape (very annoying).
Thanks
Open up the Javascript developer console and read the error msg.
In my case it looked like:
Failed to load resource: the server responded with a status of 404 (Not Found)
main.min.js:12623 Object
main.min.js:12625 API request failed (404): No such file or directory: code/pcc/Prototype%%20Pattern.ipynb
main.min.js:26690 Error stack trace while loading notebook was:
main.min.js:26691 XhrError: No such file or directory: code/pcc/Prototype%%20Pattern.ipynb
at wrap_ajax_error (http://localhost:8888/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:12671:29)
at Object.settings.error (http://localhost:8888/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:12692:24)
at l (http://localhost:8888/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:89:24882)
at Object.c.fireWith (http://localhost:8888/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:89:25702)
at k (http://localhost:8888/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:91:5373)
at XMLHttpRequest.<anonymous> (http://localhost:8888/static/notebook/js/main.min.js?v=40e10638fcf65fc1c057bff31d165e9d:91:9152)
main.min.js:12030 Loaded extension: widgets/notebook/js/extension
If Install4J could not delete a file, a message is shown which says:
com.install4j...DeleteFileAction failed
Is there any way to show the path to the file which could not be deleted in the error message? Like a variable which i can use in the custom error description?
Thanks!
The detailed error messages are in the installation log file (.install4j/installation.log).
I am setting up a web portal using TYPO3 version 7.2. I successfully installed TYPO3 following this article on a Red Hat 4.8.2-16 machine. Everything worked fine and I created some pages until for some reason the pagetree didn't show any content any more. So now the backend looks like this http://goo.gl/3p0uQn
My browsers debug console only returns this error:
TypeError: TYPO3ViewportInstance.DebugConsole is null backend.php:79:5
but I have no idea if this is related to the empty pagetree.
This occurs on Firefox, Chrome and IE, so I guess it has nothing to do with the browser.
Also, I am logged in as an admin so it should not be due to wrong access rights.
Does anybody know what's going on there?
UPDATE:
The TYPO3 Log gives me some PHP Warnings
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Http/AjaxRequestHandler.php line 255
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Http/AjaxRequestHandler.php line 250
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Core/Bootstrap.php line 1193
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Authentication/AbstractUserAuthentication.php line 439
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Authentication/AbstractUserAuthentication.php line 438
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Authentication/AbstractUserAuthentication.php line 425
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Authentication/AbstractUserAuthentication.php line 424
UPDATE 2
Meanwhile I installed 7.2 completely fresh (even with a new database) and I still get an empty pagetree. I also tried 6.2 LTS, but also here, no pagetree. I'm beginning to think that there is a problem with my PHP settings. Im using PHP 5.6.9 and MariaDB 10.0.19.
Try tu put that on your php.ini :
always_populate_raw_post_data = -1
It worked for me.
Have a nice day.
Raf
You have a PHP error somewhere. Please check your webserver log or php log for error messages. You can also show the error messages by choosing the development preset in the Install Tool or by setting the context environment variable to Development.
Make sure to clear the cache via Install Tool at least once (Important Actions).