Strict Standards Pear error with Jobberbase 2.0 - php

Fresh "Jobberbase 2.0" install on shared hosting, support desk is closed for hours, so I'll ask here in hopes of someone knowing what this is, better than I do, which is zero to none.
It's the same bug that's detailed here:
https://github.com/filipcte/jobberbase/issues/11
I tried what their solution was to no avail, as it's vague to me. I tried the same filename from PEAR current, which has a different line just 1 line before the one called into question in my error.
3 Screenshots of what I'm encountering:
http://imgur.com/tgsxVSj,uCWak31,b7ig83S
When I click on any of the 3 submenus this is my error:
Deprecated: Non-static method PEAR::raiseError() should not be called statically, assuming $this from incompatible context in /home/funkysal/public_html/_lib/CacheLite/Lite.php on line 538
I'm at a loss & appreciate any direction I can come by from users here.
Thanks much,
-C

You can fix this by either upgrading to PEAR 1.10.0dev2, which fixes those E_STRICT errors, or by hiding E_STRICT errors:
<?php error_reporting(error_reporting() & ~E_STRICT & ~E_DEPRECATED); ?>

Related

Untrackable deprecation notice

Using
PHP 8.1
Symfony 5.4
Problem
Every symfony command console output is followed by deprecation notice
2022-11-23T22:22:33+01:00 [info] Deprecated: ucfirst(): Passing null to parameter #1 ($string) of type string is deprecated
The problem is I am not using ucfirst anywhere in my project, so it probably is some composer package deprecation. However the deprecation notice does not contain neither the path to a file nor any other clue how it can be found.
How can one track the file / code which triggers this deprecation?
You may want to set error_reporting=E_ALL (not mandatory as you have depreciation notice emitted already) and then log_errors = On and perhaps log_error = syslog and then inspect the log entries in syslog and you should have file and line number which potentially could help you back track the culprit.
Aside from this, it's a depreciation notice and not an error. And since it's not in your code, there's not much you can do beside upgrade your dependencies (incl. Symfony) or disabling E_DEPRECATED notices from being emitted. Again, this is a notice, not an error.

Warning: mysqli::init(): Property access is not allowed yet in [script path]

I have installed a fresh new Typo3 installation.
I have Windows 7 and use Apache 2.4
PHP 5.6.11 with Zend Engine 2.6.0 and with Xdebug v2.3.3.
Typo3 uses their own error handler so it is possible to control the error levels in the configuration file. However the mysqli still throws warnings for mysqli::init() and mysqli::stmt_init(). In both cases the error are
PHP Warning: mysqli::stmt_init(): Property access is not allowed yet in W:\typo3\sysext\core\Classes\Database\DatabaseConnection.php on line 782
PHP Warning: mysqli_init(): Property access is not allowed yet in W:\typo3\sysext\core\Classes\Database\DatabaseConnection.php line 1190
I have tried to read the thread mysqli + xdebug breakpoint after closing statment result in many warnings but it seems the warning is related to some bugs in mysqli. As what I read these bugs should be resolved.
Since these errors comes from the core of Typo3 I think it will be foolish to edit in the DatabaseConnection.php file.
However, I have tested my connection using mysqli::__construct instead of mysqli_init(). mysqli::__construct does not throw any warnings/errors. http://php.net/manual/en/mysqli.construct.php
In typo3conf/LocalConfiguration.php I have set errorHandlerErrors and exceptionalErrors to 30965 instead of 30466 such that Typo3 does not trows an exception for warnings. This only solved the problem for mysqli_init() - not stmt_init().
So what can I do?
The problem is solved by set the error reporting level to E_ALL except E_STRICT in php.ini.
That is because the built in error handler in Typo3 is more sensitive that default error handler.
error_reporting(E_ALL ^ E_STRICT);

Strict Standards: Accessing static property JCache::$_handler as non static

I am having an issue with my business website, and it keeps giving me the following errors on my website and login:
Strict Standards: Accessing static property JCache::$_handler as non static in /home/doveheal/public_html/libraries/joomla/cache/cache.php on line 422
Also on my website is this error:
Strict Standards: Only variables should be assigned by reference in /home/doveheal/public_html/plugins/content/jw_allvideos/jw_allvideos.php on line 42
I have seen many tutorials on how to fix it via changing the strict standard settings in XAMPP, but this does not apply to me as I do not use XAMPP. Truth be told, I did not create the website (someone else did and it was handed to me), and I am really struggling to figure out how to solve this problem.
Any help would be appreciated!
You will on your localhost (Xampp) have access to the php.ini file. Open it and search for:
error_reporting =
There will be a value after the = which you need to change to:
error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT
Once changed, make sure you restart Apache.
This is however somethign you should flag to the developer of jw_allvideos so they can fix it.
Hope this helps

