Closed (won't fix)
Project:
Twitter
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
30 Jun 2011 at 10:55 UTC
Updated:
22 Nov 2011 at 05:13 UTC
ReflectionException: Function rules_core_action_execute() does not exist in ReflectionFunction->__construct() (line 1382 of \sites\all\modules\rules\includes\rules.core.inc)
The error above kills my site when I enable the Twitter Actions module.
The rest of the Twitter module seems to be working, but Twitter Actions cannot be enabled without causing the site to fail. The only way, I've found, after this is to rebuild the registry; or else the error keeps ocurring.
Hope we can find a solution.
Thanks
Comments
Comment #1
ConradFlashback commentedme too.
ReflectionException: Function rules_core_action_execute() does not exist in ReflectionFunction->__construct() (line 1387 xxx/modules/rules/includes/rules.core.inc).
But all the site goes to error and I must restore the DB.
My Database is sqlite.
Comment #2
chepec commentedReflectionException: Function rules_core_action_execute() does not exist in ReflectionFunction->__construct() (line 1388 of /apache/htdocs/teknat/tndr/sites/all/modules/rules/includes/rules.core.inc).I rebuilt my site three times before figuring out this module was the culprit (enabling it causes the error, independently of the other Twitter sub-modules).
I would like to note that in my case, the registry rebuild script did not revive the site. I mean, the script appears to have run fine (except the number of new files in the registry equals the old number of files), but this error persists.
So I am left with a site I have to rebuild from scratch, and even then no way to post to twitter, it seems.
Any help? I am at my wits end here guys.
Comment #3
michaek commented7.x is not going to see any work for a while, and there's a reason we don't have a release for it yet - it's really, really incomplete. The dev release truly is just for development, to aid the process of people providing patches.
Comment #4
a.ross commentedYou should disable the module directly, either using Drush or in the database. I failed miserably trying to disable the module with Drush, so I went into the database.
The list of modules should be in the "system" table, or if you have a prefix; "prefix_system". Then you just have to open the record and change the "status" to 0 (disabled). After that rebuild the registry and it will be back up.
I hope this is not too late :)
Comment #5
chepec commentedWell, as you suspected, the website has already been rebuilt. But I'll sure take note of your kind advice for next time. I had no idea modules could be disabled in the way you describe. Thanks!
Comment #6
revu commentedCan you please describe the database process in more detail?
Comment #7
a.ross commentedIs this sufficient?
Comment #8
juampynr commentedCommenting all the code at twitter_actions/twitter_actions.rules.inc and clearing the cache fixes the error.
I am investigating into the error to see if this part of the module was just not migrated to Drupal 7.
Comment #9
juampynr commentedtwitter_actions has not been migrated to Drupal 7. There is a lot of Drupal 6 code in it.
I have created #1317196: Implement Actions and Rules integration for Drupal 7 so progress in the port can be tracked. I also post progress related to the Twitter module at my Twitter account at http://twitter.com/juampy72.
Cheers
Comment #10
hgurol commentedI just can not enable both the Rules and Twitter module at the same time.
I dont need the Rules support in Twitter, I just want to enable 2 modules. Is there any workaround?
Thanks...