How safe is it to update the PHP stack individually?

Keywords: WordPress Multisite - Google Cloud Platform - Technical issue - Upgrade
I understand the recommendation is that php and mysql should not be updated individually. I’ve seen in a few other threads that a completely fresh bitnami should be used instead. What I’d like to know is how dangerous is it really?

I’d be looking to upgrade from 7.3.14 to 7.4

I’m running a multisite and have spent a lot of time just fixing a lot of issues and optimizing all my sites. I would like to avoid having to do a complete migration of them by having to pay for an extra plugin (All-in-One WP Migration) just to do the transfer. It’s a massive headache I would like to avoid if it’s possible to just push the next version of php.

Hi @dahr.chan,

As you have seen in other threads in this forum, it’s not possible to update the infrastructure components of the Bitnami WordPress solution without performing the migration to a new server. We build all the components from scratch and upgrading them in the same instance will require to rebuild them completely (and that requires time and power from the instance and knowledge to not to break anything so we do not recommend that). You can ask in the WordPress forum to know if there is any other plugin that can help you with the migration without needing to pay for the “All-in-One WP Migration” one.

Happy to help!

Was my answer helpful? Click on :heart:

If I leave php and mysql alone is it fine to update wordpress itself (considering it should be backwards compatible)?

I’m going through updating to WP 5.7 and all my themes/plugins

PHP 7.4 seems to be a requirement for the latest version of WordPress.

If you do not want to pay for the plugin, you can launch a new instance with the latest version of the Bitnami WordPress Multisite solution and …

  • Copy your bitnami_wordpress database from the current instance to the new one

  • Copy the entire /opt/bitnami/apps/wordpress/htdocs from the current instance to the new one.

Note that the database configuration will be different so you can either create the user/password that your current wp-config.php file contains in the new instance ( or modify the wp-config.php file once it’s copied to the new instance with the credentials that are set in default wp-config.php file when you launch it.

  • Follow this video tutorial to fix the WordPress permissions

Happy to help!

Was my answer helpful? Click on :heart:

1 Like

Thanks, that’s great to hear there is an alternative solution. I will look into it and see if I can pull it off.

Also, thanks for posting the wordpress permissions bit. I was actually just struggling with that and wondering if it’s a concern that I have it set to daemon:daemon. I was having trouble with updating plugins so I followed another thread to use that user:group combo instead and it worked. Unfortunately I can’t change it back to bitnami:daemon because then apache can’t serve the files. It’s currently working leaving it at daemon:daemon so I was thinking of leaving it like that for now if it’s safe.