The site that utilizes this plugin to connect to Your Membership has been causing some issues. I’ve tested this with the default WordPress theme and will all plugins deactivated except for this one. When this plugin is deactivated, the issues no longer exist.

Per site health:
– A PHP session was created by a session_start() function call. This interferes with REST API and loopback requests. The session should be closed by session_write_close() before making any HTTP requests.
– The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.

When testing the REST API, an error was encountered:

REST API Endpoint: https://website.com/wp-json/wp/v2/types/post?context=edit
REST API Response: (http_request_failed) cURL error 28: Operation timed out after 10002 milliseconds with 0 bytes received

We have a few functions that interact with the WordPress Rest API and this plugin seems to be interfering with that. I’m not sure when this issue arose but it could possibly be a conflict with one of the recent versions of WordPress. Any suggestions to resolve this issues would be greatly appreciated.

WordPress and all plugins utilized are updated to their latest versions.

This plugin has been working fine until the latest updates (1.1.4 and 1.1.5). Attempts to login with YourMembership credentials initially connect to YourMembership and then result in the error above. Reverting to 1.1.3 fixed my problem. Please advise.

Hi guys:

Noticed that when a new YM user signs in, it is making up an email and name in the User database like:

First name: Andreasmti
Last name: Cancer
email: [email protected]

The YM user has a real name and email, and the email is used to create the WP username.

Can you please shed some light on this?

Thanks.

The following rule in moym_style.css is hiding every radio control in the admin:

input[type=radio] {
	display: none;
}

For example, with this plugin activated you cannot set a different permalinks scheme.