Hi brashell,
Very good! I’m glad you did backup. This is very important. There must be some sort of weird capability permutation in your website that we did not take in consideration.
It’ll be really helpful if you could replicate the issue and send us the dump of your database on support@wpaam.com.
I’m sure that there will be few more folks with the same issue.
Appreciate your feedback and interest in AAM.
Vasyl
Hey, do you still need the database dump? Also I am running this script via mu-plugins
<?php
/*
Plugin Name: Add Users
Description: Add users to blogs when they visit.
*/
function helf_add_users( $user_id = 0 ) {
global $current_user, $blog_id;
if(!is_user_logged_in())
return false;
if( !is_user_member_of_blog() ) {
add_user_to_blog($blog_id, $current_user->ID, "subscriber");
}
}
add_action( 'wp' , 'helf_add_users' , 10);
?>
but it for some reason after adding a user, doesn’t enable some of the blocking settings. So when it adds a user to the site, they still can access hidden features. What can I do to fix this? I am afraid to update, do you think the transfer might break again even with beta 2?
Hi brashell,
We found the cause of issue during migration process. You can read the reply here:http://wpaam.com/forum/viewtopic.php?f=2&t=20#p48.
You can update AAM. You will no longer be asked for Migration because there is a aam_migrated flag set in database that prevents from another migration process.
Regards,
Vasyl
