Thread: [psa-devel] Actually, I'm changing the settings.php file

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I changed my mind. The rest of the class does not user the PSA_ prefix. I've
removed it from the settings.php template. We can change the entire system
over later if necessary. 

On Wednesday, August 20, 2003, 10:36:21 AM, Albert wrote:

> I changed my mind. The rest of the class does not user the PSA_ prefix. I've
> removed it from the settings.php template. We can change the entire system
> over later if necessary. 

Can you clarify? What was the change that you are now changing back?

-- 
Alex
http://www.spittingllamas.com
"Formal Restrictions, contrary to what you might think,
free you up by allowing you to concentrate on purer ideas."
 - Winter Sorbeck in Chip Kidd's The Cheese Monkeys

I would really appreciate help in designing and developing the open
registration process, and modeling the database structure for the user
Extensive user profile.

Albert

Albert Lash wrote:
> I would really appreciate help in designing and developing the open
> registration process, and modeling the database structure for the user
> Extensive user profile.

Give me an idea of what you want to accomplish, and I will throw some 
ideas or code out there for you.

I will need to add (at least - looking for additional input) these fields to
the psa_users table:

Address_1
Address_2
Town
City
Zip
Country
Date of Birth 
Company
Fax

Not the exhaustive list, but a start. I'd like to setup a basic form that
users can customize that uses the addUser function. It would be cool to have
an array as part of the setup that can define which fields are required and
which are not. Then of course some intelligent way to produce an error and a
user friendly way to highlight which fields were missed, while retaining the
original inputs. 

I just did this using PSA and my solution was very sloppy and bug prone.
This will be useful to the project because many web applications are
utilized by users who sign themselves up, or give themselves access.

- Al

On 8/20/03 12:37 PM, "Justin Koivisto" <ju...@ko...> wrote:

> Albert Lash wrote:
>> I would really appreciate help in designing and developing the open
>> registration process, and modeling the database structure for the user
>> Extensive user profile.
> 
> Give me an idea of what you want to accomplish, and I will throw some
> ideas or code out there for you.

On Wednesday, August 20, 2003, 1:43:39 PM, Albert wrote:

> I will need to add (at least - looking for additional input) these fields to
> the psa_users table:

> Address_1
> Address_2
> Town
> City
> Zip
> Country
> Date of Birth 
> Company
> Fax

Could you make the fields list dynamic as part of an install
procedure? Have some that are defaults, but let the user add custom
fields if needed. Maybe just do this at an install level and not as
something that could be constantly modified.

> Not the exhaustive list, but a start. I'd like to setup a basic form that
> users can customize that uses the addUser function. It would be cool to have
> an array as part of the setup that can define which fields are required and
> which are not. Then of course some intelligent way to produce an error and a
> user friendly way to highlight which fields were missed, while retaining the
> original inputs.

Should be fairly easy to do this by dynamically setting the CSS class
of the input fields based on some flag.

> I just did this using PSA and my solution was very sloppy and bug prone.
> This will be useful to the project because many web applications are
> utilized by users who sign themselves up, or give themselves access.

I am about to begin work on a project that would need this as well. To
that end, I would love to help as best I can.

-- 
Alex
http://www.spittingllamas.com
"Formal Restrictions, contrary to what you might think,
free you up by allowing you to concentrate on purer ideas."
 - Winter Sorbeck in Chip Kidd's The Cheese Monkeys

Alex - do you want us to add you as a developer?

On Thursday, August 21, 2003, 8:40:39 AM, Albert wrote:

> Alex - do you want us to add you as a developer?

Sure. I am working quite a bit with PSA lately and so I would be glad
to give back to the project.

-- 
Alex
http://www.spittingllamas.com
"Formal Restrictions, contrary to what you might think,
free you up by allowing you to concentrate on purer ideas."
 - Winter Sorbeck in Chip Kidd's The Cheese Monkeys

Albert Lash wrote:
> I will need to add (at least - looking for additional input) these fields to
> the psa_users table:

Here are the fields that I use a lot in stuff like this:

first_name
last_name
company
address
address2
city
county
state
zip
country
phone
fax
email
cell
pager
sex
birth_date
profession

You'll need to add a config array to the config file like:

array(
   'first_name' = REQUIRED,
   'last_name' = REQUIRED,
   'company' = TRUE,
   'address' = TRUE,
   'address2' = TRUE,
   'city' = TRUE,
   'county' = FALSE,
   'state' = TRUE,
   'zip' = REQUIRED,
   'country' = FALSE,
   'phone' = FALSE,
   'fax' = FALSE,
   'email' = REQUIRED,
   'cell' = FALSE,
   'pager' = FALSE,
   'sex' = FALSE,
   'birth_date' = FALSE,
   'profession' = FALSE
)

you'd have to define the REQUIRED constant (I'd suggest something like 
-1 since TRUE =1 and FALSE =0). FALSE fields are skipped (for 
everything), TRUE and REQUIRED fields are the only ones displayed.

When a form is posted, check against the config array to be sure all is 
satisfied. Push warnings for FALSE fields that were in the input, and 
errors for missing required fields.

The form coding should make use of the VALUE, CHECKED and SELECTED 
attributes where values are taken from the posted information in case of 
error. The values for these attributes need to be checked agains 
submitted information to avoid warnings about non-defined variables.

Hope this helps out. I've been just too damn busy to do much of anything 
anymore. :(

Alex, 

I'm guessing you are crazedwombat?

Albert

On Wednesday, August 20, 2003, 11:08:08 AM, Albert wrote:

> I'm guessing you are crazedwombat?

Yes, sorry.

-- 
Alex
http://www.spittingllamas.com
"Formal Restrictions, contrary to what you might think,
free you up by allowing you to concentrate on purer ideas."
 - Winter Sorbeck in Chip Kidd's The Cheese Monkeys

Alex Ezell wrote:
> On Wednesday, August 20, 2003, 11:08:08 AM, Albert wrote:
> 
> 
>>I'm guessing you are crazedwombat?
> 
> 
> Yes, sorry.
> 

You have been added to the project as a developer now.

Thanks.

For some reason, my first message didn't go through. Here it is:

In the current release of PSA, the settings do not update. This is because
in the settings table, the setting names are as follows:

min_username_length

And in the class, they are referenced as:

PSA_min_username_length

I'm going to update the schema and sql files accordingly.

Albert

I didn't change the database. Alex, are you still interested in being a
developer? 

On 8/20/03 10:54 AM, "Alex Ezell" <ta...@sp...> wrote:

> On Wednesday, August 20, 2003, 10:36:21 AM, Albert wrote:
> 
>> I changed my mind. The rest of the class does not user the PSA_ prefix. I've
>> removed it from the settings.php template. We can change the entire system
>> over later if necessary.
> 
> Can you clarify? What was the change that you are now changing back?

Thread: [psa-devel] Actually, I'm changing the settings.php file

phpsecurityadm-devel