1) Upon testing a user that existed in the phpbb database with aMember the user account was inactivated making it impossible for theuser to log in to the phpbb forum. 2) The user's profile fields had the data altered to break the formatting. 3) Groups that the user was a member of no longer show up as groups the member is a member of, even if the user is, in fact, a member of the group. Beware! Unless cgi-central fixes the problems this is not safe code to use with a live phpbb forum.
1) It is what aMember phpBB plugin is supposed to do - disable users that are exists but have not-active status, and enable them after they pay. I agree it is little unclear if you make import. 2) Which exactly fields? aMember doesn't touch most profile fields. 3) Yes, of course - see (1) Right way is to configure and test integation first, then run import!
No, this is not what your documentation says. For example, it says "When a user subscription expires, the member will revert to the previous user group in the Bulletin Board. " Then it should not automatically deactivate users. It should simply remove the users from the group. By deactivating users you can render the forum useless. I had to run SQL through SSH to activate my admin account after aMember deactivated it. A "little unclear" is an understatement. I release free code snippets that are far better documented than this commercial application. Thing is, I did not do any import. And the lack of documentation was not a problem for me. The problem is that the code does not perform as advertised. aMember should not touch any profile fields unless theowner of the site wants it to. aMember should be able to perform as it is described and only add and remove users from a usergroup that the administrator specifies. aMember should not take it upon itself to prevent the forum's user's from even logging in unless this is what the forum administrator wants. aMember altered the user_active field and destroyed the formatting of the interests field that I had modified. I searched the forums here prior to my test and here you claim that aMember would work with "any and all" phpbb modification. You don't seem to understand. 1) prior tousing aMember member a was a member of group a and group b. 2) If the user tries to register with aMember the user's phpbb account is deactivated and the member's group memberships are altered before payment. This is not how it should work. aMember should only add and remove users from the usergroup specified in the configuration, it should not arbitrarily deactivate users and remove all their group memberships. I did test it, and discovered that itisimplemented in a way that is dagerous and a less savy webmaster might not be able to restore their forum to the state it was in prior to aMember locking out users. It is due to this test that I am reporting these issues with your code. Testing it again will not resolve the issues that remain in this code. Alex, before purchasing aMember pro, the phpbb plugin and the photopost plugin I wrote you to ask what your code does. I was told that it would be able to simply add and remove users from a certain usergroupof my selection. I read what documentation you have written: http://www.cgi-central.net/scripts/amember/docs/html/bulletinboardplugins.htm http://www.cgi-central.net/forum/showthread.php?t=1296 This is simply not how the code works. It is not merely adding and removing users from the group specified but disabling their entire forum accounts by altering the user_active field in their profile.
I'm sorry if it was not clear. phpBB plugin code was initially designed without groups support (phpBB did not have WORKING groups support in that old time). I never received requests to change this behaviour, but I already changed it for you (we discussed this in the helpdesk today). aMember's behaviour is clear. aMember will assign user only to group(s) which he SHOULD belong by aMember records. aMember cannot just do it by events, because there is big risk to get databases out of sync. aMember must always anytime be able to restore customer account state to correct postition, so aMember must KNOW which groups user should belong to. I'm sorry if it doesn't work for your setup, but it seems to be a best approach for most clients. Moderator/admin accounts should not be entered into aMember at all and must be kept separate.
I would also like a copy of the phpbb plug as described by Craven de Kere. I agree that the default plugin operation described in this thread and http://www.amember.com/forum/showthread.php?t=2098&highlight="phpbb groups" are makes little to no sense for us. Todd Scott tscott_at_spamcop_dot_net
You want phpBB plugin to don't disable customers ? It is not a problem, just contact support via helpdesk.
Did that and I appreciate the quick fix on this. I've just installed the new plugin and so far it looks real good. Before I wasn't even getting phpbb group names when editing my product. That all seems to be working now.
hi, does anyone know if i can still get this. i want to modify it for my project. thx books for children