Hey guys, I've been messing around with this error on my own for a bit and I've given up.
I get this alongside a login/"Welcome to Your Piwigo Gallery" page:
Warning: session_start(): Failed to read session data: user (path: /home/497/307497/tmp) in /home/497/307497/public_html/include/common.inc.php on line 149
It won't login, but if given a wrong password it will take me to the identification.php page. Tried to chmod 777 the tmp folder and then doing a clean install, but without any results. The database tables do get imported successfully.
Screenshot:
I'm not too experienced with web servers so I pretty much poke at it until something happens.
Piwigo version: 2.8.3
PHP version: 5.2
I get this too on my local test site, after upgrading to PHP 7.1
https://bugs.php.net/bug.php?id=73616 has some information.
Problem remains in Piwigo 2.9.0b. As it is a test site, I don't care, but it should be investigated by Piwigo team.
Offline
related issue [Github] Piwigo issue #586
Offline
Actually there might be a problem with our code. Can someone test this ?
in include/functions_session.inc.php , function session_read, replace
if ($results)
with
if (pwg_db_num_rows($results))
Last edited by rvelices (2016-12-21 18:46:36)
Offline
dotdeb doesn't propose PHP 7.1 yet, I can't test it "easily" :-/
Offline
On [Github] Piwigo issue #586 mirlang says rvelices patch works fine.
Offline
I can confirm patch works.
Not related, but another warning pops up: Got error 'PHP message: PHP Warning: A non-numeric value encountered in /(...)/include/template.class.php on line 1791\n'
plg wrote:
On [Github] Piwigo issue #586 mirlang says rvelices patch works fine.
Offline
Actually patch does not work because it is $result and not $results
Code which does work in 2.8.4 is
{code}
$result = pwg_query($query);
if (pwg_db_num_rows($result))
{/code}
Offline
This fix did not make into 2.8.5 which is unfortunate
I have to reapply fix manually
Offline
Am I correct in saying PHP 7.1 is not supported at this time?
Offline
unless you hot fix the code yourself, yes
Offline
@plg would this bug be ever addressed?
it kind of frustrating to fix it with every new build
Last edited by Serge D (2017-02-10 18:23:33)
Offline
Hi SergeD
Serge D wrote:
@plg would this bug be ever addressed?
it kind of frustrating to fix it with every new build
Actually it is "addressed". The patch is applied on Piwigo 2.9, but not on 2.8. Piwigo 2.9 will soon be available as "stable" release.
Can you give a try to Piwigo 2.9.0beta2 and tell us if it's fine for you on PHP 7.1?
Offline
@plg
I have the same Problem and i tested 2.9 beta 2.
there is no Problem with php 7.1
Offline
plg wrote:
Hi SergeD
Serge D wrote:
@plg would this bug be ever addressed?
it kind of frustrating to fix it with every new buildActually it is "addressed". The patch is applied on Piwigo 2.9, but not on 2.8. Piwigo 2.9 will soon be available as "stable" release.
Can you give a try to Piwigo 2.9.0beta2 and tell us if it's fine for you on PHP 7.1?
@plg: as I am not actively monitoring evolution of the core, I am trying to stay on stable release. since it is confirmed for 2.9 above, I am looking forward to official release
Offline