12
For some reason sometime the update is applied but EE does not change the version number. I'm not even sure on which side the error happens, but setting the version number to 4.5 in exp_fieldtypes should solve your problem.
6
I don't know if you already have a anwser yet. But I had the same problem and I. I want to enable pagination within a Playa loop.
You need to do 2 things to enable pagination in a Playa loop.
Override the default disable of “categories|category_fields|member_data|pagination”.
Put var_prefix in your Playa tag and pagination tag.
You did a good override of ...
5
That’s an error in the documentation, and we’ll get that fixed. :child_ids only supports filtering entries with the following parameters:
var_id
var
element_id
field_id
field
col_id
col
row_id
child_id
parent_id
If you need anything else, and you should just use a tag pair:
{event_related_media
limit="2"
status="Archived"
channel="video"
...
5
It's a pretty simple operation, since they are stored very similarly.
First, backup your database. Then, run this code in a PHP-enabled template:
<?php
$playa = ee()->db->query("SELECT * FROM exp_playa_relationships");
foreach($playa->result_array() as $rel)
{
$data = array(
'parent_id' => $rel['parent_entry_id'],
'...
5
Always read the manual Steven!!! http://docs.pixelandtonic.com/playa/using/converting/relationships.html
5
So far I've discovered and fixed one case and will add more here if discovered.
File: mod.playa.php
Line: 550
FROM
$sql = 'SELECT DISTINCT(rel.child_entry_id) AS entry_id
TO
$sql = 'SELECT DISTINCT rel.child_entry_id AS entry_id, rel.parent_entry_id, rel.parent_field_id, rel.parent_row_id, rel.parent_col_id, rel.parent_var_id, rel.rel_order
3
You'll need to write a custom fieldtype to achieve this - I can't think of any existing fieldtypes that could accomplish this for you.
So in your fieldtype, you'd query exp_playa_relationships for all parent_entry_id's where where child_entry_id was equal to the entry_id associated with ee()->session->userdata('member_id'). (Not sure how Profile:Edit ...
3
Reposting here the solution that I posted on Devot:ee to the same question:
<ul>
{exp:stash:get_list name="location_list"}
{if 0 == {exp:stash:list_count name="checked_locations" match="#^{entry_id}$#" against="entry_id"}}
<li>{entry_id}</li>
{/if}
{/exp:stash:get_list}
</ul>
3
This is what the var_prefix="" parameter is for. Update your code like this.
{exp:channel:entries set="prod" dynamic="no" disable="pagination"}
...
{exp:playa:parents channel="api" field="cf_apis_related_product" var_prefix="api"}
<ul class="dropdown">
<li><a href="{path='{PROD_CHANNEL_url_title}/docs/{api:url_title}'}">{...
3
Good news, it should be a quick fix. All you need is to prefix your Playa variables with var_prefix parameter to differentiate the namespace from the Channel Entry variables, although you might have to use the full module tag:
{exp:playa:children field="item_colors" var_prefix="pl"}
"{pl:title}": "{title}",
{/exp:playa:children}
3
EE allows you to override control panel styling by adding a override.css stylesheet to the themes folder. So you could just add this rule within that stylesheet:
.playa-ss {width: 100% !important}
3
Are you trying to get the count of multiple playa entries for each matrix row? If so, you should be able to do something like the following, setting a different namespace prefix for matrix and playa to separate their tags:
{your_matrix_field_name var_prefix="mx"}
Matrix row {mx:row_count} of {mx:total_rows} total rows.<br>
{mx:...
3
In your channel entries tag, use the fixed_order parameter instead of entry_id.
3
Looks like a variable name conflict. You can use "var_prefix" when this happens. Try something like this:
{exp:playa:children channel="recipe" entry_id="{entry_id}" field="similar_recipes" var_prefix="related" }
{related:title}
{/exp:playa:children}
http://docs.pixelandtonic.com/playa/templating/module/children.html
3
Turns out the problem wasn't a parse issue after all. Playa disables categories by default so by placing a blank disable="" parameter on the {cf_feed_videos} tag it overrides this and re-enables categories for the related entries.
3
After some quick testing I'm pretty certain you can use the playa tag "total parents" and pipe that in as an orderby parameter. The playa children tag, as stated in their documentation "{exp:playa:parents} supports almost all of {exp:channel:entries}’ tag parameters", so it accepts orderby and sort parameters. So, the following should accomplish what your ...
3
This is why I buy Playa, from the relationship field docs :
Currently it is not possible to get the parents of a relationship field that is inside of a Grid field. You can also not use Relationships inside of a Grid field that does not store Channel data.
3
According to the docs http://ellislab.com/expressionengine/user-guide/add-ons/channel/channel_entries.html#search-field-name only fields of the type “Text Input”, “Textarea”, and “Drop-down Lists” are searched with this parameter.
3
You actually can search on playa fields if you've ticked the "Is field searchable?" for the field. I believe the title or entry id of the related field can be used in the search.
For example, both should work:
{!--with channel entries--}
{exp:channel:entries
channel="your_channel"
search:playa_field_name="an_entry_id"
}
{title}<br>
{/...
3
Probably the order is the order in which the relationships were created; this at least would be the case for the native EE-relationships. I assume with playa it is the same.
From the docs:
Ordering by a Relationship field will cause entries to appear in the
order the relationships were made, not based on any content from the
related entries.
3
Looks like your missing dynamic="no" parameter on the exp:channel:entries tag. However, it seems like you might be over complicating things as the exp:playa:children would work by itself if you pass a embedded variable with the entry_id of the parent to the embedded playa:children tag:
{exp:playa:children entry_id="{embed:entry_id}"}
3
I have resolved this by adding the option parse="inward" to the {exp:playa:parents} tag. So my code looks like below
{exp:playa:parents channel="article|blogs|calendar_events|contests|podcasts|videos" category="YOUR_DYNAMIC VALUE FROM PHP OR ANOTHER TAG" field="show" limit="24" parse="inward"}
// Do something here
{/exp:playa:parents}
The above code ...
2
This finally worked for me:
Tools > Data > SQL manager
Database Query Form
enter queries:
ALTER TABLE exp_playa_relationships ADD parent_var_id INT(6) UNSIGNED AFTER parent_row_id, ADD INDEX (parent_var_id)
ALTER TABLE exp_playa_relationships ADD parent_is_draft INT(1) UNSIGNED NOT NULL DEFAULT 0 AFTER parent_var_id
Submit
2
I've done this before with NSM Transplant. But I've been slowly removing it in favor of Stash. This question inspired me to finish the process with this template, so thank you!
First off, I think there might be a workflow problem with your question. I'm not sure how often people will be updating events but from what it sounds like is that when someone wants ...
2
In my
themes/cp_themes/default/css/override.css
file I added the following to control the horizontal sizing of the Playa single-select drop-down field to have up to 300px width. Would love to hear of a better method.
/* Make the Playa single select drop down fields wider.
*
* From http://expressionengine.stackexchange.com/a/17327/2436
*
* The ...
2
I'll quote the docs here:
Please note that only non-hidden and variables with early parsing disabled show up in the variable list in the Publish Form.
So, make sure the vars you want to select are not hidden and have early parsing disabled.
2
You can use {channel_short_name}:
{if channel_short_name == "channel_a"}
...
{if:else}
...
{/if}
2
I would suggest you use EE categories for your product categories rather than channels. Each product tile is an entry in the products channel, and each tile is assigned to one or more categories which determines which product grid it shows up on. The index/category page is then just a list of the categories in your product categories group, and the product ...
2
Sounds like the var_prefix parameter is your friend in this case!
2
We just came across a very similar issue where an Assets tag pair was not being parsed in one environment but was working fine in others while single tags were working fine everywhere. The solution for us turned out to be that we had to bump up the pcre.backtrack_limit value in the php.ini to 1000000 on the server where the tags weren't being parsed. It ...
Only top voted, non community-wiki answers of a minimum length are eligible