Actions
Bug #13752
closed
pfSense - Feature #13446: Upgrade PHP from 7.4 to 8.1
Avahi broken on PHP 8.1
Start date:
Due date:
% Done:
100%
Estimated time:
Plus Target Version:
Affected Version:
2.7.0
Affected Plus Version:
23.01
Affected Architecture:
Description
Clea install of 23.01.a.20221213.0600.
Installed avahi from packages.
Click on Services > Avahi
Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/avahi_settings.php:28 Stack trace: #0 {main} thrown in /usr/local/www/avahi_settings.php on line 28 PHP ERROR: Type: 1, File: /usr/local/www/avahi_settings.php, Line: 28, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/avahi_settings.php:28 Stack trace: #0 {main} thrown
Updated by Jim Pingle about 2 years ago
- Project changed from pfSense to pfSense Packages
- Category changed from Web Interface to Avahi
- Parent task set to #13446
- Release Notes deleted (
Default)
Updated by Jim Pingle about 2 years ago
- Subject changed from Avahi configuration page broken to Avahi broken on PHP 8.1
- Affected Version set to 2.7.0
- Affected Plus Version set to 23.01
There is a similar error when trying to run it as well, looking at the code it's the same use of old/deprecated array access that needs updated for PHP 8.1:
PHP Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/pkg/avahi/avahi.inc:118
Stack trace:
#0 /etc/inc/pkg-utils.inc(773) : eval()'d code(1): avahi_sync_config()
#1 /etc/inc/pkg-utils.inc(773): eval()
#2 /etc/inc/pkg-utils.inc(898): eval_once('avahi_sync_conf...')
#3 /etc/rc.packages(76): install_package_xml('Avahi')
#4 {main}
thrown in /usr/local/pkg/avahi/avahi.inc on line 118
Updated by Jim Pingle about 2 years ago
- Status changed from New to Feedback
- Assignee set to Jim Pingle
- % Done changed from 0 to 100
Fix committed, will be in snapshots tomorrow.
https://github.com/pfsense/FreeBSD-ports/commit/1c8ad5a506aa5204833ae71245fe9c61604fb11b
Updated by Jim Pingle about 2 years ago
- Status changed from Feedback to Resolved
Unable to replicate the errors on a current snapshot, so it appears to be fixed.
Actions