It's quite awkward to access files that are not public://, private://, or temporary://. The other locations could be handled with module://, theme://, drupal://, and perhaps library://

Comments

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

This is quite easy to provide in contrib, so hopefully we'll have a D7 contrib module that blazes the way.

pwolanin’s picture

pwolanin commented

My thought:

module://system is normally modules/system

module://views might point to sites/all/modules/views or sites/default/modules/views depending on where it's installed.

similarly we might have:

theme://default or theme://current (though need some way to be sure we can't have such a theme name)

as well as named themes e.g. theme://garland

I kind of like site:// or maybe docroot:// better than drupal://

tstoeckler’s picture

tstoeckler
he/him
Primary language German
Location Essen, Germany
commented

libraries://++ (...and subscribing)

chx’s picture

chx commented

misc://

I dislike a generic drupal:// 'cos that will be used instead of the specific ones.

pwolanin’s picture

pwolanin commented

@chx - is there no use for accessing some file in the top level of the Drupal install?

Anyhow - once we have git maybe we can do a more substantial re-org of code anyhow which will make us reconsider the details here.

aaron’s picture

aaron commented

@pwolanin - that's true; there's always #22336: Move all core Drupal files under a /core folder to improve usability and upgrades to consider.

@chx - that's a good point. i could see folks accidentally using docroot://sites/all/modules/my_module and then wonder why the queues are filled with issues wondering why it couldn't find docroot://sites/example.com/modules/my_module...

and yes, libraries:// would also be essential.

stevector’s picture

stevector
he/him
commented
Status: Active » Closed (duplicate)

#1308152: Add stream wrappers to access .json files in extensions