Final note, just disabling "User Role Editor" seems to fix this issue. Seems like it must add some kind of filter to the User UI. I think wordpress.org/support/topi... might be the workaround.
Final note, just disabling "User Role Editor" seems to fix this issue. Seems like it must add some kind of filter to the User UI. I think wordpress.org/support/topi... might be the workaround.
It is. I was having an issue with NPM not respecting package manager fields and fell down the GH issues rabbit hole. Found an npm maintainer ranting against how corepack was terrible and npm wouldn't have to support it.
He couldn't give a single non hand wave reason.
This doesn't surprise me.
March 25, 2025 at 5:14 AM
It is. I was having an issue with NPM not respecting package manager fields and fell down the GH issues rabbit hole. Found an npm maintainer ranting against how corepack was terrible and npm wouldn't have to support it.
If the CMS handles the content and the front-end framework handles the templating; who handles the routing? Frameworks think they do. This requires an agreement on routing between the front-end and CMS.
But if the Framework deferred to the CMS, that'd be so much simpler.
March 21, 2025 at 2:50 AM
If the CMS handles the content and the front-end framework handles the templating; who handles the routing? Frameworks think they do. This requires an agreement on routing between the front-end and CMS.
But if the Framework deferred to the CMS, that'd be so much simpler.
FIle System routing conflates route with template, and to some extent content. Any given route(static or dynamic) is inextricably tied to a single template. This works great for "apps" that have heavy dynamic content and but not for relatively static content.
March 21, 2025 at 2:50 AM
FIle System routing conflates route with template, and to some extent content. Any given route(static or dynamic) is inextricably tied to a single template. This works great for "apps" that have heavy dynamic content and but not for relatively static content.