Errorlog popup window empty on PHP8.3

[@rjen]

Forum: SMF2.1.4
Various mods

Just switched from PHP8.2 tot PHP8.3

Now I noticed that clicking to a file from the error log, the resulting popup window is not showing any code on PHP8.3. Switch back to PHP8.2 and it worsk as it always has...

Is this a known issue with PHP8.3 on SMF2.1.4?

PHP 8.2:
You cannot view this attachment.

PHP 8.3:
You cannot view this attachment.

[Kindred]

2.1.4 definitely does not support php 8.3

[@rjen]

2.1.4 definitely does not support php 8.3

Are you really sure about that?
If so, this page is definately misleading...

https://download.simplemachines.org/requirements.php
You cannot view this attachment.

Mind you, I double checked before switching, and so far this is the only strange thing I am seeing...

[Kindred]

That page is incorrect afaik...   I know that 8.3 will mostly run but will generate errors - as you have seen - last I heard we've did but claim support of 8.3 until 2.1.5 comes out

[live627]

If this is a semantics problem, press one. If your error has been resolved, press two. For a continued runaround, disregard this post.

Any further errors logged?  Be sure to check the PHP error log, too.

[@rjen]

Checking error logs: there are NO php 8.3 related errors. Not on the SMF logs and not in the server logs.

I can switch back to 8.2 to resolve my 'issue', but that is not the point.

See my question;

Is this a known issue with PHP8.3 on SMF2.1.4?

[Aleksi "Lex" Kilpinen]

Logically, I'd think if it is caused by the PHP version change, there should be an error logged server side.
That said, there may be small issues with PHP 8.3, but mostly SMF should be fine - I'm not sure if this is a known issue or not though.

[shawnb61]

No, this was not a known error, but...

Yes, it's easily reproduced on PHP 8.3, in SMF 2.1 & 3.0.  PHP 8.2 is fine.

Logged:
https://github.com/SimpleMachines/SMF/issues/8307

I run PHP 8.3 in my test environments with no issues.  Hadn't noticed this before.  There is a known session management issue with PHP 8.3 on SMF 2.1.4, that for some reason has not affected me yet (https://github.com/SimpleMachines/SMF/issues/7793).  But I don't run 8.3 on my prod 2.1 instances due to this known error.

[@rjen]

Okay, thanks.

Just curious: is 2.1.4 officially supporting php 8.3 or not?

[shawnb61]

For official support, I refer to the requirements page, which says yes, 8.3 is supported - as you pointed out.

The two known issues above, 7793 & 8307, only impact the admin.  There was a BBC issue specific to syntax highlighting also.

[@rjen]

Thanks, good to have that cleared up.

I was a bit puzzled that the Lead support specialist stated initially that php8.3 was not supported yet ..

[Kindred]

I was under the impression that it was not... 😜 because there ARE known issues

[MobileCS]

I run PHP 8.3 in my test environments with no issues.  Hadn't noticed this before.  There is a known session management issue with PHP 8.3 on SMF 2.1.4, that for some reason has not affected me yet (https://github.com/SimpleMachines/SMF/issues/7793).  But I don't run 8.3 on my prod 2.1 instances due to this known error.

That session_set_save_handler() issue is an easy fix though. I had to update that code in my personal project (non-forum), and you just need to create a new class that implements the SessionHandlerInterface.

Code Select Expand

$handler = new MySessionHandler();
session_set_save_handler($handler);

// Start the session
session_start();
   
class MySessionHandler implements SessionHandlerInterface
{
    public function open(string $path, string $name): bool {
        return self::sess_open($path, $name);
    }
    public function close(): bool {
        return self::sess_close();
    }
    public function read(string $id): string|false {
        return self::sess_read($id);
    }
    public function write(string $id, string $data): bool {
        return self::sess_write($id, $data);
    }
    public function destroy(string $id): bool {
        return self::sess_destroy($id);
    }
    public function gc(int $max_lifetime): int|false {
        return self::sess_gc($max_lifetime);
    }

    public function sess_open() {
    ...
    }
    ...
    ...
}