not enough caches invalidated for generic source files
Status: Beta
Brought to you by:
worden
Menu
▾
▴
#189 not enough caches invalidated for generic source files
A source-file element with no explicit project attribute can be used as a source file in multiple projects. However, in the page where it's stored, it's rendered using the default project for the page. And when it's edited, it's the default project that gets marked as modified, so that pages affected by that project are reparsed and project files are remade. The other projects that also use the source file don't get marked.
Discussion
Anonymous
I don't think I have a good place to put that information. I just use the project associated with the tag. I don't actually have a way to trace that tag back to all the projects that include it.
This is similar to the problem of recording which projects include an uploaded (Image) file. I hacked that one by adding the projects' PD page to the list of things linking to the Image: page. I could do the same thing linking to the mainspace pages where these tags are. But it's not a good hack. It would probably be better to make a new DB table for it, or something.