Richard Korthuis

Hi @jhaankitesh,

Thank you for using our plugin! This is most probably not due to the namespaces fallback (as @ashwinparthasarathi suggests), but due to the fact php-mbstring is not installed on your server.

@ashwinparthasarathi From the same page you are linking to: For functions and constants, PHP will fall back to global functions or constants if a namespaced function or constant does not exist. Since we have not declared a function with the same name within our namespace, PHP will fall back to the global function. The error comes from the fact that the global function does not exist, so adding a \ in front of the function will not solve this issue.

@sahooweb Are you sure you are asking in the right place? You are in the support forums for the plugin WP REST Yoast Meta. My guess is, you are having an issue with Yoast SEO.

If I visit your REST API, I don’t see the yoast_meta in it, so I am guessing you haven’t installed our plugin.

So please ask your question in the support forums for Yoast SEO.

Hi @altoscameron

Thank you for using our plugin!

Let me explain the structure and why we didn’t make it more associative as you suggest: The name/value pairs are build exactly as the meta tags would have been generated by Yoast SEO. So let’s look at the first item:

{
    "name": "description",
    "content": "Shop page meta description"
}

This directly translates to the meta tag:

<meta name="description" content="Shop page meta description">

So as you can see the name/value pairs correspond with the attribute name/value pairs of the meta tag.

So unfortunately for you we have no plans to change this structure.

Hi @divv

Thank you for your feedback, this might help other people searching through this topic ??

What file(s) did you actually delete? Because if you deleted the plugin, you should also not be able to see that notice since it is coming from the plugin. So apparently you did not delete the plugin.

(By the way: you keep referring to the notice as an error, but it isn’t an error. It is a (dismissable) notice to let you know about the settings)

Hi @hansgv

You say: “After deleting wp-rest-cache again”, but you do get a notice from our plugin, so I don’t understand that part? What did you delete?

About the notice: if you are indeed using W3TC with memcached and object caches, it is indeed advised to check the checkbox as mentioned in the message. This is because PHP’s memcached treats cache timeouts a little different and checking the checkbox will prevent any errors.

Hi @efbi

Thank you for using our plugin!

How did you change the REST URL prefix? Because if you did use the WordPress rest_url_prefix filter it should work automatically.

Hi @jamiewarb

We just released a new version of our plugin which includes the yoast_title. Please let us know if this works for you.

This thread has been marked as resolved due to lack of activity.

You’re always welcome to open a new topic.

Thanks for understanding!

Hi @adorei

We just released a new version of our plugin, which solves this error.

Hi @mdxclr

We just released a new version of our plugin which solves this error.

Hi @nicolauria

Unfortunately I am unable to reproduce this error at this time, making it really hard for me to debug and solve it. I will keep an eye on it, but for now there isn’t much I can do.

N.B. I also did see the solution posted by miniOrange in this topic you opened for their plugin. Although it might solve the problem of showing the endpoints unauthenticated, it also disables caching for those endpoints.

Hi @divv

Thank you for using our plugin and sorry for the late response. It took some time to dig into this.

For now I have a quick-fix for you, while we add this to our to-do list to see how we can better support this kind of authentication. The quick-fix involves you editing the mu-plugin that was installed by the WP REST Cache plugin, so I hope you are comfortable doing that?

Go to /wp-content/mu-plugins/wp-rest-cache.php and add the following lines directly after line 24 (so after the line if ( is_plugin_active( 'wp-rest-cache/wp-rest-cache.php' ) ) { ):

	if ( is_plugin_active( 'wp-rest-api-authentication/miniorange-api-authentication.php' ) ) {
		include_once ABSPATH . '/wp-settings.php';
		wp_cookie_constants();
		include_once ABSPATH . WPINC . '/pluggable.php';
		include_once WP_PLUGIN_DIR . '/wp-rest-api-authentication/admin/class-miniorange-api-authentication-admin.php';
		$mo = new \Miniorange_API_Authentication_Admin( 'miniorange-api-authentication', '1.0.0' );

		$mo->mo_api_auth_initialize_api_flow();
	}

Please let us know if it works for you!

Hi @hansgv

Thank you for the list, which is quite long… Unfortunately there are several paid plugins in your list, making it really hard for me to try to recreate your setup and trying to reproduce the error.

The only thing left for me to advise you is to try deactivating all plugins and then reinstalling our plugin.