Hi @myselfmani
So it is possible to upgrade the WordPress version and your server without upgrading the plugins. I assume you already have auto updates to WordPress Core and plugins disabled.
The problem you’re going to have is that as soon as you update plugins, that’s going to overwrite any customisations. So my suggestion would be to first see if you can move the customisations into a separate custom plugin. That way you can upgrade the plugins, without loosing your customisations.
Can we fix the php errors alone or need to upgrade the plugin to latest, then update the customization in latest version
I am unsure what kind of customizations you are talking about.
Are they self-developed plugins? If so, you are responsible for updating them and may have to check line by line whether they are compatible.
Are they plugins from the WordPress repository that you have customized yourself? Then you’ve gone down the wrong path as your changes are not updateable. You need to find out what changes have been made, document them and compare them with the current status of the plugin in the repository.
3 plugins outdated and not updated in the WordPress Repository also. Here also, can we fix the PHP issues alone or can find the alternative plugin ?
Customizing repository plugins yourself is the mistake I described above. You simply don’t do that, even if a plugin appears to be outdated. Nobody can tell you whether there might be an update for the plugin in the future.
The best way would be to contact the developers of the plugin in question and ask for an update. If they don’t respond, look for an alternative. Only if this does not exist, you could create a fork of the plugin (a copy) and customize this copy for yourself. This copy should definitely use its own slug so that it is not overwritten during an update. This way you are responsible for the plugin you have customized and used.
