Hot answers tagged

3

ExpressionEngine 2.8's introduced Template Routes so you now have more control over how your templates are processed. It allows you to override the default template route, which is /template_group/template. For example instead of going /blog/read/url_title you can now add a template route for read.html in the blog template group to load like /blog/url_title ...


2

As long as you don't have a template or template group named that url title, you can code your index template to take in {segment_1} as a url_title. {exp:channel:entries channel="foo" {if segment_1}url_title="{segment_1}" dynamic="no"{/if}} edit: This only works if you set strict url's to no


2

You can simply make entries for the return pages, and have transcribe handle it for you. What i do is to embed the form: {embed="_inc/.contact_form" thepath="{exp:transcribe:uri path='/contact/thank-you/'}"} {exp:forms_js_validation:init lang="{transcribe:language_abbreviation}"} {exp:forms_js_validation:add selector="form" require_class="...


1

Late to the party here but my guess is because you have dynamic="no" so it will always return a result.


1

An {if:else} conditional won't work here (or with any other tag to try to change a parameter) because it's parsed after {exp:...} tags. This is often called an advanced conditional. You can see this by turning on Template Debugging: the parameters should look unparsed or partially parsed for the tag. I don't have experience with Transcribe, Structure and ...


1

With wgcode_categories, you can add an orderby="cat_name" parameter.


Only top voted, non community-wiki answers of a minimum length are eligible