Hello,

I have been trying to change the language level settings (Basic, intermediate,Expert, native, etc.) to their french equivalents ( I have had some issues translating totally recruiter through the use of locale and i18n so i decided to do it manually)...anyway it is not working and I need some help!...PLEASE!.... here is what i have tried so far:

1. I tried to change the languages field settings through the admin/structure/field-collections/field-resume-languages/fields/field_resume_languages_level/field-settings, but I am getting the "there is data in the database for this field so it can not be changed"...as I have installed recruiter demo, I have suppressed all of my users to see if the message changed, but it does not.

2. I have also tried to modify it in the code as these level have been declared in code in the file located at recruiter/modules/recruiter_features/recruiter_resume/recruiter_resume.features.field.inc line 1061, but even after changing I am not getting any changes in the User interface, I am not familiar with this API but from what I understood from the code, this file is used only at the first launch during the set up....i think.

3. So I used php my admin to see if there was a table with these language levels declared in to see somehow if i can modify them manually and I found no table relating directly to these levels, only four tables relating to the language levels field data.

So finally I am out of option and coming to you wiser developpers for some help, and I'd greatly appreciate it if you can enlighthen me....

PS: By the way thank you for setting up this distribution!

Comments

Abbass’s picture

Category: support » bug
Priority: Major » Normal

I did a reinstall of recruiter but before going through drupal's general installation I have hacked the code in the second option that I have tried and changed the labels to what I wanted and it worked!

So I think this a bug because in your code you identify language levels with unique IDs so we should be able to change their labels without impacting the database, am I wrong? so i think it is a bug...hope this helps somebody else.