#507 Limit access to GEDCOMs

[David Banks]

I have over 12 phpgedview installations with up to 9
GEDCOMs per installation. I have set up this way as I
have a 'mixed' audience of users, some want access to
5 GEDCOMs in my BANKS site but I/they do not want
access to all the BANKS GEDCOMs (9 in total). I also
manage a number of 'other' surname sites hence the
other 11 installations.
I would like the facility to add 'Never' as an option
to the 'Access Level' part of 'Update User Account'
which would disallow entry to a GEDCOM at any time. I
suggest that the disallowed GEDCOM(s) do not appear in
the Welcome Page pull-down or accessed directly from
the address. First thought is that the Welcome Page
should read the Users table and not the Gedcoms table,
this would prevent 'unwanted' GEDCOMs appearing - what
the eye doesn't see.......
This would reduce my installations by 8 making it
easier to upgrade (and manage).

David Banks

[John Finlay]

Logged In: YES
user_id=300048

Hi David,

Most of the people visiting the site are not logged in.
What would you propose they see in the welcome page menu?

You could turn off GEDCOM switching and require that they
use different access links to choose their GEDCOM.

--John

[David Banks]

Logged In: YES
user_id=918417

Hi John

For non-logged on users there would be all GEDCOMs
available but only the NAME of the individuals would be
available, all other facts would be private.

Preventing switching I think means that I would have to
give collaborative users a login for each GEDCOM, some
users could have up to 5 logins in this case.

Basically, as an example, I have a BANKS surname site which
is geographically based and uers from Sussex would only be
interested in the Sussex Banks of which there are 5
distinct and unconnected families.

David

[paul blair]

Logged In: YES
user_id=1250929

If I can add...

I would like the option of having multiple GEDCOMs available
under one instance of PGV, with user access based on
privileges in a central user table. This name and password
opens that data, another name/password opens some other
data. It would mean password control, but that's quite
acceptable.

Paul