Machine IT Services

Hi. Thanks for reaching out. So to clarify a few points, the error provided is in fact caused/triggered by the Malcare plugin, as they are requiring the user_login exist/be present when doing their database query. However, the Malcare function is being triggered by the do_login action, which this plugin triggers after account creation, and the user does not have a user_login (i.e. username) when created via your WooCommerce checkout (only email).

So in summary: User created via WooCommerce checkout (without user_login/username) -> User Register Action in this plugin is triggered -> do_login action is triggered in Malcare plugin -> Malcare throws error because user_login/username is null during DB operation.

Some potential fixes for your situation: 1. Add username field in checkout for account creation if able, or 2. Create a custom plugin that updates users without a user_login/username to have user_login set to email (using add_action(‘user_register’…), or 3. Ask Malcare developer to update their do_login action to replace username with email if user_login/username does not exist (would be a quick fix).

This is not an error with this plugin though, and it would be outside the scope of this plugin’s purpose to update a user’s username if one did not exist, and considering WooCommerce did not assign one automatically, WordPress does not require one (users can log in with just email), and Malcare did not account for this possible null value, I’d say the most reasonable solution would be option 3 above.

This was a new WordPress installation. No custom code in the functions.php of the theme, and no other plugins installed that would cause this. As for the site address, I do not want to provide that on a public forum.

Right. Unfortunately WordPress has flagged it because we’ve been using “WooCommerce” in the beginning of the plugin name for years and they’re saying we’re now violating their trademark guidelines. I’ve submitted another update which renames the plugin to: Redirect Login to WooCommerce “My account” Page

But we have to wait for them to review it unfortunately.

No problem! We actually just published another update, version 3.0.1, to address a couple potential bugs we found related to the old (non-Javascript/hide arguments) method that were caused by the merge, and allowed us to remove some additional unnecessary code.

The information is available in the plugin description:

“WooCommerce WP-Login automatically hides the redirect information in the address bar (if JavaScript is enabled), protecting against manipulation, and providing a more seamless user experience. It will also keep any URL (GET) parameters. These redirects can also include additional parameters for any developers out there, for both pre and post-authentication customization. It also supports the wp_login_url() and wp_logout_url() functions, passing the redirect and additional parameters to the login page and interrupting the default redirect to the “My account” page on logout if a redirect is specified, respectively.

Advanced Usage Example:
wp_redirect(wp_login_url(‘/your-target/here/?with=additional&post-authentication=parameters’) . ‘&with=additional&pre-authentication=parameters’);
This will pass the URL GET parameters within the wp_login_url() function to the final destination (post-authentication redirect) and pass the URL GET parameters near the end to the WooCommerce “My account” page (to be used pre-authentication), such as WooCommerce notices, session variables, tracking information, etc.”

To summarize, the plugin will now hide redirect information in the URL, and also provide the addition Advanced Usage functionality described above for developers. These features were exclusive to the Premium version of the plugin, but given there hasn’t been much need to maintain either version, it was decided that the Premium features would be incorporated in the free version (i.e. merging the two versions).

Feel free to let me know if you have any other questions.

I was able to find a workaround to do what I was trying to do.

I believe the update fixed my issue. Thanks

Just pushed an update to declare most recent version of WordPress as supported.

Yes it is. There hasn’t been an update because there’s been no reported issues for some time. We’re constantly making updates to our Premium version though, but this version still works as advertised.

• This reply was modified 2 years, 4 months ago by Machine IT Services.

Same issue on one of my sites. I’ve missed an entire day’s worth of sales because of this…

That worked! Thank you!

I am unable to provide a System Report at this time. I feel like the information provided should be enough to look into this issue. Regardless, I found a workaround for the error for my use case, so feel free to close the ticket unless you wish to look into why these methods are being called on a WP_Error object at all.

Well there’s no activity because I was told to go elsewhere for support, not because the issue is resolved. The Slack channel also yielded no assistance, or even responses to my issue.

• This reply was modified 2 years, 9 months ago by Machine IT Services.

I’ve reviewed the resources, and even tried parsing the order ID from the rest route parameter in the URL used to query the order info. It seems like either the app has these statuses hard-coded to where all statuses are available for all orders, or perhaps the WooCommerce REST API doesn’t apply this filter. I am seeing the filter triggered but as mentioned previously, when attempting to just return an empty array (that should result in no statuses available) or trying to remove any of the statuses, it doesn’t appear to have any affect, so perhaps the filter is being triggered by something else in the REST API request.

• This reply was modified 2 years, 10 months ago by Machine IT Services.
• This reply was modified 2 years, 10 months ago by Machine IT Services.

1) Yes, I’m using the most recent version: 17.8
2) All other plugins are updated
3) I am using the most recent version of WordPress: 5.8.3
4) Yes, my server meets the PHP requirements and has been hosting dozens of WordPress sites for years without issue. I am simply reporting PHP warnings as found in the current version that I’ve not seen before until recently.