Hot answers tagged

17

I'm using EE v2.7.0 and the syntax actually appears to be: {grid_fields} {grid_fields:relationship}{grid_fields:relationship:title}{/grid_fields:relationship} {/grid_fields}


11

Use the EllisLab Playa & Matrix Importer


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

The variables inside the field need to be prefixed with the Grid variable name, like this: {lv-home-slider:slide} {lv-home-slider:caption}


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

As of EE 2.7.3 this is possible via the native orderby="random" parameter. http://ellislab.com/expressionengine/user-guide/modules/channel/grid.html#orderby


5

The grid field is a looping field, so if the field is in fact called beneficiaries, you should have: {beneficiaries} {beneficiaries:total_rows} {beneficiaries:field_total_rows} {/beneficiaries}


5

Okay, this definitely is an Assets issue, but here's a temporary fix. Open up ft.assets.php and look up the grid_replace_tag method, around line 1771. In there, you can see this line of code: $field_name = ee()->db->select('field_name')->from('channel_fields')->where(array('field_id' => $this->field_id))->get()->row('field_name'); ...


4

I think you're on the right track. I'd create a Matrix column that is a dropdown or multiselect. Then output those variables as CSS classes or data attributes and handle the sorting on the client side using something like this: http://mixitup.io/#Documentation. <ul id="filters"> {your_matrix_field} <li data-filter="{matrix_select_col_name}>{...


4

I'd recommend trying class="{if '{social_links:network}' == 'Google'}google{/if}" Whatever you use for the conditional, if you match up the quotes usage (double versus single), it makes a big difference.


4

It sounds like MX Lone Star is what you are looking for. MX Lone Star is small fieldtype which you can use to replace standard checkbox. But the real power of this fieldtypes is opened in Matrix-like fields - you can limited choosing in this fieldtype per row or/and per column. It works with Matrix , and according to this blog post it's also Grid ...


4

If submenu is the grid fieldtype name, then all you need is: {if submenu:total_rows > 0}submenu contents{/if} You may need to add quotes and brackets around the condition if the above doesn't work


4

You can use your original code if you prefix variables with the Grid field's short name. The purpose of the prefix is to avoid conflicts with the outer Channel Entries loop; it doesn't affect functionality. {gallery_images} {gallery_images:community_image} <img src="{path}_thumbs/{filename}.{extension}" alt="{title}"> {/...


4

This works in my tests when accessing a child relationship: {relationship_field} <p>Child entry title: {relationship_field:title}</p> {relationship_field:grid_field} Column 1: {relationship_field:grid_field:grid_column_1} <br> Column 2: {relationship_field:grid_field:grid_column_2} <br> {!-- etc... ...


3

I think it will be enough to delete field record in exp_channel_fields table. Go to EE CP SQL manager (CP Home > Tools > Data > SQL Manager > Database Query Form) or phpMyAdmin or any other mysql manager: DELETE FROM exp_channel_fields where field_id = 21; if you want to be sure that any pieces of your grid field was removed, execute query bellow line-by-...


3

If by "robust enough" you mean do they have basically the same features, yes. I've used EE's Relationships without any issues. I love Grid's search:column_name feature. That's a step up from Matrix. However, since it is brand new, it does not work with as many third party fieldtypes as Matrix. I'm sure that will change in the next 2-3 months. Depending on ...


3

So, I've found a way to achieve this, which seems to work in the reduced test case that I created (Grid fieldtype with one column of text type and only one entry being entered in at a time). In the future, I'll create test that's a bit more complex and see if it becomes more involved. The code for this is: <input type="hidden" name="field_id_9[...


3

Your syntax is not following the user guide's instructions. http://ellislab.com/expressionengine/user-guide/modules/channel/grid.html#template-tags You need to add the prefix for each column. {images} <img src="{images:file_url}" alt="{images:caption}" title="{images:caption}" /> {/images}


3

I tried a billion combinations as well. This is how I used it for meta data (functional): {if articles_seo_meta_data:total_rows > 0} {articles_seo_meta_data} {articles_seo_meta_data:meta_title} {/articles_seo_meta_data} {if:else} {title} {/if}


3

The simplest way is to use {field:your_grid_fieldname} to automatically output the grid content. Make sure you are also including the channel form css: <link href="{path=css/_ee_channel_form_css}" type="text/css" rel="stylesheet" media="screen">


3

After a new channel and new field group and channel fields, I suddenly had the same problem for an existing channel(+fieldgroup)'s entries. It certainly wasn't a template issue. I'm pretty sure I fixed it now: try renaming the grid field's Field Name (and Publish Label to match) to something else. It should work then (though mind that the template tags ...


3

By default, the members of the guests group cannot upload to EE; this is a permissions issue, but, it's permissions within EE, not with the filesystem, which is why CHMOD'ing to 777 didn't help. Here's a link to a previous post with this problem, and a solution.


3

I don't have enough Grid data to test this BUT it sounds very much like you are running into the 100 record limit that EE adds automatically to channel entries if you don't specifiy a limit. Try setting a high value for the limit="" parameter, like 500 or so and see if that fixes it. It could be that without that parameter EE limits it to 100 automatically.


3

If you're wanting the switch tag to apply to the grid rows, then you need to prefix it with your grid field name (docs): {press_releases:switch='|||</div><div class="row">'}


3

You can use the Search parameter to return only rows that have the checkbox cell checked. {exp:low_variables:parse var="lv_homeslider" search:name_of_checkbox_cell="true"} {total_rows} {/exp:low_variables:parse} "true" should be the actual value that you entered under "Multi-Select Options" in the checkbox field/cell settings.


3

This is a known bug in 2.9.0 and will probably soonish be fixed in an update See: https://support.ellislab.com/bugs/detail/20462/grid-fieldtype-brings-up-warning-when-rows-are-present-on-entry-submit (ps. bug report includes patch/fix)


3

I'm pretty sure you can just pass in the fieldname the row and column like $data['field_id_X'][rows][new_row_1][col_id_1] = 'row 1'; $data['field_id_X'][rows][new_row_2][col_id_1] = 'row 2'; Just increment new_row_x as needed and match up your col_id_x numbers


3

Did you mark the Grid field as searchable after creating entries? If so, you need to re-save those entries in order to populate the exp_channel_data table with searchable data, which Low Search in turn uses for its collection index.


3

There is no no_result variable or condition for grid. Use total_rows instead. {if store_telephone_data:total_rows >= 1} ... {if:else} <td>N/A</td> <td>N/A</td> {/if}


3

Let me show you how the parser will parse that code before Stash tries to capture it as a list. I'll assume your relationship field only allows you to select a single person: {!-- first grid field --} {stash:people_bio_override}Person 1 biography {/stash:people_bio_override} {stash:people_director}Person 1 director{/stash:people_director} {stash:people_name}...


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