Hot answers tagged

11

Use the EllisLab Playa & Matrix Importer


6

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

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

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

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

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

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

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

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

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 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}...


2

In your example code this: {video_gallery:product search:status='wall'} ... is theoretically telling the relationship field to only display entries which have a custom field named status with a value of "wall". (Although Relationship field tags do not actually support the search parameter - see supported parameters.) If you're talking about the status as ...


2

One way to do this. You add a grid field for the heading value, then when you input data ensure that field is only present in the first row of a group. The template code would then go something like this: Lets say your grid name is sport_grid, and the grid has two field, grid_heading and grid_item {sport_grid} {if sport_grid:sport_heading}<h1>{...


2

Can you not just use the standard file field and set up a folder for backgrounds? Your client can then either select an already-uploaded image from the list of files, or upload a new one. You can restrict this field to one folder so there's no room for confusion and have it as a field in your pages channel. This way you don't have two separate strands to ...


2

Try this: {organisation} {organisation:related_organisation:title} {organisation:related_organisation:categories} {organisation:related_organisation:category_id} {/organisation:related_organisation:categories} {/organisation} ...


2

If your conditional is checking if it is > 0 this would work fine as a replacement: {if foo:total_rows != ""} You have more than 1 row. {if:else} You have 1 row. {/if}


2

Shortly after posting this - I think I found the problem. It appears the _updates_relationships_for_grid() function didn't fire in the ud_270.php upgrade process... no idea why though since the upgrade didn't fail or error at any point. Having manually executed the SQL necessary on this function, it looks like it's working now.


2

You can not natively upload all the files at once with grid. But you can individually select them for each cell in the grid


2

This will be fixed in the next version. In the meantime, if you make sure all columns are not required, you can avoid the issue, too.


2

I just ran into this. All my grid fields were set as required, so leaving any field empty when saving removed the images. Adding data to all fields (including images) and it saved ok.


2

So it looks like the issue was with the flexslider zip. I looked at the demo included in the zip and it has the same issue. I resolved the problem by grabbing the js file from the live demo page.


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