Quote:
Originally Posted by Chuck S  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.
Quote:
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?
Quote:
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.
Do you know how to do that?