People who code: we want your input. Take the Survey

Hot answers tagged

5

Entry IDs are stored as an unsigned integer field in MySQL, meaning the maximum value is 4294967295


4

The {structure:child_ids_for:XX} tag is parsed very late, after plugin tags have parsed. In other words, too late to be used as a tag parameter. The channel:entries tag will receive the unparsed structure tag. You will have to use an embed to get around this: {embed="your/embed" entry_ids="{exp:structure:child_ids entry_id='43'}"} And your/embed template: ...


3

More a general MySQL tip: if you need to test the import and re-import a couple of times, keep an eye on the auto_increment value for the entry_id column of exp_channel_titles. Either reset auto_increment after deleting a test import, or set the entry_id value as well on import.


2

Example 1: In some cases {embed:entry_id} would be most useful by passing an entry_id from the parent template into the embeded one's entries tag pair entry_id parameter to just return the results of the given entry_id. {exp:channel:entries channel="your_channel" entry_id="{embed:entry_id}"} Just the entry that was passed from the parent template. {/...


2

In simple terms, that is how you call up the value of a variable declared within an embed tag. So for example, if in your "main" template, you insert an embedded template called sidebar: {embed="embeds/sidebar" the_passed_value="hello"} Then in the embedded template itself, you could have: I would like to say {embed:the_passed_value}. Which would render ...


2

You want to use playa:parents, not channel:entries. Playa will infer the entry_id so long as you place this tag loop within the channel:entries tag of the entry you're viewing. (You can pass it via the entry_id parameter if you like.) {exp:playa:parents channel="promos" field="promos_show_on_page" orderby="promos_order"} <a href='{promos_link}'>&...


2

Yes, forceid is specific to your site. In the context of the {embed} tag, forceid is a user created variable--the same kind of thing as weblogname, in your example: {embed="site/_head" forceid="18" weblogname="main"} These become variables available in the embedded templates. E.g., in site/_head, one can use {embed:forceid} and {embed:weblogname} ...


2

Sounds to me that the fixed_order parameter is exactly what you are looking for. Related: Expression Engine Entries Loop in Reverse


2

You can use the fixed_order="{embed:ids}" parameter. Documentation can be found here.


1

You can use two pipes as an OR operator in EE conditionals: {if:elseif entry_id == 216 || entry_id == 217 || entry_id == 218} You can also use a plugin such as Switchee (https://devot-ee.com/add-ons/switchee) if you have a large amount of conditionals.


1

Thanks to Justin Long tips I have got it to work. Example code looks like: {exp:store:checkout form_class="form-horizontal"} {items} *Some code here* {exp:channel:entries channel="products" status="not closed" dynamic="no" entry_id="{entry_id}"} *Custom field code here* ...


1

I never used EECMS 1, but I gonna try to help you. There are some errors on your code. The segment_1 is always newsletter. You never could use it on {exp:weblog:entries entry_id="{segment_1}" [...]; if your second conditional evaluates as true, both your conditionals will evaluate, because you need a segment_1 to have a segment_2; if both codes ...


1

Why would you want to find out prior to inserting? When inserting, you can find out the new entry ID added using... ee()->db->insert_id(); From the Docs. So... $data = array( <your field> => <your value> ); if ( ee()->db->insert('exp_channel_titles', $data) ) { $new_entry_id = ee()->db->insert_id(); ...


1

Yes you can add multiple of the same items to the same cart. If the item is exactly the same (i.e. Large Blue Shirt) they will show up under the same item: 2 - Shirt (Large, Blue) - $15/each - $30 If they have different modifiers or a different price Store does not consider them the same item so it would show up in 2 lines 1 - Shirt (Large, Blue) - $15/...


1

Not familiar with that plugin but you can try… IF you're calling the {exp:channel:entries} tag, you could simply place it inside that tag and it'll work fine. If you need to have it outside the {exp:channel:entries} tag you could use Stash to record it like: {exp:stash:set name="catid" parse_tags="yes" type="snippet" trim="yes"} {!-- Save as snippet --} {...


1

The code that ends up in the template with your current setup is this: {exp:gwcode_categories entry_id="{exp:channel:entries url_title="{segment_3}"}{exp:playa:parent_ids}{/exp:channel:entries}"} (some code) {/exp:gwcode_categories} Can you see the problem now? You're using two tags as input for another tag's parameter value. On top of that, the double ...


1

The date in the screen shot says 2014? Is it possible it's not active yet?


1

Yes, that is it for a basic channel entry. If your channel has categories or relationship fields, or any advanced third-party fieldtypes (such as Matrix or Playa), there will be more inserts required.


1

The fix: a quote was missing: Bad {exp:channel:next_entry channel="leadership} Next {/exp:channel:next_entry} Good {exp:channel:next_entry channel="leadership"} Next {/exp:channel:next_entry}


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