Multiple Admins

Lori,

I am working on a similar type of project. Would you be interested in collaborating?

Peer

Database: MySql: PHPRunner: Security: How to set advanced security per username?

http://www.faqts.com/knowledge_base/view.p.../36009/fid/1805

Lorri,
you can use Advanced security settings in PHPRunner to set access to your database for several people. Users can see other users data, can edit their own data only mode will work just fine for this purpose.
You need to create Admin table that holds graduation year, usernames and passwords. Each admin will be able to edit his graduation year data.
I can give you more detailed suggestion if you tell me more about your project.

Thanks
I saw that and did that for "one" global admin. Here's my situation

here's the site

http://www.baaa.org
We have over 40 years of alumni - we are going to allow registered alumni members to see information - I'd really like to have it to where only those that support the alumni can see all information (since they would have to agree to a privacy policy - so that don't use information for commerical purposes) - and for non-supporting alumni to see "who" was registered but not all their data - I know there is a guest option - and that might work with it.
With the classes - I only want people who are from a certain class year to be global admins for their year - not other years - i.e. Jack & Joan are from the class of 1975 and they will have global permission to update their class information after their class reunion - for those that have "class year" 1975 - but Lorri (me) is the class of 1979 - so I'll only be able to edit my class year of 1979 (this won't be true since I can edit everything via MySQL Front - but just as an example)
The database holds all the fields I need to use for generating dynamic pages.
I.E. Status is the key that holds L/D - D=deceased (when I set up these tables I used enum - but didn't see enum as an option to use for phprunner) - I want to be able to dynamically generate a page showing those that have passed away - preferably ordered by class year - I actually have a table that I set up for this that would be the associate with the mastertable - but don't want to have all the information submitted on the alumni that passed away in the actual information table - i.e. I mark an alumni deceased - it updates the the master table and inserts the ID of the person I just updated - including their first name, last name, class year from the master table, and add's the the InMemorium table the details that we have been provided (ie date/place/etc) -
There are several that would follow this (donations etc) - I know a little but not enough - I understand the logic of "how" things work, but can't write it - which of course is why I'm looking at PHPRunner - very SMOOTH btw - <img src='https://asprunner.com/forums/file.php?topicimage=1&fieldname=reply&id=4349&image=1&table=forumreplies' class='bbc_emoticon' alt=';)' />
Thank You

Lorri Nevil

Just checking to see if any of this had been answered. I'm really needing to make a decision - I just downloaded a "trial version" of PHPMagic - that thing is so crippled you can't see ANY possibilities in my opinion.
If there is another forum or developer group that discusses more complex applications and development using phprunner - if someone could point me in that direction so I could find some answers that would be awesome -
I'm very impressed with what I was able to do so far - thanks!
Lorri Nevil

Lorri,
You can solve this problem as follows:
With PHPRunner build three different projects on the basis of the main table and put generated PHP files into three different directories.
guest - common access, readonly, no password required.

user - full readonly access, password required.

admin - full access to his graduation year, password required.
First project is for common access. For example, users can view only name of the person and graduation year.

To do it, on the Key column tab in PHPRunner uncheck Edit, Add new, Delete, and Copy functions for the main table, and on the Formattingtab uncheck fields that users should not see.
Second project is for registered users.

Create Users table with Name and Password fields - in this table you will store data on registered users that have right to view all data in the database.

On the Key column tab in PHPRunner uncheck Edit, Add new, Delete, and Copy functions for the main table. Set Security settings as Username and password from database, using Users table.
Third project is for administrators that will have full access to the 40 years of alumni database - edit and make changes in the records of their graduation year.

Create Admins table with Graduation year, Name, and Password fields - in this table you will store admin users data.

Set Security settings as Users can see other users data, can edit their own data only or Users can see and edit their own data onlyand link main table to Admins table with Graduation year field.
Now you can route your site's visitors to the appropriate project as per their access level.
See following pictures for more info:

picture1

pisture2

Thanks so much for the detailed explanation - I will go work with my trial and see

what I can do. <img src='https://asprunner.com/forums/file.php?topicimage=1&fieldname=reply&id=4392&image=1&table=forumreplies' class='bbc_emoticon' alt='B)' />
In terms of being able to add to another table (i.e. when updating AlumniDB to either mark an alumni as passed away / donation / etc) - I realize this is more complicated...and I appreciate very much the screen captures on the other one - but can this be done using phprunner as well?
I would love to see a forum by users and things they have been able to do for sharing - maybe a "How TO Do This" where great responses like this are archived and more easily viewed.
I think it would be of great help - kind of a user built manual!
Lorri Nevil

Lorri,
probably you don't have to use a separate table for passwed away/donation people. You can start with a checkbox fields that store this info and can be updated by admin.

>>probably you don't have to use a separate table for passwed away/donation people. You can start with a checkbox fields that store this info and can be updated by admin.<<
Well - there is more information that is given for people that have passed away such as date/place & reported by - I don't want to store all that data in the main info table.
My thoughts were using the RecordID of the person as the primary key - pulling the First Name, Last Name & class year from that table for display - and then having the "extra" data in a second table - I know it can be done from a coding up stand point because my programmer has written several that way - he's just extremely busy and I need to be able to get something going - so I want to be able to cut down on as much work as possible for when he comes in.
Also - I was thinking the same thing on the admins - I already have an admin table - that consisited of RecordID,ID with ID being the unique foreign key - and was going to pull the Username/ClassYear/Pass from the main db table.
What are your thoughts? I've already done two pass throughs - I want to get some better details this time.
By the way - again - I'm very impressed with this - I've tried out several and some that didn't have trials I didn't - thank for having a trial that is not so crippled that you can't even go through the process...I've already recommended this to 3 other people and I'm not even done with the trial yet!
Lorri Nevil

Lorri,

I wasted a lot of time fooling around with PHP Magic <img src='https://asprunner.com/forums/file.php?topicimage=1&fieldname=reply&id=4421&image=1&table=forumreplies' class='bbc_emoticon' alt=';)' />

Peer

Lorri,
your idea for admin table looks reasonable.
I can show you how to modify ..._edit.php file to add data in memories table for those who have passed away.

Send me ..._edit.php file for main table and SQL scripts to create main and memories tables.

I really appreciate all your help - I've been really busy - but one thing I'd like to be able to do right now is have more than one person that can edit everything in the database (our alumni board) - I think our database is just so huge that I won't pull everything up - I manually added in my personal edit and we've just been using that - but I need everyone to be able to experience it so we can make a finaly buy decision - can you help me on how to manually edit that? It's nice clean code you produce - I commend you on that - I've gone in and hand edited some things I accidentally put in there to see and didn't mean to!
Thanks!

Lorri Nevil

I guess the easiest way is to create a separate project/folder for superadmins with full access to whole database content. You can have a separate table to store superadmin usernames/passwords.
I hope this helps.

I can see that - but I designed my database based on coding that I know can be done - of course by an experienced programmer. All the alumni are in one database along with user/pass - and I had set "access level" - with 0 being regular - and some others all the way up to 50 - full admin and then 100 - for like me for some extra stuff - I know it can be done - just am not sure how --
Thanks for your input and your postings - they are very helpful!

Lorri,
you can do it but it needs a lot of manual coding.

I think the seperate table is the way to go....

BTW,

If you write an SQL script to create and delete your table(s) on the fly, changing fields, and field properties is much easier.
It takes awhile to work out the table and field structure.
I am working on a new app and am still tihking about the field table structure.

The nice thing about phprunner is you can start over and not have to rewrite a lot of code.
Peer

I can see that - but I designed my database based on coding that I know can be done - of course by an experienced programmer. All the alumni are in one database along with user/pass - and I had set "access level" - with 0 being regular - and some others all the way up to 50 - full admin and then 100 - for like me for some extra stuff - I know it can be done - just am not sure how --

Hey Kaelin
I was able to come up with a single login and have multiple levels of access. I used only one login table.. used the groupID that they suggested and used the branching option after a successful login. I tried the one listed on the website, but found my users not too keen on it. I did modify the approach you listed in your notes, and was able to work out the kinks.. if you ever want to make it a single login, let me know
Mike