Appears so. I’m gonna mark this solved, and, again, thanks for all your help.
Update:
I don’t know why, since it didn’t seem to matter last time, but changing the ruleset for which templates are associated with the custom field (changing from AND to OR) seems to have removed the custom field from being associated with the media library.
The question, I guess, is why.
Hi John,
Thanks for the reminder on my ruleset. I think I set it that way trying to figure out this issue on my own and just never set it back.
As far as your other questions go, for ACF I’m running nothing but the base free version to set up a proof-of-concept site. No add-ons at all; and these two page templates are all that reference the custom field.
For my plugins, I’m using a fairly basic (I imagine) setup:
Advanced Custom Fields v4.4.3
Autoptimize v1.9.4
BJ Lazy Load v1.0.6
Breadcrumb NavXT v5.3.0
HTML Page Sitemap v1.2
RICG Responsive Images v3.0.0
TinyMCE Advanced v4.2.5
User Role Editor v4.20.1
Wordfence Security v6.0.20
Yoast SEO v2.3.5
No combination of turning these off seems to affect the issue.
Hi John,
I’m using ACF version 4.4.3.
My location rules are pretty simple. I’ve got a two-part rule that states that the custom field should only be shown if the Page Template is equal to one of two page templates I’ve created. Everything else on the creation screen is pretty standard, and you can see it all in a screenshot here.
Thanks for your help.
