chickenkhurana

Getting the same issue. Plugin disabled for now but we really need this functionality

I did some more testing and found this:

1. this seems to be working for wordpress pages and posts. Works for classic as well as Gutenberg editor.

2. It does not work for custom posts (I use Pods) if they use Gutenberg. However, if you disable Gutenberg for custom posts, this starts working. The link to widget appears at the bottom instead of custom permalink on the right.

Will be grateful for any leads. Thanks in advance.

• This reply was modified 5 years, 9 months ago by chickenkhurana.

so in my case, whatever value i set in custom permalink, the content still shows only the standard permalink ??

I’m not sure because
1. adding anything under custom permalink makes no difference
2.existing content items are working fine, meaning their external links are as i had set them. However, they also don’t appear under custom permalink.

Okay never mind. I figured it out (using woocommerce add_action)

thanks

great, many thanks. Got it.

Thanks, I did think of auto submit. Is it a pro-only feature?

Thanks Jim, this is helpful.

Is there an easy way to know field names though? While i know the names of fields that i created in Pods, it is spitting out a lot of other fields that are there by default.

I’ll check with Oasis Workflow about the 2nd point. Thanks again.

Sorry, I mean Oasis Workflow.

Makes sense. I’m a bit of a purist when it comes to web content management, so just don’t like mixing content elements and presentation elements in one field. Plus, thanks to Pods, I can anyways use gallery shortcodes on images uploaded via custom field. Thanks for creating such a wonderful plugin.

Thanks. I also realized this after spending hours trying to change slug of Jetpack Portfolio post type :).

Great, thanks. I decided we will not use the content field for images. I believe text content needs to be separate from other types of assets, so best to have an images custom field via Pods.

Okay i’ll answer this myself just in case someone else has similar requirements:

I ended up modifying this file: /core/front/models/modules/related-posts/class-model-related_posts.php

In this file, there is a function czr_fn_setup_query() that constructs a query to show posts related by categories and tags for wordpress posts (not custom posts).

I added some code there so it can now show related posts for:

1. Custom post types (added post type in args)
2. Taxonomies (used tax_query in args)
3. In addition it can also display related posts based on manual selection via a custom field in CPT called “related_products”.

Now a follow up question:

Is this (meaning modifying czr_fn_setup_query() in class-model-related_posts.php the right way to do this? If not, could someone please advise how do i go about doing it in such a way that is extensible and upgrade-proof?

Many thanks in advance.

PS: I think support for custom fields and related posts by taxonomy should be built-in.

I agree, this would be a great functionality to have.