Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I was editing a rule, removed some conditions and got this error message:
Warning: call_user_func() expects parameter 1 to be a valid callback, class 'RulesDataUI' does not have a method 'render' in RulesPluginUI->buildContent() (line 714 of ../sites/all/modules/rules/ui/ui.core.inc).
Comment | File | Size | Author |
---|---|---|---|
#1 | Screenshot-1.png | 82.86 KB | siva.thanush |
Comments
Comment #1
siva.thanush CreditAttribution: siva.thanush commentedI created a module using feature to take some rules configuration from one site to another.
It was working properly.
But now its not working showing some misbehaviour.
I Got this error message when i try to edit the rule.
admin/config/workflow/rules/reaction/manage/n
"Warning: call_user_func() expects parameter 1 to be a valid callback, class 'RulesDataUI' does not have a method 'render' in RulesPluginUI->buildContent() (line 714........"
Still when i tried editing the whole site's going like an unthemed site.
Not allowing me to proceed further.
I have attached the screenshots too.
Please give me a solution to fix this.
Even i tried updating the dev version.But no use.
-
Siva
Comment #2
siva.thanush CreditAttribution: siva.thanush commentedComment #3
mitchell CreditAttribution: mitchell commentedYou removed something that another thing depends on. That's the expected behavior.
You're more than welcome to reopen this if you have any ideas on how to improve this.
Comment #4
siva.thanush CreditAttribution: siva.thanush commentedNo need,
I understand that rules is not a problem it was with uuid.
Anyhow thanks.
Comment #5
PeteS CreditAttribution: PeteS commentedIt should never be expected behavior to get a PHP error. I have this error, with no apparent "things" missing, and now I have to trace through a whole mess of code to figure out what this error is talking about.
Comment #6
monsoon CreditAttribution: monsoon commentedSame issue here.. Looking for a useful solution. Thanks.
Comment #7
mitchell CreditAttribution: mitchell commented> It should never be expected behavior to get a PHP error.
Good point. Hopefully Rules could at least prevent you from having to trace it back.
AFAIR, I thought this error was caused by removing a module which breaks an existing configuration, or from installing a feature with a missing dependency. Can you guys provide better info? How can we improve this?
Comment #8
SocialNicheGuru CreditAttribution: SocialNicheGuru commentedone of the steps in the rules is no longer valid.
I would suggest going through each and testing to see if it is valid
Comment #9
asif_khan CreditAttribution: asif_khan commentedhi
thank you very much it saved me. it is confirm that problem is with uuid 7.x-1.0-alpha3 module after enableing this module rule doesn't work and gives all php errors and unusual behavior
but if you use uuid 7.x-1.x-dev 2012-Aug-27 version than rules work perfect .:-)
Comment #10
asif_khan CreditAttribution: asif_khan commentedit is now closed.
Comment #11
jenlamptonI'm not using UUID and I also have this error. Rules should not throw a PHP error is a component is removed. How about an error in the log, or a drupal_set_message for admins on the page? Some error handling when something goes wrong is necessary here.
Comment #12
mjcarter CreditAttribution: mjcarter commentedAlso not using UUID, and this happened twice without removing component, just order, or not even sure if I did make any changes, was just saving to be on the safe side.
It completely messed up the order of all my rule actions both times and they all have errors as they are referring to variables that aren't set yet.
Comment #13
mjcarter CreditAttribution: mjcarter commentedI've confirmed this only happens for me when the rule is saved with no changes having been made to order or components
Comment #14
Kris77 CreditAttribution: Kris77 commentedI have the same issue @mjcarter.
I have a rule already saved. If modify the rule by adding a new condition, or change the order of the components, it creates this error because it makes a copy of this action in compliance with unset variables.
I use Rules 7.x-2.11
Comment #15
TR CreditAttribution: TR commentedPlease provide steps for reproducing this error on a clean site.
Comment #16
TR CreditAttribution: TR commentedNo further information provided.
Comment #17
TR CreditAttribution: TR commented