wordpress versions compability

Your versions are not that far off. Do you really mean MariaDB below v10? v10.* would be better (10.4.12 latest stable). You might start there. Before doing so on the production site, I’d clone it to a staging or localhost site. Localhost with a hosts file entry for the domain allows you to use the DB unchanged, though you could not then access the production site on that machine.

If production content is actively updated, avoid making DB changes to your clone to avoid sync issues. The goal would be to get all localhost code working well on the latest versions, not to fiddle with DB content. Update everything to the latest available and deal with any fallout. Address the most egregious issues first, like fatal errors (duh!). Then warnings and notices. Don’t worry too much about pagespeed for now. Get everything working on the latest versions without logging any errors. If everything works on PHP 7.1 it shouldn’t be too bad.

Some people have reported sporadic issues with WP 5.3, but there are millions using it without issue. Issues are usually due to outdated add-ons or odd server configurations.

Thank you for your answer.
The database version is really old 5.5.52-MariaDB-cll-lve so I have to deal with that somehow. Have I understood it correctly that database upgrades are done when updating WordPress version. Is there a way to update the database version without doing the complete version update? And why is the database so old when WordPress core is 5.2.4?

I can set up localhost for the site for testing, however the multitude of different accessibility aid programs such as screen-readers and so on makes it a daunting task to say the least. But i suppose it is the way to go for testing the basic setup anyway.

I have contacted the support for the hosting as well on how to go about this. Google just say update to latest WordPress version. I am also a beginner at this (studying programming at the moment). There are a professional developer for the site but since it is way off budget for the owner we try to avoid this. My worst fear is that i mess up so badly that it will repeat the issues they had last time. I guess my backups will save some of the headache at least. I managed to get all add-ons updated and working at least , as well as some security fixes. Malware scan with Cerber showed some issues as well that will have to be looked into in time. I have also seen that they turned off autoupdates, I assume this is because of earlier problems.

info fom phpmyadmin :
MySQL

Server: 10.209.1.109 via TCP/IP
Server version: 5.5.52-MariaDB-cll-lve
Protocol version: 10
User: xxxxxxxx
MySQL charset: UTF-8 Unicode (utf8)

Web server

Apache/2.2.22 (Ubuntu)
MySQL client version: 5.5.35
PHP extension: mysql Documentation

• This reply was modified 4 years, 9 months ago by anderslinn.
• This reply was modified 4 years, 9 months ago by anderslinn.
• This reply was modified 4 years, 9 months ago by anderslinn.

WP updates to the DB will only affect its own schema, they do not affect the DB engine version. The DB engine version is outside of WP, just as PHP, Apache and the O/S versions would be independent of WP updates. Your DB schema is very nearly up to date by virtue of WP 5.2. That is unrelated to the MariaDB version. WP updates its schema during regular version updates, but updating MariaDB is up to you or whom ever the sysadmin is.

Whether you setup a localhost test site or not depends in part on whether you want to keep the production site up or not. If updates cause fatal errors, the site will be down until you can resolve the errors. Even if not fatal, it may not work correctly right after an update. If having the site go down or not work right for a time is acceptable, you can just update the site directly. I happen to prefer working on localhost anyway. For any major work on a site, I think it’s worth cloning locally.

Testing site functionality on a variety of devices could be an issue on localhost. It depends on how your LAN is setup and if the devices are tied into it. Even if complete testing locally is not possible, at least you can get the bulk of it working in browsers and mobile emulators running on your work station. Final testing could be postponed until the site is live.

Since you are not completely confident of your sysadmin skills, I think that is all the more reason to work on a local copy. Much less pressure to get it right (and no one will see the mistakes you make along the way ?? ) This does add to the tasks you need to accomplish if a localhost installation is not already in place. I think it’s worth doing anyway. TBH, the updates should go fairly well. I don’t really anticipate any problems. But there is always that chance. I’d rather find out on a test installation than a client’s production site. If you’d rather not mess with localhost, it’ll probably be fine.

BTW, the auto updates are only applied for minor updates. Major point updates like 5.x always require manually starting the process. Minor updates are often security patches which you shouldn’t want to postpone. For most users, minor updates happen without a hitch.

Thanks again, feels a bit clearer now.
I already have Xamp localhost set up for some schoolwork, so should be easy enough.
I got a reply from the hosting company that they would have to do the database update, and that they don’t have plan for this at the moment(!), doesn’t sound good considering end of life for 5,5 is now in April. Well another problem for another time I guess.

local copy it is.

Some hosts really drag their feet with version updates. In the case of DB versions, I’d fully expect an otherwise up to date WP installation to work fine on an older MariaDB. End of life PHP versions would be much more concerning.

5.5 isn’t as bad as it sounds, MariaDB versions jumped from 5.5 to 10.0.

Warning: once you get comfortable working on WP locally, being forced to do any significant development on a remote server becomes rather unpleasant ??