[RFC|Merged] Make ext/ directory

[EXreaction]

Since board owners will be using the ext/ directory, I believe it should be included as an empty directory in the package.

I think this will prevent any confusion as to where to put extensions if the ext directory does not exist or if they are supposed to create it, etc, from first time board owners.

[Pony99CA]

Maybe not empty -- you might want a .htaccess file there -- but that's certainly a good idea.

Steve

[callumacrae]

Maybe not empty -- you might want a .htaccess file there -- but that's certainly a good idea.

Steve

It can't be empty or git won't accept it. I can't see the point in a htaccess, but a .gitignore or .gitkeep would be good.

[DavidIQ]

Or the usual blank index.htm file.

[imkingdavid]

Or the usual blank index.htm file.

Right. I'm not sure we need to add yet another .gitignore, nor do we need a .gitkeep.

[EXreaction]

If nothing inside the ext directory should be accessible, it should be blocked by a .htaccess rule somewhere. Although this probably isn't the case, image files and such may be required within the extension...

[Senky]

+1 to RFC idea.

[Marc]

+1 for the idea

Or the usual blank index.htm file.

+1

[DavidIQ]

If nothing inside the ext directory should be accessible, it should be blocked by a .htaccess rule somewhere. Although this probably isn't the case, image files and such may be required within the extension...

I know my ReIMG MOD when converted to an extension would have images in its directory under /ext/ as they are currently just being copied to each style. There are also some other files included, such as one that is called via AJAX as well as common .js files. These I assume would all need to be in /ext/ and they would obviously need to be accessed outside of this directory. At the moment I have most of the files in a reimg directory in the site root so I'd be moving them.

[EXreaction]

PR: https://github.com/phpbb/phpbb3/pull/1027