Hi all

for some reason i have on my frontpage

Fatal error: Class 'FacesExtendable' not found in ***sites/all/modules/rules/includes/rules.core.inc on line 231

Can't understand what means.

Waiting for instructions for debug or possible solutions

Best regards
ArchGalileu

www.gasparsantos.eu
www.quartetodouro.eu
www.cameratanovnorte.eu

Comments

rodrigoaguilera’s picture

Component: Rules Core » Rules Engine

sub

cjarmstrong’s picture

subscribe

hansrossel’s picture

I have the same problem. I'm using commerce and the modules needed for that.

There seems to be a lot of sites that have this, Google finds more than 1000 results

The error message is output after the </html> tag, so is not in all browsers visible.

hansrossel’s picture

Title: Error on frontpage » Fatal error: Class 'FacesExtendable' not found line 231 on every page after </html> tag

changing title, also error is on every page not only on frontpage

Refineo’s picture

subscribe

andros’s picture

i get this not after </html>,but in the error log on every page loaded by an not logged in user.

yannisc’s picture

sub

codexico’s picture

Refineo’s picture

Hi,
I also got this error. Here are my test results. Did you have a simillar scenario ?

Issue

Fatal error: Class 'FacesExtendable' not found in 

/***/sites/all/modules/rules/includes/rules.core.inc on line 231
Array
(
    [type] => 1
    [message] => Class 'FacesExtendable' not found
    [file] => /***/sites/all/modules/rules/includes/rules.core.inc
    [line] => 231
)

This error occured on a front page
when browsing as an anonymous user
after a new custom rule is created (disabled or enabled).
Cache pages for anonymous users turned on.

This error did not occur for an authorized user 1.

There was no error on following pages:
***/user
***/user/login
***/user/register
***/user/password

