Meta Box

Peter, this is the code for the page.

{% set args1 = { post_type: 'repetitie-avond', posts_per_page: -1, orderby: 'date', order: 'asc' } %}
{% set posts = mb.get_posts( args1 ) %}

{% for post in posts %}
    <h2><strong>{{ post.title }}</strong></h2>
    <p>{{ post.content }}</p>
    {% set args2 = {post_type: 'muziek', nopaging: true, orderby:'none', relationship: {id: 'muziek-op-repetitie-avond', from: post.ID}} %}
    {% set muzieknummers = mb.get_posts( args2 ) %}

    {% set counter = 0 %}
    {% for muziek in muzieknummers %}
        {% set counter = counter +1 %}
        {% set post2 = mb.get_post( muziek.ID ) %}
        <p><a href="{{ post2.url }}">{{ post2.post_title }}</a></p>
    {% endfor %}

    {% if  counter == 0 %}
        Er is nog geen muziek voor deze avond vastgelegd. - no music yet - 
    {% endif %}
<hr />
{% endfor %}

Here is a short video of all settings involved: https://drive.google.com/file/d/1Ok9HploeRIkomw7uukIa7cuikxAFH1gN/view?usp=drive_link

Regards,
Eddy

Thanks Peter.

I noticed that in the first attempt I had set the post type to courses, instead of course. That was it.

I expanded the code to show thumbnail and post title. That worked nicely.
Then I added the condition to show only for coursecategory = training, that's where I step into a critical error.

{% set args = {post_type: 'course', nopaging: true, relationship: {id: 'student-results', from: user.ID}} %}
{% set courses = mb.get_posts( args ) %}

<div class="completed_courses">
{% for course in courses %}
    {% set coursecategory = mb.get_the_term_list( result.ID, 'coursecategory', '', ', ' ) %}
    {% if  coursecategory  is  'training' %}
   	<div class="course">
        {% set post = mb.get_post( result.ID ) %}
        {{ mb.get_the_post_thumbnail( result.ID, 'thumbnail' ) }}
        <p style="text-align: center;"><strong>{{ post.post_title }}</strong></p>
	</div>
    {% endif %}
{% endfor %}
</div>

Hopefully you can help me here?
Thanks!

I had set up the custom fields in a way that they were only visible in admin area to the Admin role, and let users edit in the frontend. But perhaps that's a conflicting idea?

I did many tests, and probably confused myself when I said the user could edit in admin area and not in frontend.
Anyway, I have now removed the setting that fields are only visible for the Admin role.
Now visible to the user and user can edit in the frontend.

So consider it solved.

Thanks Peter

I found it already, and expanded the code to my liking.

Peter, it happens only with 1 specific cpt, all other post types are working properly.
But you're actually right, it's caused by another plugin. Deactivating it solved it.
I'll contact them to act on the errors in the debug.log.

Thanks.

Hi Peter, thanks, that almost works.
It just, if post.fan_profile is empty, then the value of the most recent occurrence is returned.
How to avoid that?

Hi Peter,

With your help I managed to get it working.

Thanks a lot, regards.

Found it, I saw this thread: https://support.metabox.io/topic/custom-field-content-no-longer-editable-viewable-in-wordpress-admin-area