Posted: Sat Jun 30, 2007 6:11 pm
I can't seem to get permissions to actually take hold for some reason. I'm sure I'm missing some very simple step, but...
I went through http://framework.weblite.ca/documentation/tutorial/getting_started/permissions and did everything EXACTLY as suggested. Essentially just cutting and pasting.
1) Used the SQL command under Figure 1 to make the new table
2) Copied over the "[_auth]" section of the conf.ini into my conf.ini and uploaded it to "../Monsters/" (which would be "../Program/" in the doc files
This made a login button appear on the site. This works fine, BTW.
3) Copied the ApplicationDelegate.php file into a blank txt document, saved it and uploaded it to the newly created "../conf/" directory
4) Ran the given SQL query on my database copied and pasted from the "Testing our application" section
This DID seem to create the users as I can now login as these users
5) Redid everything twice more because none of it has ANY effect on my site (except for the login appearing).
What I want is to have a single account (mine) that is the owner and can do everything. All other users (whether logged in or not, as there's no reason for anyone else to even have an accounton tihs site at the moment) should have Read Only access.
I'd like to hide some of the tables from them eventually, but right now I just need to keep others from adding/editing my records. And I'm at a loss to even create a situation where people are forced to login.
I went through http://framework.weblite.ca/documentation/tutorial/getting_started/permissions and did everything EXACTLY as suggested. Essentially just cutting and pasting.
1) Used the SQL command under Figure 1 to make the new table
2) Copied over the "[_auth]" section of the conf.ini into my conf.ini and uploaded it to "../Monsters/" (which would be "../Program/" in the doc files
This made a login button appear on the site. This works fine, BTW.
3) Copied the ApplicationDelegate.php file into a blank txt document, saved it and uploaded it to the newly created "../conf/" directory
4) Ran the given SQL query on my database copied and pasted from the "Testing our application" section
This DID seem to create the users as I can now login as these users
5) Redid everything twice more because none of it has ANY effect on my site (except for the login appearing).
What I want is to have a single account (mine) that is the owner and can do everything. All other users (whether logged in or not, as there's no reason for anyone else to even have an accounton tihs site at the moment) should have Read Only access.
I'd like to hide some of the tables from them eventually, but right now I just need to keep others from adding/editing my records. And I'm at a loss to even create a situation where people are forced to login.