Hi Rabilal,
I think I found the solution
and perhaps you should add a small update to the functionality of JS Jobs
: a function that able to delete an user and
the most important TO DELETE HIS iD(SO WITH HIS ROLE) IN THE TABLE # _js_job_userroles. Why? Suppose a user had just been created on the ID 25 (in the backend or frontend), once he'll choose his role (let's say he chose: jobseeker) .So the ID 25 will also create in the table #_js_job_userroles with role = 2 ( employer=1 and jobseeker=2). Well, I'll banish this user and also remove it from my user list, once deleted we can always see in the Table #_js_job_userroles his ID 25 with role = 2 (which should also be deleted). So if a new user registers and if unfortunately it falls on recording the ID 25 then it will automatically have a role as a jobseeker (So if he wanted to be employer, he will say
) because the ID 25 is already assigned to a role which is the role = 2 = jobseeker .So you can imagine the problem if we could remove more than 100 users !!!So at least 100 new users will not have the opportunity to choose his own role. Like their role was given randomly.