7

Looks like you were missing the relationship tag pair for your person field. Try this: <Videos> {exp:channel:entries channel="videos"} {person} <Video> <Subject>{person:title}</Subject> <Facts> {person:facts} <Fact>{person:facts:fact}</Fact> {/person:facts} ...


6

Conditionals based on URL Segments is how I would handle this. For your example, I would have in my books/chapters a conditional like {if segment_2 == "summary"} {embed="embeds/summary_code"} {/if} I'd use an embed just to keep the template cleaner — instances where I do this do tend to be on more complex site where I like keeping things as clean as ...


6

It looks like you found a bug, Sean, sorry you got bitten by it. I've reported it and posted a fix here: https://support.ellislab.com/bugs/detail/19871


5

Are you looking for something as straightforward as this? <html id="template-{segment_1}-{if segment_2 != ''}{segment_2}{if:else}index{/if}"> Ah, I see you are wanting embeds as well. Here is a very simple plugin that will output some metadata for the template that is currently being processed. <?php if ( ! defined('BASEPATH')) exit('No direct ...


5

Under Members -> Preferences in the control panel, you can set the Profile Triggering Word (see docs) to % which will make them completely inaccessible from the frontend. Another technique is to configure it randomly in the config.php like this: $config['profile_trigger'] = rand(0,time());


5

For times where the Channel module is overkill, or the random bits of editable content don't really fit the Channel mould, Low Variables is really great. It has a lot of added features beyond just making global variables easily (and safely) editable by end users. Some of the big benefits are text formatting options, custom content types for the global ...


5

Can you get the templates to render if you leave index.php in your URL? eg localhost:8040/index.php/cursos If so then it is your .htaccess. Max is right about the order of your .htaccess file. Also, you could try adding a '?' in your RewriteRule directly after index.php eg RewriteRule ^(.*)$ /index.php?/$1 [L] A fairly reliable method of removing ...


5

You can't delete index templates, so you'll have to include {redirect='404'} on those templates to force them to 404.


5

Or set a $env_global['myjs'] in the config.prod.php with the analytics code ID number and leave that var blank in the config.dev.php then just {myjs} in the template and it only outputs the ID in production.


5

You can not use Template Routes to remove index.php from your URLs. To remove index.php from you URLs you need to set up a redirect in an htaccess file, there are instructions here. Getting rid of the group name is where Template Routes comes in. Navigate to the Template Route Manager under Design ‣ Templates ‣ Template Route Manager. Locate the Route field ...


5

It looks like you moved your templates folder to outside the system folder. Since you already did it, why not move it to above the web root? Just remember to update the related settings. (see "Server path to site’s templates" at the bottom of the page) To keep all system files above the web root is good practice. Alternatively... If for some reason you ...


5

I don't think it's left that many short to be honest. Most developers I'm aware of save their templates as files. Whilst I'd always recommend having version control in place, you don't need it, you can still save templates as files without Git. As for tutorials, the Ellislab docs are pretty explicit about how it's done. The learning curve for Git isn't ...


4

Couldn't you just use a Snippet for this? It would contain the markup and code used inside a tag, which you could re-use with multiple tags. For example: {exp:low_search:results ... } {sn_entry_list} {/exp:low_search:results} {exp:channel:entries ... } {sn_entry_list} {/exp:channel:entries} An so on.


4

When you use if else statements EE executes all the code in every statement before deciding what to output. This makes it very slow indeed. What you need is devot-ee.com/add-ons/switchee Now gimme some credits ;-)


4

By default EE looks for the category indicator in the URL, eg www.site/recipes/category/meat, then output content based on that category url title (/meat). If you don't want to use the category indicator you'll need to use the LowSeg2Cat addon http://gotolow.com/addons/low-seg2cat - you can then use one entries tag and one template for any category, simply ...


4

Yes, ExpressionEngine comments stop at the next --} that they find. It's quite irritating. The rule of thumb I use is to use HTML comments for notes about the frontend code, and ExpressionEngine comments about the EE code. That tends to eliminate the problem most of the time. Sometimes I just cut + paste blocks of code into other documents while I'm ...


4

You can't actually nest comment blocks. In PHP you wouldn't be able to nest a /* */ within itself, nor would you be able to nest comments in HTML <!-- <!-- --> -->, but you could try adding spaces arbitrarily in between for personal notes of where comment blocks used to be. Could be useful if it's a snippet of code you may need to reintroduce ...


4

While use cases for it are rare, CSS templates can parse tags if you need them to, but you must link to them with {path='template_group/css_template'} instead of {stylesheet='template_group/css_template}.


4

Yup - make sure you set "require all segments" to "no", then just add another segment to the rule: /about/{extra:alpha_dash} :alpha_dash means that the segment can contain alpha-numeric characters, underscores, and dashes. There are other rules available as well. Then in your template you can check the value of the extra segment this way: {if segment:...


4

You need to create a channel field into that channel and in channel entry, you need to assign that user group type who can access the page. for eg: Suppose you have a channel (named as "XYZ") and add a new channel field (as 'group_permission'). This channel field can be drop down and you can add group listing in drop down (as group A, group B) Now Go ...


4

Starting from version 2.8.0 you can use standard global variable for this {cp_session_id} if you want to make link to edit entry, don't forget about special tag for this which available from version 2.9.0 {cp_edit_entry_url} You can also output the cp main url (like example.com/admin.php) using global variable (from ee 2.8.0) {cp_url}


4

The problem is having no rule and having alpha_dash are exactly the same thing, so the error message is correct, those are duplicate routes. If you added the :pagination rule to the {pagination} variable, then it should work: /about/news/{pagination:pagination} Also, you'll need to have the {pagination:pagination} rule first, since alpha_dash would catch ...


4

Do you have PHP Parsing Stage on "Input"? <form method='POST' action='gen_req'> <input id='input' name='uid' placeholder='uid' /> <button class='btn'>Go</button> </form> {exp:member:custom_profile_data member_id="<? echo ee()->input->post('uid', TRUE); ?>"} <p>{email}</p> {/exp:member:...


3

The issue is one of parsing order... User Defined global variables are the last thing to be parsed. This PDF outlines ExpressionEngine’s Parse Order. This page in the docs details the Rendering Stages of the EE template engine. The solution is to switch to using a Snippet instead.


3

To expound on my comment to this answer, and I acknowledge this is a bit unorthodox, this solution will improve performance by only executing one channel entries tag. The query tag will fetch the entry IDs, and dynamically build an embed variable that we will use on a single channel entries tag for this page request. {exp:query sql="SELECT entry_id FROM ...


3

A quick Google search seems to indicate that it's the thumbnail icons that Coda continually regenerates, which will render the HTML (including your Google Analytics code). See this thread The solution they offered is to collapse the preview thumbnails into text. I don't have a copy of Coda, so I don't know exactly how to do that, but it sounds pretty ...


3

You'd do it precisely as you have done. If you use the custom member fields within a channel entries tag loop then you will output information about the author of the entry being displayed. You don't need any custom add-ons to do this.


3

Yes, all custom fields for each entry you call via channel:entries are loaded by the template engine and ready to be parsed, so your latter idea is a good one.


3

You can accomplish that by doing the following: Make a template group called 404.group and in that template group create an index.html template (this will be your 404 template) Set "Enable Strict URLs" to "Yes" in your Global Template Preferences For the "404 Page" setting choose "404/index" (the template you created in step 1 above), again in your Global ...


3

You may want to check if mod_security is installed on your server and either disable it or change the configuration. My guess is that your issues is that mod_security is seeing the SQL query in your query tag and blocking the submission.


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