“search:” parameter to constrain channel entries output by using a custom field (EE6) - question

Can you confirm the variable is working ok? WIll {admin_user_name} output correctly? If yes, then maybe it is a parse order issue? maybe put the channel entries tag in an embed and pass the admin name through the embed.

The search only happens in certain fields. Is the admin_user_name field a custom text field?. Also, you could try to do something like this: {exp:channel:entries channel='Administrator' search:admin_user_name="{segment_3}” limit=”1” dynamic=”no”}

@5BYFIVE Creative : Thanks.

1) I confirm that {admin_username} outputs correctly, depending on the third segment of the url, i.e :

{preload_replace:admin_username="{segment_3}”} {layout='layouts2/_html_wrapper'} {if segment_4 } {redirect='404'} {/if} {admin_username} {!– the variable admin_username gives me the correct admin username depending on the url query parameter –}

2) I read EE6 documentation about embed and looked at all the examples I could find online. For the sake of it, I just tried :

{embed='admin/details' admin_user_name='{segment_3}’} {layout='layouts2/_html_wrapper'} {if segment_4 } {redirect='404'} {/if} {admin_username}

but as expected, this led to :

Error

You have caused a template loop due to improperly nested sub-templates (‘admin/details’ recursively called)

Template load order:

admin/details
admin/details
admin/details

@jelle

• admin_user_name is a custom field . There is nothing (https://docs.expressionengine.com/latest/channels/entries.html#searchfield_name) suggesting that the “search:” parameter cannot be used with a custom field (I toggled the “Include in Search” option for that specific field).

I tried :

{layout='layouts2/_html_wrapper'} {if segment_4 } {redirect='404'} {/if} {exp:channel:entries channel='Administrator' search:admin_user_name="{segment_3}” limit=”1” dynamic=”no”} {admin_email_address} {!– the field admin_email_address always gives me the value adonovan@gmail.com no matter what {segment_3} is –} {/exp:channel:entries}

The same email address is outputted no matter what.

Do you have any other suggestions I could try ?

Thanks a lot.

K.

Here are the 3 pieces of code in a more readable format :

https://www.codepile.net/pile/5Oaxkzda

Thanks.

K.

that’s weird. might it be that {admin_email_address} is getting confused? what happens if you put {entry_id} in there? so like this:

{exp:channel:entries channel='Administrator' search:admin_user_name="{segment_3}” limit=”1” dynamic=”no”} 
{entry_id} 
{/exp:channel:entries}

Hi,

your exact code generates what is in the screenshot to this reply.

Note that 24 is the newest entry id and 14 is the oldest entry id. (There are no other entry ids for this channel.)

This is extremely troubling.

Any other suggestions / workaround ?

Thanks.

K.