**Tell us what you are trying to do?**
I'm working on a site that's currently using ACF (and also other plugins like Custom Post Type UI and Post Types Unlimited). There's a custom post type with about 200 posts and over a dozen fields (using categories and tags, too). I would like to clean things up a bit and start using Toolset instead of the post grid/carousel block in the Pro version of Kadence.
I need to set up pages that show things like:
1) A page with a list of all posts in one particular category (linked to their individual pages)
2) A page with lists of posts that have each specific tag (linked to their individual pages)
3) The info for one post
I've been setting up Content Template for #3 above, but things feel a bit patchwork, and I'd like to do this the right way. Initially I was using the ACF fields, but I'm struggling to get certain things to show up (like links and images). If I can keep ACF, great. If not and I have to recreate it all in Types, it would be great not to have to recreate all the posts.
It feels like this should be something simple to do and I'm struggling more than I should.
**Is there any documentation that you are following?**
I've tried following various posts in the forum, but nothing specific at the moment. To start out, I tried turning off the other plugins and just using the existing CPT with Toolset.
**Is there a similar example that we can see?**
I reversed my revisions, turning off Toolset on the live site so you can see what I'm trying to recreate.
And by activating the ACF fields in Toolset Settings/Front-end Content/Hidden custom fields I was able to grab the URLS (and link them as needed).
I'll update you about what I still need once I get a chance to look through. Wanted to get this post written to help you avoid extra work that wasn't needed.
And it shows the proper preview of the organization name in the editor, but on the site itself it just says "Visit website" in the link. Is it possible to use a shortcode like this within an <a> tag?
I was able to recreate everything I did on the staging site on the live site (couldn't push the staging the way it was set up). So what I did is now live on hidden link.
(I haven't used Toolset in a LONG time -- and I am VERY impressed with the changes!)
There are a few remaining issues I'd like to solve still.
1. The link for "Visit OrganizationName website" is still not working right.
2. I got the logos to display on the individual organization pages using the shortcode, but it's kind of slow to load. Is there another way to do this to make them load faster?
3. I'd like to have the styling for the list of organizations generated by the loop in the Toolset View (like hidden link for example) look the same as what's generated by the Archive (like hidden link), but I'm not sure where to go to adjust that.
4. I'd like to know how to generate a list of topics (a taxonomy) using a loop in a Toolset View (I did it manually since I couldn't figure that out) for here: hidden link
1. if you output fields with a types shortcode the field slug is used, but the wpv-post-field shortcode outputs any custom field (not just types fields), and uses the post meta key. Types custom fields are stored in wp_postmeta using a key that has a 'wpcf-' prefix, so a types field with slug 'website' would have a meta key 'wpcf-website', which is what you need to use with the wpv-post-field shortcode.
2. I'm not sure what exactly you are doing here to commentate. Types image fields are stored as URLs, I'm not sure if ACF stores images the same way. Are you using the legacy editor or the block editor? With the block editor you can output individual images with the Image block, but you also have the Gallery block and Slider block available, and these would depend on the images being stored in the expected format (i.e. the image urls).
3. Again, I'm not sure if you are using the legacy editor or the block editor. If you have set up the output for both the View and the archive the same way and the appearance is slightly different, does the theme load different styles on the different pages?
4. The new block editor for Views only works with Views that query and display posts. But you can still use the legacy editor to create Views that query and iterate over taxonomy terms. When you create a new legacy View at Toolset > Views in the content selection you would indicate this is a View to query taxonomies, specifying which taxonomy.
With either Views or Blocks plugin installed (they are essentially the same, except for the default settings) go to Toolset > Settings > Editing Experience, and there you can choose whether you want to use the legacy editor, the block editor, or have both available.
The topic ‘[Closed] Switching over to Toolset from ACF’ is closed to new replies.
