Suggestion/Request

Forum dedicated to Mods for HESK created by Mike Koch

Moderator: mkoch227

Post Reply
topoldo
Posts: 51
Joined: Wed Sep 21, 2016 10:44 am

Suggestion/Request

Post by topoldo »

Hi all.
I already wrote about this subject but I did not had any answer probably because I put it mixed with other questions.
I have a problem with my clients (really they are users more than clients because I work at the university!).
The problem is that Hesk/MfH use only the variable ['name'] (which corresponds to the string "name", of course) but which implies both Name AND Surnames in some cases like, for example, in the case of the obligatory field to be filled in when submitting a ticket.
Unfortunately many of my 800 clients/users fill in that field only with their Name and *not* with their Name and Surname!
By having a label "Name" and a prefilled suggestion "Name", my experience says in fact that persons report *JUST* their Name and NOT the combination of their surname+name! And I suppose this is a general problem not only mine.
As we are a Interdepartmental University facility and our helpdesk is only for internal users, we need to identify *exactly* who was submitting a ticket (and the email is not always useful) in order to intervene. Moreover we have no problem of privacy: if someone wants to have his/her not working air conditioning system or his/her dropping taps fixed in his/her laboratory, then we must know who is who and where (s)he is located.
So I created a customized version of Hesk+MfH where I added a new variable to be put in the language strings to translate which is:

Code: Select all

$hesklang['surname'] = 'Surname and Name';
which is used *only* the in the file "index.php" of the root directory.

In thi file, at line 317 (MfH 3.1.0), I modified the original code:

Code: Select all

} ?> placeholder="<?php echo htmlspecialchars($hesklang['name']); ?>"
with this one:

Code: Select all

index.php line 318
/*Modification */
} ?> placeholder="<?php echo htmlspecialchars($hesklang['surname']); ?>"
/*End of Modification*/
This way, when one submits a ticket, then (s)he sees that (s)he has to fill in with *both* Name and Surname the box whose label (fieldname) is "Name".

I hope this my request/suggestion of modification could be take into account for the next versions both of Hesk and MfH.

Regards,
Topoldo
mkoch227
Posts: 666
Joined: Wed Jul 04, 2012 3:37 pm

Re: Suggestion/Request

Post by mkoch227 »

Could you just change "Name" to something like "Full name" or "Surname and Name"?
Mike, Lead Developer of Image HESK: A surprisingly simple, user-friendly and FREE help desk software with integrated knowledgebase.
topoldo
Posts: 51
Joined: Wed Sep 21, 2016 10:44 am

Re: Suggestion/Request

Post by topoldo »

Could you just change "Name" to something like "Full name" or "Surname and Name"?
Nope.
The variable [''Name'] is used at least in another place (or more) and in those cases the correct string is "Name"; it could not be "Name & Surname" So if I change the associated string to something like "Surname and Name", then this string in used somewhere else with no sense because in that case must be "Name" instead. Now I don't remember where exacty it was used, but when I first submitted this problem I found it.
So, IMHO the best thing could be to add a new variable like ['Fullname'] specifically used for identify the field which contains the name and the surname of who submits tickets while the variable ['Name'] will be used in whatever place where the string "Name"is needed.
But this needs, of course, to know all the files where 'Name' variables is present... Maybe Klemen who (I suspect) introduced it could be involved...
Regards,
Topoldo
bastiaan.c
Posts: 142
Joined: Sat Jun 22, 2013 9:24 pm

Re: Suggestion/Request

Post by bastiaan.c »

mmm, to be honest I would like this as an option. Not as a standard. It would help when we ask for a Rank. For me First name would be renamed as rank and we could maybe even filter that in the search. 8)
However I agree with Full Name though :D It would just be an improvement.
Post Reply