unable to pull in Pages or CPT

dev.xiligroup is being renovated › Forums › Other plugins › unable to pull in Pages or CPT

Tagged: , , , , ,

This topic contains 0 replies, has 2 voices, and was last updated by  Anonymous 10 years, 1 month ago.

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • November 29, 2011 at 21:58 #3032

    Anonymous

    have you test with page_id=2 instead p=2 as in url query for page ?

    November 29, 2011 at 22:02 #3033

    Anonymous

    sorry, I just noticed that, and tried this which worked:

    [xilipostinpost query='page_id=2' showcontent=1 showexcerpt=0]

    thanks

    how do I get CPT to work?

    November 29, 2011 at 22:08 #3034

    Anonymous

    WHAT is C.P.T. ? cross portal theme ? ;-)

    November 29, 2011 at 22:17 #3035

    Anonymous

    Custom Post Types

    November 30, 2011 at 7:22 #3036

    Anonymous

    Example as in url with CPT named xilifunctions

    https://dev.xiligroup.com/?xilifunctions=function-xi_postinpost

    https://dev.xiligroup.com/?cat=393&post_type=xilifunctions

    very easy to see if permalinks is not active ;-)

    December 2, 2011 at 21:09 #3040

    Anonymous

    Sorry, it’s still not clear to me how to insert a Custom Post Type using a xilipostinpost shortcode. What are the query parameters? Can you please provide an example? Thanks.

    December 3, 2011 at 9:54 #3041

    Anonymous

    Queries are well documented in http://codex.wordpress.org/

    example for current post (p) : ‘p=17’

    example for custom post type (CPT) with name animals and searching one post with slug yellow-cat : ‘animals=yellow-cat’

    example for CPT sharing taxonomy category with current post : ‘cat=27&post_type=animals’

    Technically CPT seems to be an amazing solution but don’t forget that in data-model approach and query point of view it can be a nightmare if the preliminary study is no well done.

    Hope that help to fin the road ;-)

  • Author
    Posts
Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.