Re: [Refdb-users] php webinterface: php8: Uncaught TypeError:

[FreeBSD U. <fr...@wa...>]

On Sun, 13 Feb 2022 18:04:54 +0100
Markus Hoenicka <mar...@mh...> wrote:

> Hi,
> 
> I'm not running the PHP interface myself, so I'm sorry that it took a 
> while to respond. I've set up my FreeBSD box with Apache 2.4, PHP 8.0 
> and the required PHP extensions (session, dom, xml, xsl). PHP does not 
> complain about a TypeError when starting the web interface. Retrieving 
> an existing test dataset works as well. So I cannot reproduce the 
> problem here. How exactly did you trigger the problem?
> 
> regards,
> Markus
> 
> Am 2022-01-30 16:26, schrieb FreeBSD User:
> > Hello folks,
> > 
> > despite the fact that refDB is pretty inactive, it is still in use on
> > several private
> > projects and internal installations. The base OS is always FreeBSD
> > (I'm officially the
> > FreeBSD mainatiner so far).
> > 
> > Sources: most recent copy of the subversion repo provided by source 
> > forge.
> > 
> > Since FreeBSD ports now switched from php 7.4 to 8.0 as the default,
> > the php-driven
> > webinterface is broken and it seems this error is very common in the
> > group of those
> > switching from php 7.4 to 8.0. The error is triggered by
> > 
> > phpweb/idex.php.in
> > 
> > The apache's log reports:
> > 
> > [..]
> >  PHP Fatal error:  Uncaught TypeError: Cannot access offset of type
> > string on string in
> >  /usr/local/share/refdb/www/index.php:900\nStack trace:\n#0 {main}\n  
> > thrown in
> >  /usr/local/share/refdb/www/index.php on line 900, referer:
> >  https://my-host.local/refdb/index.php?thisPage=Search%20indices
> > 
> > $defaultValue seems to be treated as STRING but should be ARRAY
> > 
> > How can this be solved?
> > 
> > Kind regards,
> > 
> > Oliver
> > 
> > 
> > _______________________________________________
> > Refdb-users mailing list
> > Ref...@li...
> > https://lists.sourceforge.net/lists/listinfo/refdb-users  
> 

Hello list,

in the meanwhile other issues with our setup and the migration of PHP from 7.4 towards
8.0 occured. I guess the issue could be triggered due to a rogue php port, officially
php80 incorporates now a bunch of modules formerly realized as separate ports/modules.
I'll check and I'll report back as soon as possible.

Kind regards,

oh