Cornerstone not loading for CPT 'Product'

[RubberDuckers]

It seems as soon as there’s any content added, it doesn’t load in this CPT.

I have 2 CPTs set up exactly the same, one is ‘product’, the other ‘service’.

Each have a single layout and archive layout. Within the single layout is ‘the content’ element. Cornerstone is enabled on both CPTs to add into that ‘the content’ section.

‘Service’ works perfectly as expected but ‘product’ always gives me the ‘can’t load iframe’ error.
I’ve had the same before when using ‘product’ as a CPT before.

I can still edit in the skeleton mode and when saved, it appears on the front end.

There’s no eCom on site.

Any ways around this so the backend is editable?

[prakash_s]

Hello @RubberDuckers,

Thanks for writing to us.

It seems that you have installed the WooCommerce plugin or that you have previously installed it. Please note that the WooCommerce plugin creates a custom post type called “Product”. Creating a CPT with the same “Product” name or slug will create a conflict. This is why it is highly recommended that you choose a unique name that may not be used by the plugin when creating a custom post type. I would suggest you please change the custom-type slug from a product to a different post-type slug.

Hope it helps
Thanks

[RubberDuckers]

It doesn’t seem that way at all, it’s a newish build and woo nor any ecom has never been on site.
And the client offers ‘products’ and ‘services’, so semantically it needs to be ‘product’ as the post-type slug.

[ruenel]

Hey @RubberDuckers,

We would love to check your site. Please provide us with your WP Access. You can create a secure note in your next reply with the following info:
– Link to your site
– WP login URL
– WP username
– WP password
– WP Administrator Role
– Confirmation that we can access and make changes to your site

To know how to create a secure note, please check this out: How The Forum Works

Best Regards.

[RubberDuckers]

Sure thing

[tristup]

Hi @RubberDuckers,

I have checked and found the issue you described here. There might be some different reasons behind your issue, I would like to suggest troubleshooting the following common issue to help us to recognize the reason.

1.Theme Related Issue
2.Plugin Conflict
3.Theme Update related issue
4.Child Theme Related issue
5.CSS/JS Customization
6.Disabling Cache
7.Disabling CDN
8.Permalink

If you discover that an issue is coming from a custom code or 3rd party plugin, kindly consult with a developer or contact the plugin author. Please note that we do not provide support for custom codes and 3rd party plugins unless you are subscribed to One. If not subscribed, kindly consult with a developer or contact the plugin author.
Please note that we do not provide support for custom codes and 3rd party plugins unless you are subscribed to One service.
If none of the above helps, please copy your live site to a staging server so we can troubleshoot freely without breaking your live site.
And give us access in the secure note including:

– WordPress Site URL & Login URL
– WordPress Admin username/password

To create a secure note, click the key icon underneath any of your posts.

Thanks

[RubberDuckers]

Hi there,

It’s on a staging server so no CDN. And not live, so you can take a deeper look.
I deactivated all plugins, switched to the main Pro theme.

All the other CPTs, their layouts and archives seem to work fine in the visual builder, but Products (layout and single) don’t. The layout is fine if you’re previewing a product that doesn’t have any content in yet, but as soon as you add content it then gives the error as said.

Before any content

Adding content (content should appear below the ‘benefits/faqs/etc’ nav):

Saved and refreshed:

Deleting and trying again takes to first screenshot.

[RubberDuckers]

So a follow up. I tried a bunch of debugging as mentioned above.
I then also duplicated the product CPT in ACF but called it ‘not-services’ instead of ‘product’.
Then created a post, assigned a copy of the product single layout to it (so it’s all the same information/set up) and it works perfectly as expected.
So it feels that this must be the ‘product’ post type.
Which I thought initially as I’d had it happen on another site when using ‘product’ as a CPT.

Maybe you can try it on a fresh install to see if it is just the default behaviour?

But it would be great to have a solution for this as it’s currently the only thing holding this site from going live!

[RubberDuckers]

OK a follow up with a potential workaround (though it’s really not ideal and kinda confirms the above about ‘product’ not working).

I have Permalink Manager Pro on there, so I’ve set 'not-service’s permalink to /product/post-name and that works and loads in the builder… so Cornerstone mustn’t like ‘hard coded’ permalinks of ‘product’.

I can move over the ‘product’ posts to this new one and then just rename it in the menu and the permalink manager, so even though at the core it won’t be ‘product’ as the CPT it will visually everywhere else.

But I think it’s still worth looking into.

[RubberDuckers]

ACF flags ‘p’ as a reserved term, but not ‘product’ so I don’t think it’s ACF either. Are there any checks Cornerstone does (potentially due to the Woo integration for needing a separate type of single layouts for ecom?

[RubberDuckers]

It also seems that the archive URL can be products, just not the post type (as I’ve got that set in my ‘workaround’) and it’s loading the builder now for the archive fine.

[marc_a]

Hey @RubberDuckers,

It is because Cornerstone reserves the product post type only for WooCommerce so regretfully, you have to rename or create a post type other than product .

Hope that helps.

[RubberDuckers]

And there’s no function or anything that can be put in the child theme that can overwrite this?

[marc_a]

Hey @RubberDuckers,

I’ve asked our developer about the filter but there’s no current filter to override it. The good thing is, this will be fixed in the upcoming release.

Thank you.

[RubberDuckers]

Ah amazing thank you. Is there an ETA on the upcoming release? Just to see whether it’s worth completing the workaround or being able to stick with the initial way.

[marc_a]

Hey @RubberDuckers,

Regretfully, we don’t have any ETA for the upcoming release. I highly suggest that you check our updates here from time to time.

Thank you.

[RubberDuckers]

Thanks - I do check those updates religiously so I’ll keep an eye out.

I’ve moved the posts over to the workaround way for now and it’s working perfectly, so at least there was a solution in the meantime even if not quite perfect.

[marc_a]

Hey @RubberDuckers,

That’s great and you’re most welcome!