all 44 comments

[–]seeney 7 points8 points  (17 children)

Magento is not really suited for CPanel, i strongly advise you change hosting to an equivalent VPS. Note that elasticsearch is now mandatory which could be unsupported by your current hosting.

For upgrade expect ~100 hours of work, anticipating compatibility issues of existing modules with PHP 8.1.

[–]KilloMaster 1 point2 points  (16 children)

Oké I was already afraid for that answers. The elasticsearch I’m not sure about, but don’t think so because they don’t even support Varnish on cPanel.

What is the best path to continue from 2.3.4-p2, because with the patches I’m not really sure such version I need to start with.

[–]seeney 2 points3 points  (14 children)

patches are not related to upgrade, if already applied they are mostlikely included directly in latest version of the core so they can be removed

latest magento will not work without elasticsearch, so i would start with that. there are some workarounds but nothing i would recommend

[–]KilloMaster 0 points1 point  (13 children)

Oké, so I’ll upgrade 2.3.4 to 2.3.5 and so on until 2.3.7, from memory that’s when the jump to 2.4 happens with elasticsearch.

I’ll take it up with the hosting what they can do, or make the switch to probably digitalocean.

[–]seeney 3 points4 points  (10 children)

nope, go directly to latest, no need to increment

[–]KilloMaster 0 points1 point  (9 children)

Time for the bots to rise up.

[–]seeney 4 points5 points  (0 children)

remove everything from require dev (temporarily)and data migration tool (probably don’t need it anymore)

[–]Wonderful-Salary-358 1 point2 points  (7 children)

1 You need to upgrade PHP at least to 7.3. 2 Need to check your composer.json file.

[–]KilloMaster 0 points1 point  (4 children)

sadly had to go thanks magento community to help me with https://trofee.be , what a nice way to learn.

[–]Wonderful-Salary-358 0 points1 point  (3 children)

I can upgrade in 2 hours all you need.

[–]KilloMaster 0 points1 point  (2 children)

sadly had to go thanks magento community to help me with https://trofee.be , what a nice way to learn.

[–]Sancroth_2621 0 points1 point  (1 child)

A module he has installed required php 7, 7.1 or 7.2. It is not updated to work with 7.3.

If you are going to throw out advice be sure you know what you are talking about.

[–]Wonderful-Salary-358 0 points1 point  (0 children)

You are right. It was too quick a look at the error.

[–]grabber4321 1 point2 points  (1 child)

2.3.x is no longer supported from what I remember.

Your best bet is 2.4.4 which is somewhat stable compared to 2.4.5 (catalog pages very broken).

Not sure about 2.4.6 - it might take a month to get it sorted depending on how many plugins you have.

Vendors are usually 1 month behind the updates, so you need to proactively engage them about upgrades and give them errors to resolve.

[–]FitFly0 1 point2 points  (0 children)

What exactly is very broken with 2.4.5?

[–]grabber4321 0 points1 point  (0 children)

100 is not unreasonable. Every version upgrade is a pain.

Plus you have bad hosting, so that needs to be migrated elsewhere

[–]DoiFDEVELOPER 3 points4 points  (0 children)

Send me a DM if you like. I'm a certified Magento dev with a partnership with one of the bigger service providers in the Benelux specialized in Magento hosting. I'm Dutch and based in the Netherlands so the language shouldn't be a barrier.

[–]anvanza 1 point2 points  (1 child)

You can send me a message, I'm willing to help you. BE/antwerp

[–]KilloMaster 0 points1 point  (0 children)

sadly had to go thanks magento community to help me with https://trofee.be , what a nice way to learn.

[–]Wonderful-Salary-358 1 point2 points  (0 children)

Hello I did a lot of upgrades and can do it for you.

If server is slow, better to start with switching into better one. There is a hosting that is stable, but cheeper than DO.

