All Astronauts

I typed "The PHP programming language crying" into an AI image generator and all it gave me was a sullen, cosplaying Esther. BTW, next concert flyer? This.

Peanut gallery request.
As everything is being thrown under the aegis of Applications in the 5.x line, I'd rather not have that ACP page just clown-car out with a single (in some cases exceedingly long) list. Similar to Toolbox how about three tabs:
IPS Apps, 3rd Party Apps that have their own Content Item classes (or things with the Content Router extension maybe?), 3rd Party all-the-rest. You get the gist.
Any permutation of such to keep the clutter down would be very welcomed.

I typed "The PHP programming language crying" into an AI image generator and all it gave me was a sullen, cosplaying Esther. BTW, next concert flyer? This.

I typed "The PHP programming language crying" into an AI image generator and all it gave me was a sullen, cosplaying Esther. BTW, next concert flyer? This.

I typed "The PHP programming language crying" into an AI image generator and all it gave me was a sullen, cosplaying Esther. BTW, next concert flyer? This.

FWIW Red Hat 7 / Centos 7 installs lock in at curl 7.29 and YUM updates just patched in security fixes as the third point (7.29.14, 7.29.23, etc.).
The clown car that was Centos 8 didn't help matters as most people (I know...) skipped 8 and stayed on 7 once all that silliness went down.  It's not particularly difficult to force curl to upgrade to a more sane version but does require some manual work on your end to do so (repo and command-line stuff).
So, what I'm saying is, if you are rolling with RH/Centos 7 still and never updated curl, you need to force it on through or make the move to a higher OS version (or switch to Ubuntu or Rocky or ???).
 

You'll have to manually open it with a database edit. For plugins just the 'disabled' and 'requires manual intervention' fields in the entry need adjusting (to zero); ditto for applications. You probably need to dump your datastore after making the manual edits.
Also, you are right @aXenDev, this current beta 5 still locks on upgrading. If they are making just an IN_DEV check, then yeah, it would still lock as we upgrade outside of dev mode. If IPS is actually checking for the -TESTINSTALL flag on the key, then it's just broken.
I suppose I'm lucky. Just one thing locked for me... that has been running on PHP 8 for a year. I'm more weirded out by all the log messages saying it can't parse the plugin directories as they think they are not there.
EDIT: The latter is caused by missing widget and tasks directories. They can change the log message for that to better indicate that is the problem rather than just say the plugin directory itself is the problem.

You'll have to manually open it with a database edit. For plugins just the 'disabled' and 'requires manual intervention' fields in the entry need adjusting (to zero); ditto for applications. You probably need to dump your datastore after making the manual edits.
Also, you are right @aXenDev, this current beta 5 still locks on upgrading. If they are making just an IN_DEV check, then yeah, it would still lock as we upgrade outside of dev mode. If IPS is actually checking for the -TESTINSTALL flag on the key, then it's just broken.
I suppose I'm lucky. Just one thing locked for me... that has been running on PHP 8 for a year. I'm more weirded out by all the log messages saying it can't parse the plugin directories as they think they are not there.
EDIT: The latter is caused by missing widget and tasks directories. They can change the log message for that to better indicate that is the problem rather than just say the plugin directory itself is the problem.

You'll have to manually open it with a database edit. For plugins just the 'disabled' and 'requires manual intervention' fields in the entry need adjusting (to zero); ditto for applications. You probably need to dump your datastore after making the manual edits.
Also, you are right @aXenDev, this current beta 5 still locks on upgrading. If they are making just an IN_DEV check, then yeah, it would still lock as we upgrade outside of dev mode. If IPS is actually checking for the -TESTINSTALL flag on the key, then it's just broken.
I suppose I'm lucky. Just one thing locked for me... that has been running on PHP 8 for a year. I'm more weirded out by all the log messages saying it can't parse the plugin directories as they think they are not there.
EDIT: The latter is caused by missing widget and tasks directories. They can change the log message for that to better indicate that is the problem rather than just say the plugin directory itself is the problem.