Am I trying to make this do something its not meant to do?

  • Resolved sock2me

    (@sock2me)


    7 years, 10 months ago

    Forgive me if this is a dumb question, but I need a page on my site for each of the 50 states. So I downloaded your plugin and created a ‘state’ custom post type. Then I create a series of fields specific to this post type using Advanced Custom Fields Pro. All is well, when I go to the new post type I see all my lovely empty fields ready for content.

    Then I purchased the CPTUI Extended plugin because I thought this would help me create a page template I can use to display the post’s content….But in reading the instructions, I’m confused – do I still have to create a normal Page for each of these to get the data to show using the shortcode? I’m confused, obviously –

    Can you push me in the right direction? Seems a huge waste of time if I still have to create a Page, drop the “Oregon” shortcode onto it. Why use a Custom Post type at all?

Viewing 1 replies (of 1 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Good day to you,

    Definitely looks like there’s a small amount of confusion going on, but that’s ok.

    The amount of work involved is really going to depend on how you handle things. If you’re using a shortcode for each individual state, then it definitely feels like it’d just be better to use the single post view for the post type instead. That would use the single.php template from your theme, if no more specific template file is found. However, if you were to make a page named “States” or whatever you choose, and then use the Extended shortcode builder to query for all of the states, then you’d be good to go, generally speaking. The one page would then query for all the states you have published, and use the CPTUI-Extended template for the given shortcode, and display a generally generic quick layout for each. A custom post type for this type of thing is still a good idea, in my opinion, as it keeps your content types separated in your admin area.

    To better clarify what CPTUI-Extended is for, I’ll give the following analogy. With the base free Custom Post Type UI, we created a plugin that provides form fields to fill out to choose and save parameters to pass into the register_post_type() and register_taxonomy() functions, so that you don’t have to. With CPTUI-Extended, we took that same idea of providing a UI, but this time we applied it to collecting arguments for custom queries using WP_Query. Both require zero coding from the user, but do different things. The first will register things for you, the second will query and “generically” display for you.

    If I confused you more and you need some better explanation, opened up new questions for you, or missed any part, let me know.

Viewing 1 replies (of 1 total)
  • The topic ‘Am I trying to make this do something its not meant to do?’ is closed to new replies.