I have set a groupX field to store values in #__cck_store_item_users. This field loads its children from an unpublished content type.
The values sent from all child fields are concatenated in the groupX column in #__cck_store_item_users (storage location is set to Custom > User).
Nevertheless, the search generic plugin seems to be looking for those values elsewhere and therefore the query returns no matches.
This shortcoming renders the plugin nearly useless, as far too many relevant fields store their values in that groupX column.
To make matters even more sketchy, Seblod stores option identifiers (or names) from simple select lists, rather than the option string itself. That is to say, Option 1=1 is stored as 1, not Option 1.
Example:
<br />::job_families_holder::1::/job_families_holder::<br /><br />::cck_job_families_holder::job_families::/cck_job_families_holder::<br />::job_families|0|job_families_holder::Maritime Applications::/job_families|0|job_families_holder::<br />::jt_mgmtadv|0|job_families_holder::::/jt_mgmtadv|0|job_families_holder::<br />::jt_legal_services|0|job_families_holder::::/jt_legal_services|0|job_families_holder::<br />::jt_communication_publication_and_information|0|job_families_holder::::/jt_communication_publication_and_information|0|job_families_holder::<br />::jt_budget_finance|0|job_families_holder::::/jt_budget_finance|0|job_families_holder::<br />::jt_technical|0|job_families_holder::::/jt_technical|0|job_families_holder::<br />::jt_pollution_preparedness|0|job_families_holder::::/jt_pollution_preparedness|0|job_families_holder::<br />::jt_maritime_information_services|0|job_families_holder::::/jt_maritime_information_services|0|job_families_holder::<br />::jt_visits_and_inspections|0|job_families_holder::::/jt_visits_and_inspections|0|job_families_holder::<br />::jt_operational_support_services|0|job_families_holder::::/jt_operational_support_services|0|job_families_holder::<br />::jt_human_resources_management|0|job_families_holder::::/jt_human_resources_management|0|job_families_holder::<br />::jt_information_technology|0|job_families_holder::::/jt_information_technology|0|job_families_holder::<br />::jt_specialised_support|0|job_families_holder::::/jt_specialised_support|0|job_families_holder::<br />::jt_administrative_support|0|job_families_holder::::/jt_administrative_support|0|job_families_holder::<br />::jt_secur|0|job_families_holder::::/jt_secur|0|job_families_holder::<br />::cckend_job_families_holder::::/cckend_job_families_holder::<br />
Is this behaviour a bug or a limitation? What can be done to make the search query target the actual column where the values land?
