https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35716
--- Comment #20 from David Cook <[email protected]> --- (In reply to David Cook from comment #19) > (In reply to David Cook from comment #16) > > Sorry, Pedro, but given the amount of work this is going to take... I don't > > think that I'll be working on it at all. > > Well, clearly I didn't stick to that. > > But even refactoring Koha/Template/Plugin/Asset.pm... we need to know the > application file system route if we're going to find the file as part of the > algorithm used there... > > Which I guess means maybe adding another parameter to "Asset.url()" which > takes a value like 'shared', which doesn't do a filesystem lookup against > the application file root and instead just serves it from the web root. Catalyst looks like it's a bit sneaky with how it finds its "home" and "root" (for templates). I don't want to get autobanned by Bugzilla so I won't paste links... Catalyst.pm#L3584 and Catalyst/Utils.pm#L204 We could use __FILE__ to get /kohadevbox/koha/Koha/Template/Plugin/Asset.pm or /usr/share/koha/lib/Koha/Template/Plugin/Asset.pm Using their algorithm we could then pop off Koha/Template/Plugin/Asset.pm and "lib" if it's present which gives us "/usr/share/koha" or "/kohadevbox/koha" which... doesn't help us. I reiterate about how Koha's file structure is one of my pet peeves... -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
