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
Created by: Jordan Lev ([email protected]) on 2015/08/04 21:33:14 +0000
Votes at time of UserVoice import: 2
Prefixing a template filename with an underscore prevents it from being served directly by Craft if a url matching its name happens to be requested. But this entire feature of "directly serve templates" is just nutty and I want to completely disable it for my site's templates directory (instead of having to prefix everything).
I tried setting the 'privateTemplateTrigger' config to an empty string, which worked for my site templates (that is, it prevented them from being served directly), but then it broke many of the CP pages (such as Globals and Plugins).
It would be great if we could just disable this feature altogether (but only on the site-level templates directory I guess, so as not to break the CP?).
This discussion was converted from issue #1151 on June 26, 2021 09:24.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Prefixing a template filename with an underscore prevents it from being served directly by Craft if a url matching its name happens to be requested. But this entire feature of "directly serve templates" is just nutty and I want to completely disable it for my site's templates directory (instead of having to prefix everything).
I tried setting the 'privateTemplateTrigger' config to an empty string, which worked for my site templates (that is, it prevented them from being served directly), but then it broke many of the CP pages (such as Globals and Plugins).
It would be great if we could just disable this feature altogether (but only on the site-level templates directory I guess, so as not to break the CP?).
See http://craftcms.stackexchange.com/a/10852/3931 for more details.
Beta Was this translation helpful? Give feedback.
All reactions