I have been using DBMan for last one year, but this is the worst error I ever encountered or ever noticed.

With the default DBMan Permissions. I created two users both with all rights except for Admin.

User1 added a record and logged out.

User 2 Logged in and modified the record added by User1 but

it failed to change the ownership of the record?

Even after modifying the record owner is still user 1?

Any help and how to make it possible that when someone modifies the record, it should change the ownership too.

Searching the archives I found only one post related to my question:

http://www.gossamer-threads.com/...uth_user_field;#3754

I tried this option too but no use.

Thanks for any input.

Zeshan.

Users should only be able to modify their own record, unless they have admin permission. I'm not sure how user2 was able to modify user1's record.

It think if you try to set it up so that anyone can modify the records of others it could cause problems or mischief by those not owning the records.

It's possible to create a field within each record (comment field) to allow other users to add to a record but not overwrite what is already there.

Perhaps if you explain what you are doing as far as wanting to allow everyone to modify all records someone might come up with a solution for you.

Unoffical DBMan FAQ

http://creativecomputingweb.com/dbman/index.shtml/

Yep, I want that Anyone with Modify rights can modify Any User's record. There is no such restriction that only who owns the record should modify it.





Below given is my Config File

# Authorization Options
# --------------------------------------------------------
# No Authentication? (1 = "there is no authentication", 0 = "there is authentication")
# If you choose no authentication, then set the permissions of what
# people can do with: @auth_default_permissions below.
$auth_no_authentication = 0;

# The amount of time in seconds that user files are kept in the
# auth directory before the program removes them. 2-6 hours is
# probably a good value.
$auth_time = 21600; # 6 hours (in seconds)

# Enable (1) or disable (0) logging.
$auth_logging = 1;

# Allow a default user? This means you can specify a user via the URL
# and skip the logon process. Use this to allow people to search without
# logging on, but require log in if they want to add/modify/remove etc.
# (1 = "yes", 0 = "no")
$auth_allow_default = 0;

# Default permissions used if there is no authentication, or for a default
# user. (View, Add, Delete, Modify, Admin), 1 = enable, 0 = disable.
@auth_default_permissions = (1,1,1,1,0);

# Allow people to sign up for their own userid/passwords? They will
# recieve default permissions.
$auth_signup = 1;

# Permissions a new signup should get.
@auth_signup_permissions = (1,1,1,1,0);

# Registered users: can modify/delete _only_ own records. For this to make
# sense you should set default off or to 1,0,0,0.
$auth_modify_own = 0;

# Registered users: can view _only_ own records. For this to make sense
# you should turn off default permissions.
$auth_view_own = 0;

# Auth user field. This is the field position in the database used for storing
# the userid who owns the record. Set to -1 if not used.
$auth_user_field = 19;

The restriction is how the script works. A registered user will have the permission to edit or view only the record(s) that he/she has added.

If you want anyone to be able to modify or delete records than you should just allow a default user and give them all but the admin permission.

Perhaps JPDeni's DBMan tutorial would help you to better understand permissions and how they work http://jpdeni.com/dbman/

Unoffical DBMan FAQ

http://creativecomputingweb.com/dbman/index.shtml/