oh boy... here we go again...

> @return mixed

bruh

I don't see the issue

/s

@lambda123 🙈

Alrighty then.

🥹it's beautiful.

What is happening?

@Lensflare it's a nested str_replace...

Though I don't see a particular reason why the array form of str_replace wasn't used.

https://php.net/manual/en/...

You need to start at the last str_replace - it takes an HTML document and then replaces value=/ with an absolut url.

The rest of the str_replace calls work on the result of the previous str_replace calls and replace one HTML tag / attribute after another.

array form would have been much clearer I think.

you have typo in absolut

@vane no typo needs more vodka, comrade

💥💥💥

worst nightmare of string manipulation

Looks like someone unrolled a loop there.

Looks like something GitHub Copilot would come up with

@Frederick The whole file is some 9000 LOC... and it's not the only one...

Wow, this guy must be brilliant! 🤔

@Frederick nope! We talked about it and concluded on not killing them for a reason:

People die but their code doesn't, send them into good code rehab and force them to refactor **and** document.

This way we get more good coders and get rid of bad coders.

@lambda123 it is a possibility that *it was revealed in a dream once,* too

@melezorus34 technically if the input cannot be cast to a string then str_replace will return null.

@kwilliams but your intent is not to return null, correct?

@kwilliams https://php.net/manual/en/... no section here tells me about the null return thing.

Perhaps check your logs for errors?

@melezorus34 I am mistaken it seems. But honestly I've avoided PHP like the plague for the last 5+ years.

@kwilliams You have done the best, I hope you continue to do so too. Amen.