If you bought a pro version you can open a ticket on https://support.codeat.co with the email associated to the license.
1) Are you talking about the post picker? There is a new php filter with 2.2 that let’s you to change it glossary_posttype_picker I just forgot with the new release to add the documentation for it and the other ones.
2) About that you should talk with the Yoast plugin support as it is something form them happening in the wrong way as we are using the WP native feature for slug. Did you flushed the permalink after changing that settings in our plugin?
Hi @mte90
1) Are you talking about the post picker? There is a new php filter with 2.2 that let’s you to change it glossary_posttype_picker I just forgot with the new release to add the documentation for it and the other ones.
I’ve searched for glossary_posttype_picker in the plugin folder and the only file I found is the readme.txt. Sure, you added this code to the plugin?
2) About that you should talk with the Yoast plugin support as it is something form them happening in the wrong way as we are using the WP native feature for slug. Did you flushed the permalink after changing that settings in our plugin?
Looks like this is a bug in Yoast, as there are ignoring the redirects (of course I flushed the rules after changing things).
Will write them a bug report …
All the best
Torsten
The filter name is generated by the plugin so you can’t find it with the complete slug.
You can find the doc on https://docs.codeat.co/glossary/developer/#change-the-post-types-available-in-the-internal-url-field-picker
Hi @mte90
sorry, but this still does not work. I’ve added the snippet:
add_filter( 'glossary_posttype_picker', function() {
return array('post','pages');
} );
But on a single glossary entry, there is still only posts available for internal link autocomplete. And it is still saying: “Wähle einen Beitrag von deiner Site (EN: “Choose a post from your site”).
For the Yoast bug I think I have found the culprit and it seems to be a mistake in Yoast (I think they just look at the database and ignore the redirect argument):
https://github.com/Yoast/wordpress-seo/issues/20439
All the best
Torsten
You have to change that snippet with the other post type but if you open a ticket in our premium ticket platform and sharing an admin access I can check what is happening.
I am already planning another bugfix release for the next week so I can quickly release it if there is something wrong in the plugin.
What do you mean with “You have to change that snippet with the other post type”? @mte90
So when you edit a glossary term you can link it to a specific post. That filter let’s you to add other post type where you can pick that link. You need to specify that post type if you need others.
I was suggesting to open a ticket in our premium ticket platform that is private so we can share screenshot and I can get an admin access.
Yes, @mte90, I added the mentioned snippet from your docs:
add_filter( 'glossary_posttype_picker', function() {
return array('post','pages');
} );
This should add pages to the post types array, if I understand correctly. But it does not work. I search for pages and they do not appear. And I could not set up a post type via UI, like this doc is showing:
https://docs.codeat.co/glossary/getting-started/#how-to-link-terms-to-internal-postspages
The client bought the license, I have asked for the credentials but they do not send them yet.
(Just a short note: I really appreciate your fast help, but you are not allowed to ask for admin access here. The support moderators will get you modwatched/banned if you are asking for it or you are redirecting users to your support channel for asking them there.)
I will open a ticket when I get the credentials, but I would appreciate that you are trying to help me without any admin access.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
@mte90 Please take it off this site as Torsten is now a customer and these forums are for the opensource users only of the plugin here.
*DRINKS COFFEE, SO GOOD*
Here is the normal reply for pro users.
For pro or commercial product support please contact the developer directly on their site. This includes any pre-sales topics as well.
As the developer is aware, commercial products are not supported in these forums. I am sure they will have no problem supporting you there.
Note that there is nothing to prevent anyone from coming back to this topic and replying like so:
This was resolved on the developer’s site with <INSERT SOLUTION HERE> and the free version may be updated to account for this scenario.
Or something like that.
Yes, we already have a pinned thread about the pro support in the forum for our plugin but we don’t have a prefilled answer for those cases (yet).
I suggested a couple of times in this discussion to move there.
@jdembowski This is a misunderstanding. Although I am a customer, this information is only additional. The feature with the bug is in the free version.
The second problem is about a bug in Yoast which only is shown with this plugin.
So both issues have nothing to do with a pro version feature.
@mte90 I could temporarily fix the Yoast problem with this code:
function yoast_seo_breadcrumb_append_link( $links ) {
global $post;
if ( get_post_type( $post->ID ) === 'glossary' ) {
$links = array(
array(
'url' => site_url( '/' ),
'text' => 'Startseite',
), // Home in DE
array(
'url' => site_url( '/glossar/' ),
'text' => 'Glossar',
), // Glossary in DE
array(
'url' => get_the_permalink( $post->ID ),
'text' => $post->post_title,
),
);
}
return $links;
}
add_filter( 'wpseo_breadcrumb_links', 'yoast_seo_breadcrumb_append_link' );
Sure, but with a ticket in our premium platform I can investigate better compared from here.
If you open there the support request we can address it better as it is not clear to me various things and a look on the website and backend can speed up the issue.
There was a typo on the documentation:
add_filter( 'glossary_posttype_picker', function() {
return array('post','pages');
} );
needs to be
add_filter( 'glossary_posttype_picker', function() {
return array('post','page');
} );
Then pages will be searched as well.
There is another bug with opening internal links in a new tab if this is configured for external links. Update this here if I get this fixed too.
