• Resolved atkulp

    (@atkulp)


    I have a custom post type and I also override the permalink generation for this type. I just noticed recently that it seems to not understand how to deal with this type. It’s not using query parameters translation plugins. Any ideas?

    It looks like the URL https://www.vrvoyaging.com/oneiric-masterpieces-paris/ is not part of this site or is not based on standard WordPress content types, therefore there is no data available to display.

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Hi there @atkulp,

    Thanks for reaching out. If you’ve overriding the permalink generation for your custom post type I suspect this is the cause of the error. I’ll need to check this myself, but it Site Kit isn’t detecting that any URLs from your custom post type are part of your WordPress install then the notice you’re encounter is normal at present. You can however find out more details of this particular URL by visiting the Analytics platform directly, just not within the Site Kit dashboard.

    We also have some information on the plugin website in relation to this error.

    I’ll report back to you here once I have more information on this, after checking overwriting a permalink generation for a custom post type or checking this with the team. Thank you!

    Plugin Support James Osborne

    (@jamesosborne)

    Hi @atkulp,

    Thanks for your patience on this. I’ve been testing out various CPT implementations, while also defining public and show_in_rest arguments, without encountering the error you’re facing.

    Can you share what you used to override permalink generation and I’ll try to recreate this and test on my side?

    Thread Starter atkulp

    (@atkulp)

    I’m using the CPT UI plugin. My custom post type has a rewrite set like this:

    
    $args = [
    		"label" => __( "Apps/Reviews", "darknews-pro-child" ),
    		"labels" => $labels,
    		"description" => "",
    		"public" => true,
    		"publicly_queryable" => true,
    		"show_ui" => true,
    		"show_in_rest" => true,
    		"rest_base" => "",
    		"rest_controller_class" => "WP_REST_Posts_Controller",
    		"rest_namespace" => "wp/v2",
    		"has_archive" => false,
    		"show_in_menu" => true,
    		"show_in_nav_menus" => true,
    		"delete_with_user" => false,
    		"exclude_from_search" => false,
    		"capability_type" => "post",
    		"map_meta_cap" => true,
    		"hierarchical" => false,
    		"can_export" => true,
    ======>>>>	"rewrite" => [ "slug" => "review", "with_front" => false ],
    		"query_var" => true,
    		"menu_position" => 5,
    		"menu_icon" => "dashicons-location-alt",
    		"supports" => [ "title", "editor", "thumbnail", "excerpt", "trackbacks", "custom-fields", "comments", "revisions", "author", "page-attributes" ],
    		"taxonomies" => [ "category", "post_tag", "app_language", "app_genre", "review_supported_headset", "play_areas", "post_status" ],
    		"show_in_graphql" => false,
    	];
    

    Does that help? I’m still learning how to customize my WP instance so if there’s a better way to do this, I’m ready to learn!

    Plugin Support James Osborne

    (@jamesosborne)

    Hi @atkulp,

    Thanks for the update. I’ll take a look and see if I can recreate the same based on the same plugin and arguments.

    Does that help? I’m still learning how to customize my WP instance so if there’s a better way to do this, I’m ready to learn!

    There may be nothing wrong with how you’ve added your custom post type, or there could be something else impacting Site it not detecting the related URLs as part of your WordPress site. If you wish to perform additional testing you may wish to manually create a custom post type, or create a test CPT using another plugin, and then using the Site Kit admin toolbar on any of your CPT URLs and clicking on the .

    I’ll test the same plugin you have in use and back to you at some stage today. Thank you!

    Plugin Support James Osborne

    (@jamesosborne)

    Thanks for your patience on this. I’ve created a custom post type using the Custom Post Type UI plugin with the same settings as your own. In my case I don’t encounter the same error.

    As I suspect this error you’re encountering may be as a result of a multi plugin conflict, or another plugin impacting your CPT, I’m happy to use the same CPT you have set up and test this further. The same plugin as an export option, so if you want to share your own settings I can test this on my own site set up to test this further.

    Along with sharing your CPT settings please share your Site Health information so I can check for anything else which may be impacting your CPT.

    Note also that the error you’re seeing doesn’t mean any CPT URLs are not being tracked by Google Analytics. It’s only the detailed page stats.

    Thread Starter atkulp

    (@atkulp)

    Thanks for taking the time so far. I’m still working on this, but it’s between some other things. I hope to reply in the next day or two.

    Plugin Support James Osborne

    (@jamesosborne)

    No problem at all, take your time. I’ll keep an eye out for any updates. You may wish to also test created other CPTs, using different methods, including without plugins. If creating a test CPT you can then check do you see detailed page states for any page with a CPT endpoint.

    Plugin Support James Osborne

    (@jamesosborne)

    Hi @atkulp,

    just following up with you to check whether the same issue persists if you manually create your own CPT, or whether you’re been able to tweek your CPT settings before then checking individual CPT content types for detailed page stats?

    Plugin Support James Osborne

    (@jamesosborne)

    As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘“URL is not part of this site” message’ is closed to new replies.