You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that resolving path names to files is different for cached templates than for "live" templates. When I cache working pages' templates, which are composed of a variety of partials, some in subdirectories, I get a fatal error. Example error message below:
exception: File date-range-picker.xml not found in paths (., /Users/gits/web/staging/templates)
Note that the file being requested is actually located at this path:
I had closed this previously after finding a typo in a template that made it fail in this manner. But now I've proven via A/B testing that indeed sometimes cached templates do not find files that uncached templates are able to locate. There is a definite difference in behavior.
It appears that resolving path names to files is different for cached templates than for "live" templates. When I cache working pages' templates, which are composed of a variety of partials, some in subdirectories, I get a fatal error. Example error message below:
Note that the file being requested is actually located at this path:
The requesting template code looks like this:
The text was updated successfully, but these errors were encountered: