Using page wildcard that doesn’t affect other content..?

This topic is: not resolved

This topic contains 3 replies, has 2 voices, and was last updated by  chris.pilko 1 year, 9 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #166043

    Guil
    Member
    Post count: 5

    Hi there,
    New to pods, so please bear with me.
    More of a theory question, than a technical one.

    I understand Pods generally, but there’s a few things I can’t get my head around.
    If I set up a template for general pod pages, it works beautifully if the page uses wildcards like so: page/* .

    This way, the wildcard won’t interfere with any of my other content (there’s some WP pages and other content already). However, this throws in a pesky page/ into the url.
    To get the same result without the /page/, I figured using just a wildcard * for the page name would work – it does. But then every other page that already exists is assumed to be a pod page; doesn’t exist, and a 404 is shown for the content.


    So how can I (if possible) get pod pages to use a url like that without affecting other pages? … .com/myPodPage rather than having to stick in another word like so: .com/page/myPodPage

    Thank you.

    Harley.

    #166044

    chris.pilko
    Member

    @Harley:

    This is what the Pages menu is for in the Pods admin area. You can create nearly any page with nearly any structure you want using these pages:
    /my-pod-page (camel case isn’t recommended for URLs…)
    /some-stuff/more-stuff/even-more-stuff
    /detail-page/*

    #166045

    Guil
    Member
    Post count: 5

    Thanks for your response Chris,

    I was trying to make my ‘one-off’ pages work through a general_pages pod, so that I can use custom fields and file uploads and whatnot. If I use the pages tab for each page, I’ll need either A) a new Pod for every page, or B) hard-code the pages and not use any fields (columns).

    Perhaps (and probably) I’m looking at things from the wrong angle; please let me know your thoughts.

    Harley.

    #166046

    chris.pilko
    Member

    Harley:

    I’m not really sure what you’re trying to do. Can you post some more details? I can’t envision a use where you would use Pods, but have to have a new pod for every item.

    Pods real power is displaying a multitude of different items using the same structure: A portfolio, movie times, products, reviews, etc. This way you create a container (a Pod) with fields that hold your descriptive data, then create a presentation layer using pages and templates to display that information to your users.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

Wordpress Cloud Hosting