I’m seeing the same error with debugging turned on. The entire admin returns a 500 error unless wp-members is removed from the plugins directory.
Exactly excentricjester, the back-end stucks until plugin is disabled (or directory renamed/canceled)
I disabled the plugin via wordpress.com account. Never thought of this, it turned out to be a very useful feature… Since it’s the FIRST TIME IN MY LIFE I didn’t backup the entire site, because “it’s useless, what can go wrong?” AHhhhrgh. five minutes panic. Please fix.
GAG
To fix your site for now you can upload the missing api.php file from the Github repo.
I’m sure Chad will update the plugin soon!
@excentricjester Line 90 is blank now – be more specific if you can. The site I have this installed on needs this update as well –
Are we to replace an existing line of code or add this to a blank line? The require_once section is under the function load_dependencies() { section.
Thanks
Am I just blind? The GitHub repo only has older versions of files in it, nothing newer than 10 months? Am I missing a newer repo?
Sorry, I updated my previous reply because while it was working it was linking to a different api.php file.
You might be in the wrong repo. Check github.com/butlerblog/wp-members/tree/master/admin/includes
I am getting the same issue. I tried the download api.php from git hub and place in DIR but same 500 error.
Got it!!
Sorry for the issue. I actually had the new admin api file included with the package, but it didn’t get added in the SVN commit to the plugin repo.
Rather than just add the file, I reversioned the package as 3.1.3.1 so that anyone who has downloaded the 3.1.3 version up to now will see the update.
Thanks all for posting!
@judahjams re: the Github repo – that is an unofficial mirror that is not managed by me (or ww.wp.xz.cn). That repo is a mirror created by bluehost and I have no idea why it doesn’t update. I’ve contacted them about it before.
The official repo on github is https://github.com/butlerblog/wp-members
If you were downloading the api file from the repo, make sure (1) it is the repo listed above, and (2) that file is /admin/includes/api.php and not /includes/api.php. You’re actually better off downloading the entire package so that you get everything where it is supposed to be. Also, the 3.1.3.1 release addressing this is now in the ww.wp.xz.cn repository so you can load it from there as well.
@chadbuttler I updated the two files using the repo that @excentricjester pointed me to and it worked great after that. Thanks for the quick update and for contributing to the WordPress community.
No problem – thanks for the info.
Thanks for the quick update again Chad! Great support 🙂
Thanks. Solved, great job!
No problem – glad we got is solved.
