WPIntell

Source evidence

get_users causes memory error

WP OAuth Server ( Login with WordPress ) · support · 2020-02-17T16:01:00+00:00

WP OAuth Server ( Login with WordPress ) plugin evidence original source source API
mixedsentiment
mediumseverity
0.85relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 29 rows with source links

17.2% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

24 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
samnockels resolved
Hello, Upon installing your plugin, I experienced an error when using the authorize endpoint. I believe the problem was a timeout/memory allocation error through the use of the get_users function call at _mo_check_user_login (endpoints/registry.php line 224) After replacing this line with: get_user_by('login', $current_user_cookie['username']) the plugin begins to work as normal. My guess is that our large database of users is causing a memory error! This topic was modified 6 years, 3 months ago by samnockels . This topic was modified 6 years, 3 months ago by samnockels . This topic was modified 6 years, 3 months ago by samnockels . Hi Sam, We are looking into the issue. Can you tell us how many users you have right now in your WordPress database so that we can reproduce the issue? We have 16,464 users in total Hi Sam, Thanks for the reply. We have fixed the issue and updated the plugin. You can now update/download the latest version of the plugin.

Comments

3 shown
miniOrange 2020-02-17T20:44:00+00:00

Hi Sam, We are looking into the issue. Can you tell us how many users you have right now in your WordPress database so that we can reproduce the issue?

samnockels 2020-02-18T08:38:00+00:00

We have 16,464 users in total

miniOrange 2020-02-19T19:35:00+00:00

Hi Sam, Thanks for the reply. We have fixed the issue and updated the plugin. You can now update/download the latest version of the plugin.