Simple Machines Community Forum

SMF Support => SMF 2.0.x Support => Topic started by: WantSome on December 31, 2019, 08:12:37 AM

Title: 2.0.16 PHP issues
Post by: WantSome on December 31, 2019, 08:12:37 AM
Hello,

Today I managed to update to 2.0.16 and then 2.0.17 - I read in other threads that the 2.0.16 will have PHP 7.2 support.

I therefore updated the php on my server to 7.2.

Upon doing this it seemed impossible to post on the forum - it says that the session time has expired, regardless of how long it takes to post the message or when the user logged in. 

I have moved back to php 5.6 which seems to allow posting.

Any thoughts?
Title: Re: 2.0.16 PHP issues
Post by: Looking on December 31, 2019, 08:15:07 AM
Did you try clearing your cookies, looking at the error log to ensure nothing was amiss?
Title: Re: 2.0.16 PHP issues
Post by: WantSome on December 31, 2019, 08:32:33 AM
Thanks Looking!

I tried clearing cookies, and that seemed to make the issue worse by causing a 'session verification failed' error message on all reloads of the forum.

Error log shows:

/forum/index.php?action=logout;cdb3c031=0c238b40fdfe8b5d0c5f28ed866d7eb0
2: session_start(): Failed to read session data: user (path: /var/cpanel/php/sessions/ea-php72)
File: /forum/Sources/Load.php
Line: 2561

This is the segment of the file it shows as containing an error:

2552: // Use cache setting sessions?
2553: if (empty($modSettings['databaseSession_enable']) && !empty($modSettings['cache_enable']) && php_sapi_name() != 'cli')
2554: {
2555: if (function_exists('mmcache_set_session_handlers'))
2556: mmcache_set_session_handlers();
2557: elseif (function_exists('eaccelerator_set_session_handlers'))
2558: eaccelerator_set_session_handlers();
2559: }
2560:
==>2561: session_start();
2562:
2563: // Change it so the cache settings are a little looser than default.
2564: if (!empty($modSettings['databaseSession_loose']))
2565: header('Cache-Control: private');
Title: Re: 2.0.16 PHP issues
Post by: Illori on December 31, 2019, 08:36:17 AM
given the error you are seeing, ask your host to look into it. they may be able to fix it.