Hot answers tagged

11

If you enable the Output Profiler you'll see the profiler at the very bottom of the page. Look around for this: If you click the show link you'll see all of the queries required to build your page along with the file, line number, class, and method that ran that query: You might still need to do a bit of hunting because a query could be created in one ...


5

You can add disable_form="yes" to the {exp:store:product} tag to disable the creation of the form. (Docs.)


5

In addition to the fine answer by Wes I'd add that most likely you don't need to "find a better solution" you just need to use the disable parameter in your exp:channel:entries tags. A couple of those JOINs will be eliminated with this simple fix.


4

Ok - found a fix for this. This simple condition {if shipping_same_as_billing} ALWAYS SHOWS AS TRUE! <p><strong>Same as Billing Details</strong></p> {if:else} No longer works, but altering the condition to be more specific does. {if shipping_same_as_billing == 1} ...


4

By default, EE is support calculations in conditions only. For other cases you can use MX Calc {exp:channel:entries channel='links' orderby='link_order' sort='asc' dynamic='no' category='12' parse="inward"} <div class="item" id="pane-{exp:mx_calc expression='{count}+15'}" style="display: none;"> <!-- stuff here --> </div> {/exp:...


4

The best thing to do is have Tag convert to lowercase. There is a setting for that under preferences.


3

There is only one correct syntax style: {companies_type:label}. If it's not working you might have changed your options after saving an entry. So the stored value is not matching any options anymore and thus resulting an empty value for {companies_type:label} and {companies_type}.


3

Go to this field via Admin > Channel Administration > Channel Fields > Group > Field and switch the formatting back to XHTML confirm and then back again to none. When switching EE should show a checkbox before confirming asking if you want existing fields to be reformatted. Check this. Alternatively keep as XHTML in EE and use a plugin to alter the rendered ...


3

Is it an EE1 site? If so, go to Extensions, then Fieldframe's settings and check the path.


3

It's a BBCode problem: http://ellislab.com/expressionengine/user-guide/general/bbcode.html Pretty sure the issue here is the first [i] only, all subsequent [ii], [iii] should not be replaced as bbcode by EE. A dirty but effective method would be to change the very first instance of [i] to [&#105;] which is the html entity for the letter i. I tried a ...


3

Layouts are a bit hard to get your brain around to begin with. There are two things you need to know, and I think you'll be on top of it. Layout templates work by letting you drop the content from one template within another. The places that the content appears are defined by the position of the {layout:variable} tags that you put within the layout ...


2

I think you're on the right track with switchee, and something like the following should work: {your_relationship_field} {exp:switchee variable="{your_relationship_field:channel}" parse="inward"} {case value="news"} <a href="{url_title_path='news/entry'}">{your_relationship_field:title}</a> {/case} {case ...


2

uri_page="{last_segment}" is not a valid parameter for channel entries. You're looking for url_title I imagine :) {exp:channel:entries url_title="{last_segment}"} {exp:stash:set_list name="related_articles"} {related_articles} {stash:rel_title}{related_articles:title}{/stash:rel_title} {stash:rel_excerpt}{related_articles:excerpt}{/stash:...


2

If you're able to compile all of your data into something like a spreadsheet, you may be able to use one of the import add-ons like Solspace Importer, Data Grab, or Data Import. I've been using Solspace Importer for something similar to what you want to do, and it works well--and accomplishes a big chunk of the batch processing that I need. However, in my ...


2

Found the solution. The tag {order_email} works in the email templates.


2

EECMS just saves the IP of who edited an entry, not his or her member_id. You can try the Audit add-ons: Audit Pro, which lets you archive logged data, set custom email notifications and search log entries; Audit Tags, which lets you output Audit’s logged data in your templates. The add-on can be found on github as well.


2

Allows ExpressionEngine code to be used in entries and then parsed in the template. Currently, you cannot put EE tags into an entry/post and have them rendered in the template. Instead, the code itself will just display, unprocessed. This plugin makes it so any EE tags in an entry will actually be parsed and have results outputted. Allow EE Code by ...


2

Adding dynamic="no" fixed this issue.


2

Thanks for adding some details, but I'm still slightly confused. I'll lay out an attempt (too long for a comment anyways). You have some content that you want processed (into a file format?), but not until a browser event is triggered. Some clarification about ways to write modules for ExpressionEngine may help. A module can return data in multiple ways. ...


2

Sorry we haven't responded to your prior support request attempts. We'll try and get this sorted for you soon. I can think of two reasons that may cause this error to appear but I'll need to take a closer look. Can you please send me a support ticket via http://ee-garage.com/nsm-better-meta/support as I'll probably need to get more information about the ...


2

You can do something like that: {exp:channel:entries channel="test" disable="categories|category_fields|member_data|pagination|trackbacks|relationships" dynamic="no" } {if count%2 == 1} <div class="even"> {/if} <p>{title}</p> {if count%2 == 0 || count == total_results} </div> {/if} {/exp:...


2

Your issue is nothing to do with ExpressionEngine. The template you are uses javascript to smooth-scroll within the page. It appears to be configured properly for in-page scrolling, but not for links arriving from other pages. This is a consequence of how the scrolling utility you are using is written - it needs to check for whether it is being called ...


2

Typically in EE you can use the offset parameter. offset="1" would start the output on the second item in the loop and setting a limit parameter limit="1" would return only the second item. However, I am unsure if it works with your tags above as they are tag pairs within the AWS products module. If offset is unavailable as a parameter, you may need to ...


2

It is not so clear from what you say what actually you are trying to do, but at the simplest level, it seems that while example.com/product generates output when applied to the template fragment you provide, example.com/product/entry/entry-page does not. Probably this down to a parameter dynamic="no" that is missing from your {exp:channel:entries} tag. ...


1

Tag data should be saved to exp_channel_data, and therefore be searchable. Super Search can search Tags like this. Although I'm not sure for EE's simple_search form, I assume it would also work fine. Is the Tag field set as searchable? If not, please set it as searchable in the custom field settings in the EE CP. You may need to re-save the entry so that ...


1

You're nearly there. Just got the nested list tags the wrong way round, and you have to use the {entry_id} from the channel entries tag as the unique context when setting the list since {place_entry_id} is only available when getting the list: {exp:stash:set_list name="place-{segment_1}" parse_tags="yes" parse_depth="3" save="yes" scope="site"} {exp:...


1

You would simply use {url_title} within your entries loop. {exp:channel:entries channel="videos" search:category="some_category"} <span>{title}<span> <a href="www.domain.com/videos/{url_title}"></a> {/exp:channel:entries} In light of new information... If the field is a relationship or Playa field you can access the URL title by ...


1

Use a conditional statement to only output the heading on the first row: {if count == "1"} <div class="row"> <h1 class="style">Related Articles</span></h1> </div> {/if}


1

No, it's not. There's no mention to multiples channels on docs and Boyink talks about this case too. I don't know exactly what you're trying to do, but I believe that the query module can help you: {exp:query sql="SELECT channel_title AS the_name_you_want_for_your_variable FROM exp_channels WHERE channel_name IN ('news','contact');" } {...


1

I think the problem is that the Store JS code doesn't know the SELECT has changed so doesn't update the price. Setting the selected attribute doesn't fire the change event. You could test this by creating a change event on the select with a debug output to see if it fires. $(".options select").change( function() { console.log("SELECT TRIGGERED ".$(this)....


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