Describe the bug
Not exactly Seravo Plugin issue but I think we should remove the wp-check-haveibeenpwned return code check from passwords.php as it's useless and currently causing issues.
In production env:
PRODUCTION [@joosuakoskinen:~] $ wp-check-haveibeenpwned --json b03fe988f8d55b87dbd2223ee1a8a37a0f882d6e 2>&1
{"found": true}
PRODUCTION [@joosuakoskinen:~] $ $?
-bash: 0: command not found
Randomly in development env:
DEVELOPMENT [@wordpress:~/wp-content/mu-plugins/seravo-plugin] seravo-plugin-2/master(+1/-0)* 127 ± wp-check-haveibeenpwned --json b03fe988f8d55b87dbd2223ee1a8a37a0f882d6e 2>&1
{"found": true}
DEVELOPMENT [@wordpress:~/wp-content/mu-plugins/seravo-plugin] seravo-plugin-2/master(+1/-0)* 1 ± $?
-bash: 1: command not found
Describe the bug Not exactly Seravo Plugin issue but I think we should remove the
wp-check-haveibeenpwned
return code check from passwords.php as it's useless and currently causing issues.In production env:
Randomly in development env: