Jason Coward
Jason Coward
It is currently not possible to move the core directory in 3.x. Composer has to have the path to it for proper autoloading and this cannot be a variable path.
No, there is not. Composer has to have the path before setup is executed.
Protecting the core using .htaccess or a simple nginx rule is just as secure as the security-by-obscurity of moving the core.
This was already discussed extensively in multiple places. If everyone would participate beyond this two-day rush to do everything all at once, there wouldn't be a problem here. It is...
> There could certainly be a check in the setup that looks for the core directory in its default location and warns about that. Unfortunately, I don't think that would...
The proper way to avoid directory traversal is to compare the realpath() of the path provided by the user with a pre-defined base path for the operation. I don't see...
If you can specify any directory, why are we preventing directory traversal with regex? This makes no sense. We need to be using basename() to get the filename and using...
I believe the process cannot load the existing classes and therefore cannot update them since it uses Reflection to get the existing code. For some reason, it cannot find the...
I'm a little lost. If you define a static element with a selected media source, it would have to be written by the media source. If you do NOT select...
> > This approach attempts to keep things working along the same lines as 2.x, where it's writing the file outside of the media source (in modElement). > > @opengeek...