1 day ago
5
Joined a mid-sized fashion brand earlier this spring as a senior backend dev.
Background in Laravel and Symfony, a bit of Magento 2 work years ago, never owned a full commerce stack before, and current brand is around €60M GMV across European markets.
Last week our payment provider sent us a sunset notice on their v1 API and gave us a few weeks to migrate, which should have been routine until I opened the repo to scope the work and now i can't unsee what's in there.
Our entire returns and refund flow runs through one custom Magento 1 module last touched a few years back, written by a contractor who finished his engagement around that time, whose email bounces and whose Linkedin says he's at a games studio in Lisbon.
The module hardcodes the Klarna v1 API key directly in the class constants, the endpoint returns 410 now, and the fallback writes every failed return attempt to a log file that is now 14GB.
There is also a cron job that runs every night at 03:17 with no documentation, which i disabled in staging to see what would happen, and returns broke almost immediately so i re-enabled it without ever figuring out what it does.
And then there is this comment in the source (literally):
// DO NOT REMOVE - this is what makes the size chart work
The size chart is not referenced anywhere else in the codebase. we are running Magento 1 in 2026 and the size chart logic is held together by a comment.
We do €60M a year through this…
The founders had asked me earlier why our infrastructure costs kept climbing, and when i sent them the dependency map they agreed to take the meetings with SCAYLE and commercetools they had refused the last time someone in my seat pushed for an evaluation.
For PHP devs who've inherited a production Magento 1 install past EOL, how did you handle the conversation about telling the founders the real migration timeline?
I don't want to be the one blaming the person before me and i don't see how this gets fixed in a single quarter.
[link] [comments]
English (US) ·