Hi @marcusdowning – Thanks for posting on the support forum.
I have not thought about this plugin being used as an MU plugin, and as you said, the plugin core code resides in the src sub directory within the plugin code.
My immediate observation is that this plugin, in theory, should work as an MU plugin. I’m still interested in keeping the plugin code separate in an src sub directory as it keeps the main plugin code minimal and helps add autoload features should WordPress eventually starts to use them.
Can we try this?
1. Download the plugin zip file off wordpress.org.
2. Extract contents to wp-content/mu-plugins directory, so that there is a wp-content/mu-plugins/password-hash/wp-php-password-hash.php file.
3. Create a new file at wp-content/mu-plugins/ named wp-php-password-hash.php (Full path: wp-content/mu-plugins/wp-php-password-hash.php).
4. In the file created at #3, enter the following content:
<?php
require __DIR__ .’/password-hash/wp-php-password-hash.php’;
This will hopefully make WordPress see the password-hash plugin, proxied from the file ew created at #3. See https://wordpress.org/support/article/must-use-plugins/#caveats
I appreciate if you would post your results and observations with it. Thanks.
Confirmed, that works.
I didn’t add the require line, I just edited the existing require in wp_password_hash_include.
Awesome thank you @marcusdowning . I will update the FAQ list about MU information.
