Ryan Cramer

I don't think there's anything we can do about this at present since we rely on jQuery UI for this. But it sounds like longer term we should consider not...

ProcessWire just supports compilation of modules that don't already have a namespace. The purpose of it is only to support that most PW 2.x modules continue to work in 3.x....

As a matter of security we validate both the session and the code. (We do the same with the core ProcessForgotPassword module). Maybe down the road we can provide an...

I think this one was already fixed on the core dev branch awhile back. If you want you should be able to grab the /wire/core/WireHttp.php file from it if you...

Thanks @harikt I've been meaning to get in touch with you about this. I don't use composer everyday and thus don't consider myself an expert on it, but know that...

Thanks @harikt this is very helpful. I have gone ahead and added support for the composer vendor autoload per your suggestion. Rather than putting it in the /index.php file, I...

> Can't it be kept in boot.php than in buildConfig ? It could be, but boot.php is only called for the master instance, not for any other PW instances that...

@Crell Thank you very much for taking the time to reply here, this is all very helpful, excellent info. There's a lot to consider and think about here for now...

@Crell We've got to continue supporting the admin install/upgrade process of modules and core, just because we've already gone down that path… and can't really take it away. One of...

Good points @LostKobrakai > Say I want to use two modules, which both depend on a library, which is available via composer. Now at best this library would only be...