Skip Navigation

[Resolved] Custom type converted from Pods not showing on front end using template

This support ticket is created 4 years, 1 month ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: 

This topic contains 11 replies, has 2 voices.

Last updated by brianW-8 4 years, 1 month ago.

Assisted by: Shane.

Author
Posts
#1801763

I have a site I am converting from using Pods. I've converted the custom type and am able to access the type and all custom fields in the editor. I can get templates to display on the front end using a shortcode insertion, but I can't seem to set it so the single item pulls up when calling the /type/item URL. (i.e. the type is "campus" and the item is "my-college", when I call site.com/campus/my-college" I get nothing but a blank page, even after I have created a content template using toolset and assigned it in the dashboard.

This method seems to work for NEW types I create from scratch, just not converted items. There are more than 500 custom items, so ideally I don't want to create a new type and start from scratch.

Any ideas on why the converted items would not show using the permalink structure?

Thanks

#1801983

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Brian,

Thank you for getting in touch.

Can you provide a little information on how you converted the Pods CPT to Types CPT?

Once you've provided the steps you did we can take it from there.

Thanks,
Shane

#1803453

I followed the directions here: https://toolset.com/course-lesson/convert-existing-custom-types-and-fields-to-types-control/

I could see the custom types in the Dashboard, so I didn't need to do the first part, "Converting custom post types and taxonomy". I created a field group for the type, then added all the custom fields to the group.

This seems to have worked because I can see all the fields in the template creator and can create the template without a problem. In the block editor, it even pulls the data from the custom type with no problem. The issue is when I go on the front end to a specific item (e.g. /campus/virginia-commonwealth-university) the page is blank, the template I created using the editor does not show on this page.

As I mentioned, if I create a new custom type, use the template editor and then go to that permalink, it shows up fine. So somehow, there is a disconnect for the converted custom type.

#1803503

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Brian,

Thank you for the details.

Would you mind allowing me to have admin access to the website as well as the name of the post type with the issue so that I can have a further look at this for you ?

The private fields have been enabled for your next response.

Thanks,
Shane

#1806017

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Brian,

I'm able to clearly see the issue. However I will need to debug further.

Would you be ok if I installed the duplicator plugin to grab a copy of the site to test here locally?

Thanks,
Shane

#1806167

Sure thing. Go for it.

#1806379

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Brian,

Thank you, the issue was being caused by the Pods plugin.

Once i've disabled the plugin i'm able to see the content on the frontend.

You should now be able to continue working on your content template for the campuses post type.

Thanks,
Shane

#1806519

Then maybe I'm doing something else wrong. ... because I see the page rendering now, but the data from the custom fields still isn't showing.

See hidden link ... It should show not only the title, but I've added a few custom fields in as well. None of those are rendering

#1808821

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Brian,

This is because you added your content to the custom fields.

It should be noted that the custom field data won't automatically show up on the frontend.

You will need to create a content template for them to start showing up. Here is a link to our documentation on how to create a content template.
https://toolset.com/course-lesson/creating-templates-to-display-custom-posts/#how-to-design-templates

Please let me know if this helps.
Thanks,
Shane

#1808837
2020-10-12_11-40-50.png
2020-10-12_11-37-01.png

I don't understand. Isn't that what I've done? I have already followed those instructions, I thought.

I created a template, it shows in the Dashboard "TEMPLATE" column. When I look at the template in the editor, it shows the blocks I've added, with data. The only place it's not showing is the single-item page, which I thought was what the template was supposed to do.

For example, there is a custom field called "adoption_resources" that has been added to the template. It has content for virginia-commonwealth-university. It's not showing on the front end.

See screen shots

#1808857

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Screenshot 2020-10-12 at 10.48.40 AM.png
Screenshot 2020-10-12 at 10.47.38 AM.png

Hhi Brian,

On the post itself, you didn't assign the content template to it. See Screenshot.

Currently it is set to none. To ensure that all your posts under the campus post type gets assigned the content template you will need to click the Apply to all button. See Screenshot

Please let me know if this clears things up for you. Once you have done this you should see your content showing up.

Thanks,
Shane

#1808887

ROCKSTAR!

Thanks so much! Seems like I have it now.

My issue is resolved now. Thank you!