Static Standards error after updating to php 5.4.9

I am getting following errors after updating php to version 5.4
Strict Standards: Non-static method Debugger::invoke() should not be called statically, assuming $this from incompatible context in /usr/share/php/cake/libs/debugger.php on line 575
Strict Standards: Non-static method Debugger::getInstance() should not be called statically, assuming $this from incompatible context in /usr/share/php/cake/libs/debugger.php on line 575
I have already tried following solutions
Error while Disabling error reporting in CakePHP
Cakephp doesn't work after installing php5-curl package (Unable to locate "Cake" folder as I have baked my project)
Wampserver cakephp 1.3 Strict standards error
How to eliminate php5 Strict standards errors?
PHP 5 disable strict standards error
https://stackoverflow.com/questions/11799085/turn-off-php-strict-standards?lq=1 (Was not able to turn off the errors)
Cleared cake cache, web browser cache, cookies and restarted server after each change. Even tried in private browsing and chrome, firefox, ie also.
I believe this is because this app is built on an older version of CakePHP, which may use some deprecated functions.
It'd be awesome if you (or someone else) could upgrade Cake to a new stable branch.
As of now try this in your core.php you could remove the E_STRICT from your error reporting:
i.e go to app/Config/core.php find
Configure::write('Error', array(
'handler' => 'ErrorHandler::handleError',
'level' => E_ALL & ~E_DEPRECATED,
'trace' => true
));
replace it as
Configure::write('Error', array(
'handler' => 'ErrorHandler::handleError',
'level' => E_ALL & ~E_STRICT & ~E_DEPRECATED,
'trace' => true
));
Changing the error_reporting function does work to fix this. However, cakephp seems to set these flags in several places, that's why the solution may not have worked for you (I went through the same)
Do a source-wide search for "error_reporting" and you'll find it used in several files. Add the flag "~E_STRICT" wherever you can. For instance:
error_reporting(E_ALL & ~E_STRICT & ~E_DEPRECATED);
You'll see it in places like /cake/bootstrap.php, /cake/libs/configure.php, /cake/console/cake.php, etc. I just changed them all to exclude E_STRICT and the problem was fixed.

Non-static method utf_normalizer::nfc() should not be called statically

At the moment, I am installing PHPBB 3.0.10 and am having this error:
Strict Standards: Non-static method utf_normalizer::nfc() should not be called statically in C:\xampp\htdocs\PHPBB\includes\utf\utf_tools.php on line 1781
I have tried to find an answer for this on the PHPBB boards but have had no luck. I have a bit of background in PHP but don't understand static function calls from dynamic ones. I am using PHP v5.4.4, Apache 2.4.2 and Xampp 1.8.0, if any of that is of relevance. I am also running this on my localhost, not on a remote server.
To induce this error, all I am doing is installing PHPBB. Once I have inserted the Database settings and the Admin account settings, it comes up with this error and won't allow me to continue. I have no extensions installed (ofcourse).
Also, I have not been able to find the nfc function in the file specified. I am unsure as to whether it's in an include though. I also searched inside all files for "function nfc" (excluding quotation marks), but found nothing, and so am unable to use this: Strict Standards: Non-static method STemplate::assign() should not be called statically
. I am aware that this problem is common, and many people have claimed that a certain fix has worked for them, but I have been unable to apply these fixes because they were for earlier versions of PHPBB (i.e. 1.0.4).
I have been able to install PHPBB on localhost in the past, but not now. I currently have no working PHPBB installation.
Thanks for any help given.
I know this is outdated, however rather than suppressing the issue
If you want to properly fix this at the root of the problem,
Open up includes/utf/utf_tools.php
Go to ~line 1663
Replace
utf_normalizer::nfkc($text);
With
$utf_normalizer = new utf_normalizer();
$utf_normalizer->nfkc($text);
unset($utf_normalizer);
I'm still not sure why this hasn't been fixed in a proper release
go to your /includes folder and open up the startup.php
On line ~22 change the line
error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED);
to
error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT);
This may solve your problem =).
I run into a similar problem today after I updated to 3.0.12 and I think the proper solution is to make static all the functions in utf_normalizer.php instead of making non static all the calls to these functions.
BTW this is how it's done in phpbb 3.1.1

Categories