0

I'm struggling for custom fields to appear in my Drupal views. They just aren't. I've populated my CiviCRM tables into the Drupal settings table, but they just aren't appearing.

Standard fields appear fine. It's just custom ones.

Please can anyone tell me a) if they've experienced the same thing lately? and b) where I should start debugging?

Should I be using CiviCRM Entity for this? Never needed to before.

Thanks,

John

Improve this question
3
  • shouldn't need civicrm entity - are your tables in single db or one for drupal and one for civi - in which case you need to add the prefix 'stuff' in settings.php
    – petednz - fuzion ♦
    Commented Feb 1, 2017 at 20:26
  • Thanks for the response. I've done the prefix stuff in settings.php but the custom fields - only the custom ones - aren't appearing in the list. Any suggestions for how I can debug this?
    – JohnFF
    Commented Feb 1, 2017 at 20:34
  • Just to be clear, you put the info into settings.php after creating the custom data fields in Civi, correct? I once added a custom field a few months after installation and couldn't figure out for the life of me why Views wasn't finding it... I hadn't redone the settings file.
    – Allen Hutchison
    Commented Feb 2, 2017 at 3:43

1 Answer 1

Reset to default
2

See CRM-19545 There was a a regression introduced in 4.7.14 and fixed in 4.7.17 If you want the fix sooner see https://github.com/civicrm/civicrm-drupal/pull/417/files

Improve this answer
5
  • This is the correct answer. It was bugged.
    – JohnFF
    Commented Feb 3, 2017 at 9:20
  • How can I apply this bug fix as a patch?
    – Christia
    Commented Sep 2, 2017 at 9:02
  • 1
    @Christia the preferred option now would be to upgrade to the latest (4.7.23) which includes this fix and numerous others. Is there a reason why you can't upgrade?
    – Aidan ♦
    Commented Sep 4, 2017 at 8:27
  • Yes of course. I have to wait until launch time so that I can bring over the data from a legacy database in the version it's in (4.7.15). I did end up doing a test upgrade and it didn't end up solving the problem for me.
    – Christia
    Commented Sep 5, 2017 at 22:22
  • In that case, see github.com/civicrm/civicrm-drupal/pull/417/files Edit modules/views/components/civicrm.core.inc on your system, find the lines that are highlighted on the left starting at line 2942 and change them to match those highlighted on the right. Note that the +- symbols in the first column show what has been changed and do not appear in the source file. But ... if you have already tried a test upgrade without success then you may have a different problem.
    – Aidan ♦
    Commented Sep 6, 2017 at 7:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.