FIXED Problems upgrading to V.12 using up/up2

[eugenio]

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,

 

[eugenio]

Fixed in V12.1

 

[Jaccarin]

PHP Version: 8.2.12

mysql version: 11.1.3-MariaDB-1:11.1.3+maria~ubu2204

Web server: Apache

Client: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36

Hi Eugenio

PHP has write permissions on the current folder: No NO To run the upgrade script, PHP needs write permissions on the DaDaBIK root folder.

Tried upgrading from 12.0 to 12.1 with up/up2 procedure but I'm getting this error. Not happened with previous upgrades. Is there a workaround or shall I do a manual upgrade?

Regards

John

 

[eugenio]

Hello,
nothing has changed from that point of view from the previous upgrade script; I guess that for some reasons, when you upgraded to 12.0 PHP had write permissions. Being able to write during the upgrade is a necessary condition.

Best,

 

[Jaccarin]

Hello,
nothing has changed from that point of view from the previous upgrade script; I guess that for some reasons, when you upgraded to 12.0 PHP had write permissions. Being able to write during the upgrade is a necessary condition.

Best,

Thank you. For some reason, the permissions on my site root folder had changed, but it's all fixed now.