Hello,
I want to summarize the reported problems here.
1) Permissions problem: if PHP cannot write in the DaDaBIK directory (at least during the upgrade), the up/up2 procedure cannot work, this is not related to V.12, same thing happened before.
2) After a long investigation and thanks to the help of a customer who set up a machine where I can see the issue, I discovered a piece of code in up2.php, specific to V.12, that can lead, on some systems, to the "PHP Warning: session_name() ... " issue that in turn makes the up/up2 procedure fail (while upgrade/upgrade2 worked). The issue has been fixed and as I wrote in another thread, I am planning to release in about a week a 12.1 release containing a few bug fixes including this one.
Best,
I want to summarize the reported problems here.
1) Permissions problem: if PHP cannot write in the DaDaBIK directory (at least during the upgrade), the up/up2 procedure cannot work, this is not related to V.12, same thing happened before.
2) After a long investigation and thanks to the help of a customer who set up a machine where I can see the issue, I discovered a piece of code in up2.php, specific to V.12, that can lead, on some systems, to the "PHP Warning: session_name() ... " issue that in turn makes the up/up2 procedure fail (while upgrade/upgrade2 worked). The issue has been fixed and as I wrote in another thread, I am planning to release in about a week a 12.1 release containing a few bug fixes including this one.
Best,