I'd be fine with a "if nothing else, fall back to default" option, too. Garvin?Don Chambers wrote:That is my whole point - I would not want to provide duplicate smarty templates if they are identical to /default/
YL
I'd be fine with a "if nothing else, fall back to default" option, too. Garvin?Don Chambers wrote:That is my whole point - I would not want to provide duplicate smarty templates if they are identical to /default/
Code: Select all
<script src="{$serendipityHTTPPath}templates/{$template}/js/myscript.js">
I'm assuming if somebody were to change that path (seems highly unlikely to me), he/she would know to edit 3rd party templates accordingly.Don Chambers wrote:And FYI, although we did it in BP, and I have done it in other templates, understand that the hard coded path 'templates' would be incorrect if anyone changed the default "relative template path" in their s9y configuration.
Oh. Yes, that might work.garvinhicking wrote:The js file simply needs to be fetched also with {serendipity_getFile}.
Haven't really worked with this in quite a while. Assuming you're using a recent dev snapshot, permissions are correct, cleaned out templates_c etc., i.e. the usual stuff:Timbalu wrote:What are your experiences so far?
I don't understand what you mean by that.Timbalu wrote:The fall back setting to whatever, however, seems extremly sticky.
If you use the navigation which is integrated in the s9y core, you need at least one theme option for it to work. This can be a dummy option. See the respective thread about core navigation.Timbalu wrote:I can still run it by having no config.inc, no lang.
Still not sure I get what you want to do or have issues with. However, since this is actually a rather old feature which everyone completely forgot about, I don't assume a config.inc.php is a necessary element of a child or engine theme. (Garvin should definitely comment on this after his vacation.)Timbalu wrote:It just means I havent found by now the very minimum setting required to turn this on/off.
No, not true ...yellowled wrote:As far I understand it, an engine template is supposed to have all files default has, which is why the recommendation to use default as the "ultimate" fallback engine is actually a good one for the time being. Helps keep the "actual" engine template tidy.
Code: Select all
$serendipity['defaultTemplate'] = 'bulletproof';
Code: Select all
engine: new_default,bulletproof,default
Code: Select all
$serendipity['template_engine'] == new_default,default
I guess we can assume a lot, we'll have to wait for Garvin to comment on this.Timbalu wrote:I would still presume it follows (myTemplate) ->new_default ->bulletproof ->default on the way falling back, differing in which file searching for css - other files via path or getfile - {TEMPLATE_PATH} - and or other path building functions.