Norman H?hne

Thank you very much for your fast reaction on this.

I can see that you’ve changed the regex slightly (word-boundary -> “set of whitespace and semicolon characters” before echo commands) which works perfectly with the ACF forms.

Thanks alot for your help!

Best,
Norman

Must have been the late time here in Germany…

after deactivating and activating Yoast SEO it worked as intended.
This is my code which is placed on the single custom post type template file:

add_filter( 'wpseo_schema_article_post_types', 'nh_add_wpseo_article_schema_to_cpt');
/**
 * Add Yoast SEO article schema for a custom post type.
 *
 * @author Norman H?hne
 */
function nh_add_wpseo_article_schema_to_cpt( $post_types ) {

	$post_types[] = 'your-cpt-slug';

	return $post_types;
}

Hope that helps everybody out and that the yoast team is extending its documentation of the Schema API.

• This reply was modified 5 years, 3 months ago by Norman H?hne.
• This reply was modified 5 years, 3 months ago by Norman H?hne.

I am experiencing the same issue. I’ve added the filter in my plugin that adds a custom post type for recipes but it does nothing instead of extending the places were the Article schema should occur.

Please dear yoast team, give us some more documentation.

I just noticed the update and I’m glad you did it! That’s very nice and should boost speed and privacy. ??

Thanks for the support.

Cheers,
Norman

Hey @kywyz,

these are some good news! Looking forward to see the new update in my dashboard ??

Have a nice day!

Cheers,
Norman

Hey Thomas,

amazing that indeed was it! Didn’t noticed you guys removed something. You should consider implementing a standard setting for the new version if people come from an old one with deprecated settings. That would help with confusion and bugs.

Kind regards
Norman

That’s good to hear @codyarsenault!

Is there actually a workaround for this because this issue is very critical from my point of view.

Cheers

Ah got you,

the deprecation error is visible on every page on frontend as well as everz page on backend.

That sad to hear. Maybe you just modify the MetaBox.php manually as I suggested. For me this works like a charm and it is according to the PHP7 guidelines.

Cheers
Norman

Hey JP,

thanks for the detailed reply and your opinion about it.

On the one hand I’m totally with you and the social networks. But on the other hand I’m very disappointed about their point of view. Some of the good old content will still be relevant over time but the ideas behind social networks is to publish regularly so that people will still participate. :/ For my opinion it’s not always necessary nor valuable to reinvent the wheel (content) over and over again.

So let’s hope they will finally do something and thanks alot for your time

Cheers
Norman

Hey Niloy,

sadly the page is still in development stage and not accessible. But the page is not very relevant anyways since the issue is officially declared as deprecated:

https://php.net/manual/en/migration70.deprecated.php

Cheers
Norman

Same here :/

Hey there,

I’m having the same problem on a clients website. My Firefox browser as well as the Firefox of my client wont do anything after clicking the images. Chrome works like a charm. But the Javascript Console isnt showing any errors

Same with me. No updates on the plugin.

Has someone tested it productive? Is everything working like a charm after all?

Hey Marcin thanks for your reply,

actually I couldn’t find an HTML Element that carries this class on the posts table (wp-admin/edit.php) in backend but I could manage your idea with the following css class:

.column-thumbnail {
    display: none;
}

Thank you so far, I would be glad to see my idea in your plugin someday! ??
Wish you a healthy start into the new year.

Kind regards
Norman

I also wanted to add that you might consider to remove the FontAwesome Stylesheet from your plugin.

Due to the fact that many websites and plugins already load a Font-Awesome Stylesheet it is for some websites redundant and causes avoidable overload.

So please consider if it is really necessary. As far as I can see, you only use it for the “information icon” beneath the Widget Box. Is that correct?

Maybe use some unicode characters instead. For example:

• https://www.fileformat.info/info/unicode/char/2139/index.htm
• https://www.fileformat.info/info/unicode/char/1f6c8/index.htm

Kind regards / Viele Grü?e
Norman