I am getting the following error when I log into Magento connect Manager.
Exception caught:
Unknown error (8192): Function eregi() is deprecated in /home/nirmal/public_html/magento/downloader/pearlib/php/PEAR/Registry.php on line 774
The php version I am using is 5.3. Can you help me?
Hmm, this is tricky. This is a so-called E_DEPRECATED notice, pointing out a function call that still works, but will be removed in one of the coming versions of PHP.
You could manually edit the code to fix this, but it seems to be in a core part of Magento or the PEAR client. It is likely to be fixed in a future version of Magento. Turning off error reporting for E_DEPRECATED notices might be justified in this case.
The error_reporting setting for that would be
error_reporting(E_ALL ^ E_DEPRECATED);
This is because eregi() function is deprecated
Warning
This function has been DEPRECATED as
of PHP 5.3.0. Relying on this feature
is highly discouraged.
http://php.net/manual/en/function.ereg.php
Here is a fix of this problem
http://www.devcomments.com/magento-and-deprecated-errors-solved-to290776.htm
Here is also a very similar issue and fix. Take a look here
http://www.magentocommerce.com/boards/viewthread/59208/
The core of this problem is that Magento still doesn't officially support the PHP 5.3 branch as far as I am aware. Since the framework catches even quasi-serious errors and kills execution, you may discover many such bugs.
The easy fix is to use the current 5.2.X version of PHP.
Related
Need help on this problem. I received an error message
Strict Standards: Declaration of JCacheControllerPage::store() should be compatible with JCacheController::store($data, $id, $group = NULL) in Unknown on line 0
but I don't know what caused this problem and how do I resolve it? I'm using joomla 2.5 and still learning how to make these things work.
Thank you in advance
Are you using the latest Joomla 2.5 version? Strict Standards messages are not really errors and you can disable these errors by going to Joomla Global Configuration and set Error Reporting to Basic OR None for live sites and Maximum for sites under constructions.
I am installing SugarCRM Portal on my local host. In installation wizard it says that I must turn on Allow Call Time Pass Reference and I did at php.ini and stopped my apache server. When I started it back again an error occurred saying there was a fatal error.
Here is the error on my logs
"Fatal error: Directive 'allow_call_time_pass_reference' is no longer
available in PHP"
I cannot continue my installation if all settings are all green. This is the only thing that is blocking me. Help Please.
It says in the PHP documentation that this configuration option has been removed from PHP 5.4.0 onwards.
http://php.net/manual/en/ini.core.php
If your php version is above PHP 5.4.0, try downgrading PHP.
I've got it
air4x's comment is correct but not detailed so I am here to give the detailed one.
All you have to do is go to sugarportal_dir/install/ then open checkSystem.php. There is a if statement that looks like this.
if('0' == ini_get('allow_call_time_pass_reference')) {
}
All you have to do is change 0 to 1:
if('1' == ini_get('allow_call_time_pass_reference')) {
}
That's it. Hope that helps others. And thanks for the reply air4x your logic is correct.
Can someone please tell me what the error is in the following script? Was forced to update to php 5.3 instead of 4 and now site is down
<!--form action : <?=//MYSURL_DEV?>properties_features.php-->
You should check your php.ini to see if short tags are enabled. They are often disabled by default. As of PHP 5.4 short tags are always on, but not so on PHP 5.3 and lower.
If you're able, in php.ini you'd enable this with:
short_open_tag = On
Be aware thought that in some hosting environments you actually may be prevented from enabling the use of short tags. And even though 5.4 has them always available, they are generally not recommended because of the very issue that you may have encountered: you may move to another environment that doesn't have them enabled (or even allow it).
The alternative is to use:
<?php echo $var; ?>
More info can be found here: Are PHP short tags acceptable to use?
Good morning.
I've been having this issue for some days and have been lokking for a solution, but I haven't found one yet.
The problem is, I have this Magento store and some grids can be exported to CSV files, while others shows:
Error 503 Service Unavailable
Service Unavailable
Guru Meditation:
XID: 853411302
Varnish cache server
The Magento version I'm using is 1.6.2. I guess the problem is not about PHP code, since the error shown is this generic error, instead of a PHP one (I even found the code used for exporting files and it seems to be ok).
I would like to know why is this error being showed to me.
This is a Varnish Cache related error, I would suggest following the guide below on how to identify what the XID is returning for more insight on how to fix the issue:
https://www.varnish-cache.org/docs/trunk/tutorial/troubleshooting.html#varnish-gives-me-guru-meditation
CodeIgniter 2.0.2 syntax error blank page
i have CodeIgniter 2.0.2 (CI) and its annoing, that when i write lots of code and then just get blank page. Hard to debug without error. i got error reporting E_ALL in php.ini and in config of CI its turned on for every case of enviroment (devel, product) just for sure...
Does anyone knows, where the bug can be? How to turn it on? I think CI is rewriting php.ini error reporting setting somewhere somehow...
Thanks.
The other thing to check in your php.ini are the 'display_errors' and 'display_startup_errors' variables, they should both be set to 1.
In my (little) experience with CI this issue has been the most frustating one. I can understand that no framework is perfect, and any web developer is used to deal with errors (no matter if the framework or the developer is to blame). But that ANY error results in a blank page, with ZERO information in logs, console, whatever, is unacceptable.
If I recall correctly, in my case this was caused by of some combination of CI (ab)using the "silent error" PHP operator (e.g. prepending some db statements with the # operator, a not very clever way of avoiding leaking potentially private information to the end user), together with some bad use of *error_reporting*. See my post here (and see how many answers I got!).
I reported another related CI's idiocyidiosyncrasy related with logging here (again, zero answers)
please check the index.php which locate in the SAME LEVEL of the application folder
inside the index.php the second line
line 2:
ini_set("display_errors", "1"); //ensure it is set to 1
line 23:
define('ENVIRONMENT', 'development'); // development | testing | production
grep your php.ini for the word "error", turn them to On etc...
Do you have output compression turned on in the config? I find that will cause white pages when you have errors.
$config['compress_output'] = FALSE; // Should be set to this when developing.
I had the same problem and eventually fixed it when i noticed I had no 'logs' directory in my application folder