I see you posted while I was formulating a response. Yes you must use a fully new vb with no special groups or if want you can create those vb groups with the same id number as the ones in photopost and just remove the code in the import script that renumbers the user's usergroup and let the import script import that groupid in its normal format. Remember the script I wrote is designed to import into a clean vb format which has no custom usergroups so this is your issue.
Yes you must use a fully new vb with no special groups
I did that. Only the usergroups that are part of the standard install of a fresh vb 3.68 have been there.
Originally Posted by Chuck S
... or if want you can create those vb groups with the same id number as the ones in photopost and just remove the code in the import script that renumbers the user's usergroup...
How do I do this?
Originally Posted by Chuck S
Remember the script I wrote is designed to import into a clean vb format which has no custom usergroups so this is your issue.
There have been no custom usergroups in this fresh vb install. Only the UG, that are part of a clean install by default. And I think this is the problem. It seem I really have to delete/change first the standard vb usergroups or their ID.
In "import.php" I see in the second half this code. I guess this is where I have to add something to reflect the PP usergroups and their IDs. So over the next 2 hours I will do the following:
1. I will add some lines in the code of the import script below (the part I marked in bold is according the UG-ID numbers I posted earlier in this thread).
2. I will then again make a fresh install, create additional usergroups within vb (to have something to import to for the code addition in bold), check again their UG-ID and put the numbers accordingly in the lines in bold below.
3. Then I start the importscript.
Content visible to verified customers only.
Theoretically, the UG-ID-Problem should then be solved, or do I oversee here something?
my modification in the script does not work. The PP users get imported in totally different vb-usergroups, but I do not understand why. Did I hack the wrong place in the code? Did I use the wrong numbers? I took the numbers from the PP database and the vb numbers from the ACP of vb.
So where in the code of this script do I have to put the ID numbers for changing PP usergroups in the appropriate vb usergroup?
Correct there are 7 default vb usergroups and this script as explained will import your users into the usergroup 2 and the admin to usergroup 6. No script is going to import users how you want them nor can I support any changes made to my script. If you use the scripts as they are designed you will be able to integrate vb and photopost and the userid's will be correct so the issue you had with using vb impex script is gone. What you do with usergroups or what groups you make and distribute users after you finish things are of little concern to the scripts or the integration as long as the exact groups exist in both apps and you set permissions accordingly.
Your code you post above should work and those groups better exist in vb with the same id but sorry I can not support any changes you make to my script.
maintenence mode? You lost me there as we dont have something like that. My script will place all users with a usergroup id of 2 except admin which is 6 you can safely update any other fields to match anywhere else. This script just imports users into vb users table.
maintenence mode? You lost me there as we dont have something like that.
In PP ACP I can "close" the gallery. If I do this a message is appearing for all suers that the gallery in in maintenence mode. Allthough I do all the stuff on a test-install, I have always this maintenence mode on while working on it. This is what I meant.
o.k., I will try to change the UG-ID in PP Database after the sync with vb forum and report back...
The usergroup they belong to in vbulletin must match the groupid in photopost users table and verify the groupnames are correct in photopost usergroups. Remember one step in the switch usergroups is for you to delete all photopost usergroups except admin change that to group 6 and then go to admin and resync your groups and set permissions accordingly.
The usergroup they belong to in vbulletin must match the groupid in photopost users table and verify the groupnames are correct in photopost usergroups.
I did check this. It is correct.
Originally Posted by Chuck S
Remember one step in the switch usergroups is for you to delete all photopost usergroups except admin change that to group 6 and then go to admin and resync your groups and set permissions accordingly.
I also did this everytime. But the problem persist. In both db the UG-ID is the exact same, but when I click on the suer's profile within PP, users are sometimes admins, somtimes banned etc. The suernames affectes are totally wrong in those groups.
IMHO this has nothing to do with the script, since all users are now in the database of vb. And within vb they are all in the correct group. also the UG-ID of vb are teh exact same like in PP after the delete/sync process.
So where does PP get the information, that although according to vb a user is member of usergroup A, it shows online usergroup B?
in the database of vb, one user has UG-ID 9 (which is correct) the same user in PP database has UG-ID 6 (which is wrong).
There seems to be a step in the code of PP, where it does not take 100% the information provided in the database of vb.
Wait a moment...
The UG-ID 6 in PP was formerly (before the import) the correct UG-ID for that user. It is usergrouplevel Bronze.
The UG-ID for Bronze is in vb 9, not 6. In the database of PP after the sync, is the UG-ID for Bronze also 9.
So it seems that PP does not "update" the UG-ID for each user after the sync! It just leaves the users with their old UG-ID from the time before the sync!