You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[root@presto:/usr/files/install] php -v
PHP 8.2.22 (cli) (built: Jul 30 2024 11:47:12) (NTS gcc x86_64)
Copyright (c) The PHP Group
Zend Engine v4.2.22, Copyright (c) Zend Technologies
with Zend OPcache v8.2.22, Copyright (c), by Zend Technologies
FastCGI sent in stderr: "PHP message: PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /opt/rh/httpd24/root/var/www/html/xataface-3.0.3/Dataface/SkinTool.php on line 361" while reading response header from upstream: "fastcgi://unix:/var/run/php-fpm/php-fpm.sock:",
FastCGI sent in stderr: "; PHP message: PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /opt/rh/httpd24/root/var/www/html/xataface-3.0.3/Dataface/SkinTool.php on line 361; PHP message: PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /opt/rh/httpd24/root/var/www/html/xataface-3.0.3/Dataface/SkinTool.php on line 361;
PHP message: PHP Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /opt/rh/httpd24/root/var/www/html/xataface-3.0.3/Dataface/Application.php on line 3053; PHP message: PHP Deprecated: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in /opt/rh/httpd24/root/var/www/html/xataface-3.0.3/Dataface/SkinTool.php on line 361" while reading upstream, request: "GET /instdb/index.php?--msg=You+are+logged+in HTTP/2.0", upstream: "fastcgi://unix:/var/run/php-fpm/php-fpm.sock:"
commit: d183f7b
PHP Version: 8.1.14
PHP Server API: FPM/FastCGI
From the PHP error log:
PHP Fatal error: Array and string offset access syntax with curly braces is no longer supported in /var/www/html/xataface/installer.php on line 200
I'm not sure how deep this goes. This seems similar to an error in issue #121
The text was updated successfully, but these errors were encountered: