Hi, with your help I upgraded to the latest ACF this week. Now, a “buy now”
affiliate link URL is not showing.
I have a Resource content type that features six custom fields. Most are straightforward text-entries. The last three are related to the BUY NOW link for AMazon affiliate.
In the backend, I have all 6 custom fields showing and the URL is present. That is:
purchase_details = 1
purchase_details_0_purchase_website_name = Amazon US
purchase_details_0_purchase_web_address = http://www.amazon.com/gp/product/0643097856/ref=as_li_ss_tl?ie=UTF8&camp=1789&creative=390957&creativeASIN=0643097856&linkCode=as2&tag=laurakammerme-20
But in the ACF area, three custom fields are shown, but “Purchase Details” is, for lack of better term, “grayed out.” The words are there, but there is no entry field. This is where I would normally write Amazon and enter the buy now URL. And still, the URL is present in the custom fields because this was loaded before the update.
It’s as if some add-on may be missing (but I can’t imagine what that is? I didn’t code the site, I’m a content person).
The page source reveals:
<div class="clear"></div> <div class="submeta"><hr /> <h3>DETAILS</h3> <div class="contributorFloat"> <div class="resourceBox"> <div class="resourceTitle">Author:</div> Richard Thomas, Sarah Thomas, David Andrew and Alan McBride </div> <div class="resourceBox"> <div class="resourceTitle">Copyright:</div> 2011, 2nd edition </div> <div class="resourceBox"> <div class="resourceTitle">Publisher:</div> Csiro </div> <div class="resourceBox"> <div class="resourceTitle">Buy Now:</div> <ul> <li><a href="" target="_blank"> </a></li> </ul></div> </div></div>
How can I get that ACF for buy now to start showing and turn it back “on” on the front end?
Sounds like you have upgraded from ACF v3.x to v4.x
This transition introduced a new way to create field types. v3 field types are no longer compatible with v4 (this is heavily documented).
I believe that your website contains a ‘buy now’ field type which was built from v3, but not for v4.
My advice would be to contact the dev team from the build and ask them if this is the case. If so, I would hire them to rebuild the field into a v4 compatible version. This is a pretty simple task as there is a starter kit available on github and documentation on the resources page.
Hope that helps.
You must be logged in to reply to this topic.
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
© 2019 Advanced Custom Fields. Subscribe