joomla warning message - joomla

i get this message on my local host running joomla:
Warning: Parameter 1 to modMainMenuHelper::buildXML() expected to be a reference, value given in C:\xampp\htdocs\libraries\joomla\cache\handler\callback.php on line 99
what should i do?

This forum post contains the answer, it seems to be a problem with PHP 5.3. Note that Joomla! doesn't officially support 5.3 yet.

Related

ErrorException - Trying to access array offset on value of type null in ServiceProvider.php line 84 in Lumen

I am new to Lumen so I just downloaded and installed a fresh lumen setup but unfortunately as soon as I hit postman it sends me above error. I have read many posts all says to use isset() i did so but still error persists therefore i request to help me.
Composer update also does not work.
Thanks!
It seems to be an issue between your version of PHP and Lumen 5.*
I found something here https://github.com/DarkaOnLine/SwaggerLume/issues/82
This worked for me
// in bootstrap/app.php
$app->configure('view');

Laravel 5.2 view in register a provider

i have installed the chat package:
https://github.com/dazzz1er/confer
Unfortunately i get an error when i try to publish it. Here is the error:
[Symfony\Component\Debug\Exception\FatalErrorException]
Call to undefined method Illuminate\Support\Facades\View::composer()
Thanks !
As correctly pointed out by #curious_coder confer is not compatible with Laravel 5.2 yet. Please keep an on the open Laravel 5.2 issue on Github and/or ask the author of this package for updates.

SugarCRM portal installation Allow Call Time Pass Reference

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.

My website is throwing "PHP Fatal error: Call to undefined method CI_Lang::lang()"

I created a website using CodeIgniter Framework 2.1.0 that was originally working well. Yesterday, I integrated this i18n code into the site for multi-language support.
Now, when I upload my site to cpanel and open it, I get this error in my log file:
[21-Nov-2011 10:19:04] PHP Fatal error: Call to undefined method CI_Lang::lang() in XXXX
However, the website is working well on my localhost server (xampp for Windows). What's wrong?
See the thread attached to the library: http://web.archive.org/web/20120112092127/http://codeigniter.com/forums/viewthread/179036. In the first post is attached a modified library that claims to alleviate the buggyness of the original.
There is also a post on the first page there referencing an error similar to yours:
After copying the files as described in the article I get the
following error: Fatal error: Call to undefined method
CI_Lang::CI_Lang() in
/www/websites/audio-machinery/application/core/MY_Lang.php on line 32
Though he seems to be calling CI_Lang, not Lang. His solution appears to have been to use the code attached to the forum thread.
Also, cpanel is a control panel for hosting, not a hosting provider. But your hosting provider may be causing issues (e.g. if using older versions of PHP which do not work with newer version of CI. Often hosting providers will give you the ability to choose which version of PHP you are using--usually found in cPanel).
have you uploaded ALL the new files to your live server? that error implies that the code is not found or available to the script.
I came accross the same problem.... it was working fine on localhost but when loaded on live server it gives me undefined error... the problem appears becuase I created file with name My_Lang.php and My_Config.php as on live server it is case sensitive.... so I changed it to MY_Config.php and MY_Lang.php .... it works fine now.... Hope it will work for you too

Error when logging to Magento connect manager

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.

Resources