Hi
On 19.02.2015 17:52, Emmanuel BOUAZIZ wrote:
"There are two primary URL paths for static resources - |/chrome/common|
and |/chrome/site|. Plugins can add their own resources, usually
accessible by |/chrome/<plugin>| path, so its important to override only
known paths and not try to make universal |/chrome| alias for everything."
* I suppose that if a plugin creates its own resource directory, it
should be mapped too. A plugin like wikiextras creates 7 of these
directories which makes a lot of aliases
Ideally, yes.
* I don't understand why "its important to override only known paths and
not try to make universal |/chrome| alias for everything", unless you
suspect a rogue user could create more directories in `htdocs`
I think it just means that not necessarily all paths can be mapped the
same way, e.g. because plugins will be installed later (but not mapped
in htdocs), or maybe some plugins are installed globally and mapped to
some shared path etc.
There's also /chrome/shared defined by the htdocs_dir option in the
inherit section of the TracIni.
http://trac.edgewall.org/wiki/TracDev/TracURLs
--
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.