test 1

  • Turn off and clear cache
  • No custom rules in ***/admin/config/workflow/rules
  • go to front page
    result: No error

    test 2

  • Create a custom rule ("Test rule")
  • Turn off cache
  • No tags
  • React on event "User has logged in"
  • Save changes "Your changes have been saved."
  • go to front page
    result: No error

    test 3

  • turn on cache (Cache pages for anonymous users) on ***/admin/config/development/performance
  • go to front page
    result: No error

    Summary

    The error disappeared after I turned off cache and then didn't occur after I turned on cache pages for anonymous users again.
    You probably need to clear and turn off all cache mechanisms to solve this issue.

    Environment

    • Drupal 7.7
    • Entity API 7.x-1.0-beta10
    • Rules 7.x-2.0-rc1
    • Memcache 7.x-0.0
  • rodrigoaguilera’s picture

    Just tested that without cache the error is gone but renabling it again brings the error again

    nelslynn’s picture

    This seems to be random. If I browse back and forth between two pages, the error shows up at the bottom of each page maybe 50% of the time?

    Refineo’s picture

    As far as my site is concerned the error disappears after

    • turning off and turning on cache again
    • rebuilding permissions
    rodrigoaguilera’s picture

    not for me

    Refineo’s picture

    Maybe this code can help you ?
    http://drupal.org/project/registry_rebuild

    rodrigoaguilera’s picture

    Thanks for the help but already tried that with no luck

    Tsuba’s picture

    Also if cache turn on server give 500 error for all pages, but site workin fine. And in log error Fatal error: Class 'FacesExtendable' not found in ***sites/all/modules/rules/includes/rules.core.inc on line 231

    klausi’s picture

    klausi’s picture

    Status: Active » Needs review
    StatusFileSize
    new502 bytes

    I could reproduce this issue using this comment: http://drupal.org/node/1110492#comment-4480228
    After a long way of debugging, I found that the TestingMailSystem serializes messages to the variable table. On bootstrap the variables are loaded, unserialized and Drupal looks for the classes that correspond to the (nested) variables. But at this point module files are not included, so code that relies on module files will fail (the custom rules class loader for example).

    So it is a problem that we include complex class variables in the email message data. The patch attached removes that.

    Status: Needs review » Needs work

    The last submitted patch, 1257580-rules-email-classes.patch, failed testing.

    klausi’s picture

    Status: Needs work » Needs review

    wtf testbot?

    gagoo’s picture

    Hello,

    I have the same issue, but only with Chrome.
    No problem with firefox or safari... Strange !

    Subscribe :)

    benmalen’s picture

    sub

    fago’s picture

    Status: Needs review » Fixed

    thanks for tracking this down klausi.
    tests are green for me -> committed.

    Refineo’s picture

    Hi, will there be a new 7.x-2.x-dev for this patch on http://drupal.org/project/rules?

    klausi’s picture

    yes, in 12 hours max.

    gagoo’s picture

    Hi,

    I updated to the 7.x-2.x-dev released on 2011-Sep-07 that should include the patch but it didn't solve the issue.
    I see this error message only under Chrome, no problem with the others browsers.

    Please help !

    Thanks

    benmalen’s picture

    Version: 7.x-2.0-rc1 » 7.x-2.x-dev
    Status: Fixed » Needs review

    I am still getting this error with the latest dev release, even after clearing cache

    7.x-2.x-dev tar.gz (147.31 KB) | zip (176.73 KB) 2011-Sep-08

    Fatal error: Class 'FacesExtendable' not found in /sites/all/modules/rules/includes/rules.core.inc on line 231

    klausi’s picture

    Status: Needs review » Postponed (maintainer needs more info)

    Please describe the exact steps to reproduce this problem.

    Tsuba’s picture

    Installed profile: Commerce Kickstart (commerce_kickstart-7.x-1.0-beta6)
    This profile contain Rules and this error.

    klausi’s picture

    I guess commerce_kickstart does not contain the latest Rules dev version, please update and test with the latest Rules dev package.

    benmalen’s picture

    The error message seems to only appear for anonymous users, so maybe "cache pages for anonymous users" in performance options may be relevant. It appears as soon as the Rules module is enabled - no rules have to be created/activated. When logged out, bypass your browser cache (eg Firefox shift + click refresh or ctrl + F5) and you will see the message. (Browser cache may explain why some users are seeing the error in one browser and not in another.)

    gagoo’s picture

    I confirm that even if I clear the browswers cache on every page loading, the fatal error message appears only with Chrome.

    hansrossel’s picture

    I applied patch #18 and still have the error.

    I actually don't see it visibly myself in any browser I have installed, but got clients with other browsers that could see it and I can see its present in the Google cache of the site). The message also becomes very visible when I import a newsletter page (a node on the site) into Mailchimp, then the message is at the bottom of every newsletter that is sent.

    When Anonymous cache is turned off the error message is gone. As soon as cache is turned on again (also after clearing the cache) the error is back.

    modoq’s picture

    sub

    fago’s picture

    I cannot reproduce, regardless I turn anonymous caching or use chrome. There must be something else triggering this.

    klausi’s picture

    I suspect that some users still have some serialized Rules objects in their variables table. They are initialized before modules are loaded, which can cause this error.

    Could anyone provide a error backtrace from drush or xdebug so that we can see if it is still triggered in variables_initialize() ?

    aspilicious’s picture

    I have the same error for anonymous users. The only rule I have is that a mail gets send after someone adds a new node for a custom content type.

    aspilicious’s picture

    Ok update:

    I couldn't edit the rule so I suspected the rule to be broken. So I removed it and added a new one.
    Error gone, me happy.

    I remember something about "return array" as upgrade message. Don't remember if it was a rules upgrade message.

    gagoo’s picture

    OK, I have the same additional problem than aspilicious : I can't edit my rules. I have a 500 server error when I try to do that. These rules send an e-mail when a content from a custom type is saved.

    I deleted these rules but the fatal error still be at the bottom on all my pages.

    faridjame’s picture

    The latest dev version resolved the issue for me.

    benmalen’s picture

    Well I am still getting this error message. I completely removed the rules module and made sure no tables were left in the database then installed it again.

    1. /admin/modules - Disabled Rules, Rules Scheduler, Rules UI
    2. /admin/modules/uninstall - Uninstalled Disabled Rules, Rules Scheduler, Rules UI
    3. Completely removed the rules module from /sites/all/modules
    4. /admin/config/development/performance - Clear all caches
    5. /admin/config/system/cron - Run cron
    6. Upload Rules 7.x-2.x-dev 2011-Sep-08 to /sites/all/modules
    7. /admin/modules - Enable Rules, Rules Scheduler, Rules UI
    8. Log out, clear browser cache - Error message "Fatal error: Class 'FacesExtendable'"
    9. Log back in, /admin/config/development/performance - Disable "Cache pages for anonymous users"
    10. Log out, clear browser cache - No error message

    JGO’s picture

    Hi,

    I had the same error on the rc2 version, but fortunately the latest dev version fixed the problem for me as well!

    mototribe’s picture

    sub

    Canadaka’s picture

    subscribe, having this issue on a couple random view XML outputs. breaks XML validation

    fago’s picture

    >I deleted these rules but the fatal error still be at the bottom on all my pages.

    Sounds like it is triggered by some Javascript that embeds something there, maybe drupal 7's poormanscron solution? Does disabling the "automatic crons" help? Or do you have something else embedded there?

    budda’s picture

    I've been building a site on a PHP 5.3 server for 5 months and never had any problems like this. I deployed the site on a PHP 5.2 server and instantly got the HTTP 500 error. Examining the log its just loads of this error.

    PHP Fatal error: Class 'FacesExtendable' not found in /home/dinocrun/public_html/sites/all/modules/rules/includes/rules.core.inc on line 231

    Reading the two similar issues i don't have anything else to add apart from the PHP version difference in my case. Running Rules 7.x-2.0-rc1

    viren.ratan’s picture

    +1

    hansrossel’s picture

    #45, its not poormanscron, I'm not using it, also I think poormanscron does not bother if the anonymous cache is on or not and the error occurs only when anonymous cache is on.

    benmalen’s picture

    Hmm, I am running PHP 5.2.17, so maybe this is a PHP bug?
    Web server is running LiteSpeed.

    gurvan’s picture

    I've just updated webform, Taxonomy Views Integrator, tagadelic & site map, now I don't have any fatal error. Maybe it will help...

    JGO’s picture

    Hmm the error is not gone. Sometimes it disappears for a while and then comes back. Probably something to do with caching

    dangermonkey’s picture

    Version: 7.x-2.x-dev » 7.x-2.0-rc2

    Sub.
    Got the error this morning after updating to the rc2 release. Clearing the cache and rebuilding permissions works fine, but if I can avoid the problem entirely that would be awesome.

    Also, didn't mean to change the issue details. I'm a noob at this whole posting thing!

    cyberwolf’s picture

    Suffered from this problem as well. Somehow a variable "drupal_test_email_collector" got set, containing a serialized instance of the RulesAction class. When loading variables it was trying to load the class as well, but somehow it couldn't as the registry wasn't initialized / completed yet. I removed the drupal_test_email_collector entry from the database and the fatal error disappeared.

    Edit: apparently the TestingMailSystem MailSystemInterface implementation included in Drupal core uses the drupal_test_email_collector variable to capture all outgoing e-mail.

    larowlan’s picture

    Version: 7.x-2.0-rc2 » 7.x-2.x-dev
    Status: Postponed (maintainer needs more info) » Active

    Seeing same issue on rules-7.x-2.x-dev as of today's date.
    What I'm doing to cause the issue:
    I have a private file field and a custom 403 page.
    When an anonymous user (chrome browser) attempts to view the private file they should get the custom 403 page, instead I get a Fatal error - xdebug stack trace below.
    I've removed the site_403 variable (ie back to the default) but that makes no difference.
    The site has commerce and features installed if that makes a difference - the rules are mostly related to commerce.

    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP Fatal error:  Class 'FacesExtendable' not found in /var/aegir/drupal-7.8/sites/nsand.leerowlands.com.au/modules/rules/includes/rules.core.inc on line 231
    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP Stack trace:
    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP   1. {main}() /var/aegir/drupal-7.8/index.php:0
    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP   2. drupal_bootstrap() /var/aegir/drupal-7.8/index.php:20
    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP   3. _drupal_bootstrap_page_cache() /var/aegir/drupal-7.8/includes/bootstrap.inc:2075
    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP   4. bootstrap_invoke_all() /var/aegir/drupal-7.8/includes/bootstrap.inc:2231
    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP   5. module_invoke() /var/aegir/drupal-7.8/includes/bootstrap.inc:1072
    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP   6. call_user_func_array() /var/aegir/drupal-7.8/includes/module.inc:795
    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP   7. rules_exit() /var/aegir/drupal-7.8/includes/module.inc:795
    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP   8. rules_show_debug_output() /var/aegir/drupal-7.8/sites/nsand.leerowlands.com.au/modules/rules/rules.module:1101
    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP   9. drupal_autoload_class() /var/aegir/drupal-7.8/sites/nsand.leerowlands.com.au/modules/rules/rules.module:0
    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP  10. _registry_check_code() /var/aegir/drupal-7.8/includes/bootstrap.inc:2860
    [Wed Sep 21 10:16:09 2011] [error] [client 128.30.52.70] PHP  11. require_once() /var/aegir/drupal-7.8/includes/bootstrap.inc:2935
    
    yannisc’s picture

    I keep getting the error even after clearing the cache and reloading permissions.

    It appears randomly I think.

    liliplanet’s picture

    subscribe thx, fatal error exists on Chrome and no other browser.

    Have disabled all rules, error persists ..

    fago’s picture

    everyone who still faces the issue, please make sure the "drupal_test_email_collector" is cleared - as described in #53.

    @#54: That backtrace looks totally weird. If rules_exit() is called, rules.module is included and thus the faces autoloader must be registered.

    gagoo’s picture

    I don't have any "drupal_test_email_collector" in my variable table and still have this issue.

    jviitamaki’s picture

    Sub

    liliplanet’s picture

    hmm, drupal_test_email_collector does not exist in my database, that's good i presume :)

    fago’s picture

    Status: Active » Fixed
    StatusFileSize
    new2.09 KB

    ok, seems like this issue persists. I've talked to klausi and we agreed upon moving to the registry for faces inclusion. This makes it impossible to install faces module besides Rules, but that doesn't matter much as I'm not going to further pursue faces. I've marked the faces module as abandoned.

    I've attached the patch I've committed.

    Update-notes: This makes Rules incompatible with the faces module. In case you have the faces module enabled, disable it before updating Rules!

    larowlan’s picture

    Thanks fago

    JGO’s picture

    Well I looks like that the last patch in #61 finally fixed the problem.

    that0n3guy’s picture

    This fixed my issue as well...

    juliakoelsch’s picture

    I was having this issue, and the latest patch fixed it for me. Thanks!

    codesmith’s picture

    Updating to 7.x-2.0 today fixed this for me.

    dangermonkey’s picture

    Updating to 7.x-2.0 today fixed this for me.

    Same here. So far, so good.

    Status: Fixed » Closed (fixed)

    Automatically closed -- issue fixed for 2 weeks with no activity.

    chriscalip’s picture

    Status: Closed (fixed) » Active

    error sighted using 7.x-2.0

    chriscalip’s picture

    Status: Active » Fixed

    Nevermind false alarm. Pardon me. was using 7.x-2.0 release candidate :)

    Status: Fixed » Closed (fixed)

    Automatically closed -- issue fixed for 2 weeks with no activity.