Looks good! I think it's worth seeing about integration. (Also, what's been up? It's been a little while, hasn't it?)

And don't fret, it wasn't boring. It's nice to have my eyes actually opened up to coding standards that aren't from like 2007, lol.

Working a lot right now so had to put some things on pause.

Symfony has some great features but also some limits to its documentation. I already raised 3 issues with the EventDispatcher docs project.

That's okay, no worries. Take your time.

By the way, do you have an account on ycombinator/slashdot/etc? Might be worth putting out the news about XMB's redevelopment on those kind of programmer spaces - you never know quite who's lurking, and jogging once-thought-to-be-lost memories might actually be a decent shot.

Meanwhile, speaking of documentation, what's the XMB documentation like? I haven't looked into it much.

I maintain a few pages in the docs. Nobody has worked on the rest in a very long time.

https://docs.xmbforum2.com/index.php?title=Special:Contribut...

Huh, no signup page?
I was going to fix up the BBCode one.

This community is too small to justify anonymous (spam) wiki usage. I will setup an account and send it to your email today.

I don't think the email went through. Typical GMX moment I suppose.

Feel free to U2U the password or something.

(Also, there's a missing line break in the last section of the board rules on this very site. )

Just got busy, sorry. I'll work on it now.

Nice first edit. I can see that BBCode page has a lot of old formatting issues. Based on the short history, my guess is it didn't import very well either from the old wiki or the old HTML files.

I did think it was a bit cumbersome. Still needs some work, but it's not as weird as it was.

Trying to untie a knot on the alpha site today. I tracked down a bug in a file I'm working on, with no errors thrown. When I stub an error_reporting() call it returns -10251 which... without some kind of binary calculator could mean just about anything. I'm also wondering if that level is invalid and where it's coming from.

https://github.com/php/php-src/issues/18867

Here's the problem with DreamHost: They wrote a proprietary PHP extension called dh_php_ext that forces a bit mask of ~2 & ~8 & ~2048 & ~8192 on the PHP error_reporting value.

The workaround is to add this to the .user.ini file in the site directory:

error_reporting_allow_deprecated = 1
error_reporting_allow_notice = 1
error_reporting_allow_strict = 1
error_reporting_allow_warning = 1

DreamHost recommends doing this in the phprc file, however those are version-specific and less convenient.

After that, it might be necessary to use an SSH login to kill the php processes.

killall -9 php84.cgi -u <username>

This implies you will have to create an SSH login if you don't already have one. Alternatively, it may be possible to wait several minutes for the PHP process to recycle on its own.