I have a view that displays userid and profile2 data (with a relation). If I display the userid and data from only one profile on wich I apply a VBO component action (changing the content of ProfileType1_field_A), all works well. My view looks like this :

UserID ProfileType1_field_A ProfileType1_field_B

If I add fields from a second profile, to have a display like this :

UserID ProfileType1_field_A ProfileType1_field_B ProfileType2_field_X

I then get the following error:
Fatal error: Call to undefined function rules_ui_element_fix_empty_after_build() in /home/mysite/public_html/includes/form.inc on line 1830

Comments

bojanz’s picture

bojanz CreditAttribution: bojanz commented
Project: Views Bulk Operations (VBO) » Rules
Version: 7.x-3.x-dev » 7.x-2.x-dev
Component: Core » Rules Engine

Moving to the Rules queue to get the maintainers' opinion.
Sounds like ui.forms.inc doesn't get included at a certain point, is there anything extra VBO should do?

fago’s picture

fago
Primary language German
Location Vienna
CreditAttribution: fago commented

Nope, that should be added in via RulesPluginUI::formDefaults(). Maybe the reference on the form state is lost somewhere? That would result in FAPI forgetting the include...

mitchell’s picture

mitchell CreditAttribution: mitchell commented
Title: Fatal error: Call to undefined function rules_ui_element_fix_empty_after_build() » RulesPluginUI looses form state
Component: Rules Engine » User Interface
Status: Active » Postponed (maintainer needs more info)
mitchell’s picture

mitchell CreditAttribution: mitchell commented
Issue summary: View changes

typo error

Itangalo’s picture

Itangalo CreditAttribution: Itangalo commented

I don't know if this helps, but I have people reporting the same problems for a module of mine: #1975906: Fatal error when adding a lesson and #2083847: Fatal error in php script when submitting dates on admin tabe of course offering.

I started experiencing the same problems when the server got upgraded from PHP 5.3 to 5.6.

Itangalo’s picture

Itangalo CreditAttribution: Itangalo commented
Issue summary: View changes

Confirming that the error disappears when switching back to PHP 5.3.
(This isn't solving the actual problem, but it might help locating it.)

TR’s picture

TR CreditAttribution: TR commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

All tests run successfully on PHP 5.3 through PHP 7.2. Feel free to reopen this issue if you can provide detailed steps to reproduce this on a clean installation of Drupal/Rules.