These errors happen while I am installing sugarcrm. After finishing installing, its index.php has the same kind of error.
How can I fix it ?
set display_errors = 0;
Determines if the errors will be printed on the webpage as part of the output or if they will remain hidden.
check this out
In index.php add following code (after starting tag of PHP)
error_reporting(0);
And Delete cache files.
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)
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 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.
I am using the latest commercial version of SugarCRM, with 7.2.1 in Ubuntu 14.04.
I have logged-in to the sugar and it shows Endless 'Loading...' message. And there is one Fatal Error in my console i.e., TypeError: error.payload is undefined at cache/include/javascript/sugar_sidecar.min.js?v=v05JhcpoUqgUDSTVs1g86g on line 599"
I've seen this endless 'Loading...' message appear when some of the file & folder permissions are incorrectly set. The article here has resolved it for me: http://support.sugarcrm.com/04_Find_Answers/02KB/02Administration/100Install/Required_File_System_Permissions_on_Linux/
Ben.
Endless loading can be caused by a number of things, probably all of them JavaScript issues. The last few I encountered had to do with accessing the cached javascript files. Make sure you have mod_rewrite enabled if you're using Apache, and that .htaccess has the RewriteBase setting correctly pointing to the site. Also check config.php that site_url is correct.
The SugarCRM PHP code is horrendous and generates loads of errors (warnings/notices/etc.)
I would add the following, either in your Apache settings or the .htaccess file in the root directory of SugarCRM.
# Avoid all those strict warnings
php_value error_reporting 0
This technically turns off all the warnings and notices, some of which would be transformed to errors as your question seems to show.
For some reason one installation of Moodle 1.9.3+ has a problem that file.php returns a blank 0 byte file sometimes, even the apache log shows 0 bytes were returned. Another moodle installation works OK with the same htm files.
What could be causing this? Problematic files are just usual htm files - bug occurs with links like this:
http://server/file.php/164/moddata/scorm/4/data/msg.htm
(The problematic moodle was upgraded from 1.8 version earlier)
A completely blank response may indicate a PHP error; check the PHP error log.
I've had this with a recent XAMP install, it did it whenever a file was saved as UTF8 (which my Visual Studio was doing automatically). Worked on every install apart from my test XAMP box though.
I had some problems with loading binary files with file.php, I think it showed up incorrectly as being 0 bytes (but I'm not sure).
Turned out to be an extra new line character in the beginning of the jpg-files,
the reason was a extra new line in the config.php file after the finishing ?>
I'm not a PHP-programmer but I've seen suggestions to remove the ending ?> in php-only files to minimize this kind of problem.
Hope it helps.
Johan Carlsson
Deactivate all filtes of your moodle system and test again.