Lara Schenck

@chee: You are very welcome! And totally right – helping with the docs has been on my back burner, could definitely be some improvements there. Will move it up in the list!

Hah no worries! Thanks for correcting ??

gear_to_deal is a relationship field within Gear where Deal is the custom type being connected. To be honest I can’t entirely remember how I can up with the get_field() business up there, but here’s another example for a repeater field:

post.readings = relationship field name

{% if post.readings %}
	<h4>Resources</h4>
	<div class="list--minor">
		{% for post in post.readings %}
			{% set post = TimberPost(post) %}
			{% include 'teases/_tease-resource.twig' %}
		{% endfor %}
	</div>
{% endif %}

I believe TimberPost is necessary to access the entire Post object. That code should work if it’s a straightforward repeater. And the include is just including markup accessing what’s in post e.g. {{post.date}}, etc.

Let me know if that does the trick!

Essentially, yes – I was using a WYSIWYG custom field through Advanced Custom Fields, but I’d imagine it acts the same way. wpautop isn’t run on the text area field type, so I think that’s what fixed it.

Also – that’s using the raw embed code, not the plugin.

Oh, I did! I believe it was from wpautop which happens even when using the ‘text’ tab of the WYSIWYG editor. I was using ACF and used a text area field instead of the WYSIWYG to avoid the issue. In other words, it seems that wrapping the embed code in a <p> causes the error.

I’m having the same problem. Did you figure anything out?

Solved! Turns out you can’t use get_field() within get_field() and I thought I needed to for the relationship field for some reason. The correct way to loop through a relationship is like this:

{% for item in post.get_field('gear_recommendations') %}
	<div class="item">
	       <h4>{{item.gear_title}}</h4>

		{% set deals = TimberPost(item.gear_to_deal) %}

		{% if deals %}
			<h3>Deals!</h3>

			{% for deal in deals %}
				<p>Related deal: {{deal.title}}</p>
			{% endfor %}

		{% endif %}
	</div>
{% endfor %}

Actually, it looks like checking Homepage does the trick. Not sure why that is.

Did you figure anything out? I am having the same issue and using Bones also.

I had the same issue and you seem to be right. I was using a custom field to upload the image and the same thing was happening. Thanks!

np ??

Try disabling all plugins to make sure there isn’t a conflict – especially anything like WP Super Cache.

Actually that won’t work – this is way harder than it should be. Seems like there’s some style called in a WP core stylesheet that is very hard to override. I’d like to figure this out as well – will post a solution when I do.

Have you tried searching the theme’s main style.css for background-color: #FFFFFF? Then change that style in the child stylesheet.

Add this to your child theme’s style.css to hide the white boxes.

.container, .sf-menu li a, .sf-menu li li, .sf-menu li li li {
    background-color: none;
}

Cool site, btw.