It would be nice if the users could create their own
family tree. So that if say, my friend wanted to sign
up he could make his own family tree under my domain.
In effect, this is already a PGV feature. You need only
establish a GEDfile start, one INDI, and enable the user to
ADMIN that GEDCOM file. IOHO, to do otherwise would expose
the Admin features and access/modification rights for the
entire site to possible abuse.
You can accomplish this by creating any INDI as a dummy.
Then after the new user begins using his rights to create
the GEDfile, he/she could delete that first INDI. i.e.,
Create several dummy GEDCOMS with a record, naming them also
in a "dummy" fashion. Then when a user registers, you would
assign one of those created GEDCOMs to that user, granting
them edit and or admin rights, and off they go.
-stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ahreno
You ask again - built-in or automated - but you ignore the
security aspect. It is necessary for you to grant access to
the GEDCOM, specifying what actions the user can take, none,
access, edit, admin, etc. Otherwise, every user of your site
could change any feature willy-nilly.
It might be possible for John to write a segment of code
that automatically created a new GEDCOM file, but you would
still have to review and specify the security (read privacy)
and operations aspects for that GEDCOM. Then too, you would
have to assign the access rights for the user you desire.
Currently, every GEDCOM you add is automatically added to
each user, so every user you have will have access to every
GEDCOM created, probably not what you had in mind.
We think that having you create a number of dummy, single
INDI GEDCOM files for future assignment, each with a name
link NEW1, NEW2, NEW3... would be the easiest method to
accomplish what you ask. Remember, there is much more to
each GEDCOM managed by PGV than simply to have the file.
User privileges, public privileges and more must be
specified for each file.
-stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=1061833
In effect, this is already a PGV feature. You need only
establish a GEDfile start, one INDI, and enable the user to
ADMIN that GEDCOM file. IOHO, to do otherwise would expose
the Admin features and access/modification rights for the
entire site to possible abuse.
You can accomplish this by creating any INDI as a dummy.
Then after the new user begins using his rights to create
the GEDfile, he/she could delete that first INDI. i.e.,
Create several dummy GEDCOMS with a record, naming them also
in a "dummy" fashion. Then when a user registers, you would
assign one of those created GEDCOMs to that user, granting
them edit and or admin rights, and off they go.
-stephen
Logged In: YES
user_id=1328725
seems a bit complicated to do... would it be hard to have it
built in and/or automated...
Logged In: YES
user_id=1061833
ahreno
You ask again - built-in or automated - but you ignore the
security aspect. It is necessary for you to grant access to
the GEDCOM, specifying what actions the user can take, none,
access, edit, admin, etc. Otherwise, every user of your site
could change any feature willy-nilly.
It might be possible for John to write a segment of code
that automatically created a new GEDCOM file, but you would
still have to review and specify the security (read privacy)
and operations aspects for that GEDCOM. Then too, you would
have to assign the access rights for the user you desire.
Currently, every GEDCOM you add is automatically added to
each user, so every user you have will have access to every
GEDCOM created, probably not what you had in mind.
We think that having you create a number of dummy, single
INDI GEDCOM files for future assignment, each with a name
link NEW1, NEW2, NEW3... would be the easiest method to
accomplish what you ask. Remember, there is much more to
each GEDCOM managed by PGV than simply to have the file.
User privileges, public privileges and more must be
specified for each file.
-stephen