Update Thirty Bees to stay in step with PHP - But did it work?

[Ian Ashton]

As my ISP moves PHP along I occasionally have to update Thirty Bees to stay in step

My order of play was

Log into BackOffice

Move site to PHP 8.3 on my Control Panel

Run Core Updater [ 1.6.12 ]

Set target to PHP 8.3

Run Core Updater/Check Updates followed by Update Site

Then in BackOffice looked at Advanced Parameters/Configuration Information

which reported

Thirty bees revision: 1.6.0

Build for PHP version: 8.1

Your server is running on PHP version 8.3.25. You should use core updater and fix your installation

BUT now running Core Updater says 

Core Updater/Check Updates =>  Your System is up to date!

Your system is up to date!

You are already using latest stable version 1.6.0.

No further actions are required.

So did anything happen? Shop seems to be working OK.

Why the mismatch between Core Updater and Advanced Parameters/Configuration Information?

 

 

 

 

 

[nickz]

Glad it worked. 

I'd suggest to move you shop asap.
Hostings who force you are no good.  

[the.rampage.rado]

Could you try and follow this procedure and tell us if it makes any change.

At this very moment if you're updating to version 1.6, the same version should be in your BO.
If you update to edge channel your BO should show 1.7 (which is currently not released as final version).

When you switch between php versions you update only dependencies, the core is not updated.

 

[Ian Ashton]

4 hours ago, the.rampage.rado said:

Could you try and follow this procedure and tell us if it makes any change.

At this very moment if you're updating to version 1.6, the same version should be in your BO.
If you update to edge channel your BO should show 1.7 (which is currently not released as final version).

When you switch between php versions you update only dependencies, the core is not updated.

 

Is it OK to switch to 1.7 to test this and then revert to 1.6? Or Should I stay on 1.7?

It's just that I'm doing it on the live shop. If 1.7 is nearly live then I'm OK staying on it.

[DRMasterChief]

Hi,  just a small notice:  perhaps you'd like to set up a test shop on a cost-effective hosting provider (a 1:1 copy of your shop).

This way you can easily test any changes and modules. There are already suitable hosting packages available for as little as 3-4 dollarini per month.

I'd like to recommend www.serverprofis.de, which offers excellent performance.

[the.rampage.rado]

Currently edge has no pressing bugs (in fact it has quite lot of work done since 1.6 in terms of bugs and small new features).

If you have a test installation I would strongly recommend updating there to 1.7, see if it's working with php 8.3 (it should work but third party themes and modules might have a problem) and then update your production after you've made a working backup of it (files structure and db).

I use edge on my production and I can't remember when was the last newly introduced but I noticed in my daily work.

But thirty bees 1.6 would also work on php 8.3 (with few more deprecation warnings which should not be conserning) so if you only want to make your install work on php 8.3 I would recommend to play with only one variable - update your current store and make it working robustly on 8.3 and only then update it to edge if you see any reason.

[Ian Ashton]

I did try the update on my test installation which ran OK.
Advanced Parameters/Configuration Information report below. I'm not sure about "Install the 'yaml' PHP extension on your server " as its a shared server so PHP managed by the ISP.

 

 

 

 CONFIGURATION INFORMATION

This information must be provided when you report an issue on github or forum.

 SERVER INFORMATION

Server information Linux #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64

Server software version Apache

PHP version 8.3.25

Memory limit 128M

Max execution time 120

 DATABASE INFORMATION

MySQL version 5.6.51-log

MySQL server IP

MySQL name TB NAME

MySQL user TB USER

Tables prefix prefix_

MySQL engine InnoDB

MySQL driver PDO

 STORE INFORMATION

Thirty bees version: 1.7.0

Thirty bees revision: f1c64a1600692325f6ff2621edb590519bf7c2ca

Build for PHP version: 8.3

Shop URL DOMAIN

Shop Root Directory: ************************

Current theme in use community-theme-default

 YOUR INFORMATION

Your web browser Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/143.0.0.0 Safari/537.36

 CHECK YOUR CONFIGURATION

Some required tests failed

• Install the 'yaml' PHP extension on your server

[Ian Ashton]

54 minutes ago, the.rampage.rado said:

But thirty bees 1.6 would also work on php 8.3 (with few more deprecation warnings which should not be conserning) so if you only want to make your install work on php 8.3 I would recommend to play with only one variable - update your current store and make it working robustly on 8.3 and only then update it to edge if you see any reason.

Just to clarify - my live store is on PHP 8.3 and TB 1.6.0 and appears to be working.

what I don't understand is why Advanced Parameters/Configuration Information reports

 

Build for PHP version: 8.1

 Your server is running on PHP version 8.3.25. You should use core updater and fix your installation

 

 

HOWEVER running Core Updater doesn't do anything but says "Your system is up to date! No further actions are required"

?

[the.rampage.rado]

There is a bug in thirty bees or the core updater that not every time the update runs define('_TB_BUILD_PHP_', '8.1'); in settings.inc.php is updated.

It is not critical and you can manually edit this if you're sure the update propagated and your shop is running OK.

This isssue was spotted a while back and @datakick advised that it can be fixed that way but nobody tracked down the issue so it's still present for some users in some scenarios.

[Ian Ashton]

Many thanks. That's what's happened.

Order restored ;-))))