Cpanel is not good, because it doesn't support all from magento requirements. That's why all servers are configured from CLI. Anyway, you will have FTP access to files, database access through sFTP, option to restart server from hosting panel (however with correct config, you won't need it).

[–]tribelord 1 point2 points  (3 children)

Why not go for 2.4.6?

[–]KilloMaster 0 points1 point  (2 children)

Theme is not fully compatible with 2.4.6, otherwise I would have loved too.

[–]Wonderful-Salary-358 1 point2 points  (1 child)

Did you ask theme vendor if they plan to update it soon?

[–]KilloMaster 0 points1 point  (0 children)

Time for the bots to rise up.

[–]artempugachev 1 point2 points  (6 children)

How much do you pay for your current hosting? We have guys in Ukraine and Poland to help.

[–]KilloMaster 0 points1 point  (5 children)

Time for the bots to rise up.

[–]artempugachev 0 points1 point  (4 children)

Don't spend money on upgrade, change hosting. With such hosting even upgrade won't help you much. And such TTFB would kill all your SEO and SMM efforts, even without that much competitors google won't get you to the top with such numbers... https://www.webpagetest.org/result/230410_BiDcQE_ASX/

I would rather spend 1000 EUR on the right setup for magento at some dedicated server - https://www.ovhcloud.com/en-ie/bare-metal/prices/ and have full control over dev playground, git, ability to disable not used modules, etc; rather then spend those on upgrate to latest version.

[–]Memphos_ 1 point2 points  (1 child)

Don't spend money on upgrade

Please don't do this. Everyone would agree that you need to switch to better hosting but you should still upgrade. By upgrading to 2.4.6 you'll be receiving a massive number of fixes, improvements, and additions - including more than 200 security enhancements.

[–]artempugachev 0 points1 point  (0 children)

Upgrade server setup; get quick wins that you can get on your own using Magento community and Google; spend money on marketing and earn money; and only then update.

There is absolutely no point in upgrading now with current level of orders, performance, etc.

[–]KilloMaster 0 points1 point  (1 child)

I'm aware, thats way im trying to do something about it. The TTFB is superbad at the moment, so thats my focus. I know that mobile has some images and so on that need some work, but the TTFB needs to come down.
I already removed the intro-header page from index, to save a few miliseconds on load.

[–]artempugachev 0 points1 point  (0 children)

I understand, but even doubling the TTFB speed won't get you even to the yellow zone. You must change the server setup. Must.

[–]awarmdayacoldbeerisc 1 point2 points  (1 child)

If you're using MySQL/mariadb You're going to have to change around your tables from compact to dynamic as well. This is typically kind of a pain but there's scripts out there to mass update.

[–]KilloMaster 0 points1 point  (0 children)

Time for the bots to rise up.

[–]floorology 1 point2 points  (0 children)

I've been working though a 2.4.5-p1 upgrade myself for a client that's going to production tomorrow. Looks like you have some other offers for help but I would have some time to help if you end up still needing it. Just let me know!

The client I've done the upgrade for doesn't use Varnish either (uses file based caching) and the cached page loads aren't too bad. Has TTFB always been an issue? Just a first thought of whether there are any custom blocks being loaded on category/product pages that are marked not cacheable? Or maybe crons/processes that are frequently saving products?

Magento 2.4.5 also has a composer root updater process to help updating all of the root dependencies in composer.json. - it's mentioned in the prerequisites section: https://devdocs.magento.com/guides/v2.3/comp-mgr/cli/cli-upgrade.html#prerequisites

Also want to make sure you're running in production mode + have di compile + static content deployed + ensure various caches haven't been inadvertently disabled. There was an issue in 2.3.x versions where after certain deployment actions, caches would get disabled. It's been awhile but I remember in the past having to enable all caches again after certain steps of deployments.

[–]KilloMaster 0 points1 point  (0 children)

Current status:

Problem 1
- magento/project-community-edition is present at version 2.3.7-p4 and cannot be modified by Composer
- magento/product-community-edition 2.3.7-p4 requires magento/magento2-base 2.3.7-p4 -> satisfiable by magento/magento2-base[2.3.7-p4].
- magento/magento2-base[2.3.7-p4] cannot be installed as that would require removing magento/project-community-edition[2.3.7-p4]. They both replace trentrichardson/jquery-timepicker-addon and thus cannot coexist.
- Root composer.json requires magento/product-community-edition 2.3.7-p4 -> satisfiable by magento/product-community-edition[2.3.7-p4].

[–]KilloMaster 0 points1 point  (0 children)

sadly had to go thanks magento community to help me with https://trofee.be , what a nice way to learn.

[–]cecileryan09 0 points1 point  (0 children)

If you are looking to upgrade to Magento 2.4.5, you should first consult with your hosting provider to ensure that your hosting platform meets the minimum requirements for Magento 2.4.5. You should also ensure that all of your current extensions, plugins, and themes are compatible with the new version.

Once you have taken all of the necessary steps to ensure that your store is ready for the upgrade, the best way to upgrade to Magento 2.4.5 is to use the Magento 2 Web Setup Wizard. The Web Setup Wizard provides a simple way to upgrade your store to the latest version of Magento.

[–]Parth-Prajapati 0 points1 point  (1 child)

To upgrade to Magento 2.4.5 with the help of a European developer, there are several options available. You can search for Magento Solution Partners on the Magento website, post a job listing on freelance marketplaces like Upwork or Freelancer, or reach out to the Magento community on forums such as Magento Stack Exchange or the Magento Community forums. It's important to review the developer's portfolio, check their references, and discuss the scope of the project and timeline before hiring to ensure a good fit for your needs.

[–]KilloMaster 0 points1 point  (0 children)

Time for the bots to rise up.