Achievo/ATK - Bugzilla – Bug 333
Editing empty profiles and supervisors possible
Last modified: 2004-10-23 11:10:01
You need to log in before you can comment on or make changes to this bug.
When editing an employee in setup without having profiles or supervisors defined, the corresponding fields in the form are filled "empty". The form allows to edit these "empty" fields anyway, which should not be possible. When trying to edit, the edit-forms are followed by error messages, as described below. Editing "empty" profile: ---[start cut]--- error: [+00.00784s] You have an error in your SQL syntax near 'ORDER BY name' at line 1 (errno: 1064) error: [+00.00789s] Invalid SQL: SELECT DISTINCT profile.id,profile.name FROM profile WHERE profile.id= ORDER BY name ---[stop cut]--- Editing "empty" supervisor: ---[start cut]--- error: [+00.04206s] You have an error in your SQL syntax near 'AND person.role='employee' ORDER BY lastname' at line 1 (errno: 1064) error: [+00.04210s] Invalid SQL: SELECT DISTINCT person.id,person.title,person.lastname,person.firstname,person.address,person.zipcode,person.city,person.state,person.country,person.phone,person.cellular,person.fax,person.email,person.function,person.remark,person.role,person.birthdate,functionlevel.name AS al_a,functionlevel.id AS al_b,entity.name AS al_c,entity.id AS al_d,supervisor.lastname AS al_e,supervisor.firstname AS al_f,supervisor.id AS al_g,supervisor.cellular AS al_h,supervisor.fax AS al_i,supervisor.status AS al_j,person.status,person.userid,person.password FROM person LEFT JOIN functionlevel functionlevel ON person.functionlevel=functionlevel.id LEFT JOIN profile entity ON person.entity=entity.id LEFT JOIN person supervisor ON person.supervisor=supervisor.id WHERE person.id= AND person.role='employee' ORDER BY lastname ---[stop cut]--- Making changes to the form and trying to save them does not have any other effect - the changes actually cannot be saved.
This is fixed in cvs now, you can check it tomorrow in the nightly builds of achievo 1.0
*** Bug 313 has been marked as a duplicate of this bug. ***