WordPress.org

Ready to get started?Download WordPress

Forums

Please! Anybody please help me as soon as possible... Fatal Error (25 posts)

  1. cjlidua
    Member
    Posted 1 year ago #

    Fatal error: Cannot redeclare bp_dtheme_ajax_querystring() (previously declared in /home/content/15/9594115/html/perants/wp-content/plugins/buddypress/bp-themes/bp-default/_inc/ajax.php:91) in /home/content/15/9594115/html/perants/wp-content/themes/custom-community/_inc/ajax.php on line 81

    here's the site: please check....

    http://www.performingants.com

    I can't access any page... Please help me soon, thanks..

  2. RichardWPG
    Member
    Posted 1 year ago #

    Deactivate your theme and use back default theme to see if this error still exist or not?

  3. Pioneer Valley Web Design
    Member
    Posted 1 year ago #

    I am sorry to note that it appears your site is crashing due to malware:
    http://sitecheck.sucuri.net/results/www.performingants.com/

  4. cjlidua
    Member
    Posted 1 year ago #

    How will I fix it @Seacoast Web Design....

    @Richard I can not access the admin panel... just a blank white page with that error... What will I do?

  5. Pioneer Valley Web Design
    Member
    Posted 1 year ago #

    Start by reviewing and contact your host right away:

    http://codex.wordpress.org/FAQ_My_site_was_hacked

    You can use FTP or your host File Manager to replace files. Make a backup first, but be careful in it's use.

    See also:
    http://wordpress.org/support/topic/268083#post-1065779
    http://smackdown.blogsblogsblogs.com/2008/06/24/how-to-completely-clean-your-hacked-wordpress-installation/
    http://ottopress.com/2009/hacked-wordpress-backdoors/

  6. Hold on here. A PHP Fatal error DOES NOT mean your site was hacked or has malware.

    From Securi:
    PHP Error: Fatal error
    Description: This error happens when a PHP file has a fatal error and is causing the site to crash. It could be related to malware or just a programing error. Either way, it should be fixed because the site is down.

    Please disable or delete all plugins and switch to the default theme (TwentyEleven since 3.3). After making these changes does the problem still occur? If no, re-enable everything one by one to see which component causes the problem.

  7. Pioneer Valley Web Design
    Member
    Posted 1 year ago #

    Hold on here. A PHP Fatal error DOES NOT mean your site was hacked or has malware.

    The files listed would show as malware except they are crashing the site.

    http://forum.avast.com/index.php?topic=90296.0

  8. prionkor
    Member
    Posted 1 year ago #

    @cjlidua:

    Just a FTP software and rename the plugin folder buddypress check on wp-content/plugins to something else. That should remove the fatal error.

    When the site back again do a scan using http://sucuri.net. Don't panic.

  9. cjlidua
    Member
    Posted 1 year ago #

    I do not even have an access to any parts of the website... have tried contacting support on our host and they did not answer my question...

    can anybody please send me a step by step process of all possible solutions regarding this problem, please? I am really in trouble now... thanks to all who replied..

  10. Pioneer Valley Web Design
    Member
    Posted 1 year ago #

    You need to read through and understand the links I posted above. The instructions are there.

  11. ClaytonJames
    Member
    Posted 1 year ago #

    @cjlidua

    The first thing you might try is very similar to what @prionkor has suggested. What you might do, is use your ftp client or the file manager in your hosts control panel to rename the "custom-community" theme folder, rather than the buddypress folder, and see if that lets you fall back on the default buddypress theme, or at least the default WordPress theme. I suspect the custom-community theme may be causing a conflict.

    Give that a try first, and let us know if it changes anything. That might be the logical first thing to try, before getting too far along in your troubleshooting efforts.

    [edit] also, as Chris Olbekson has noted, this is not yet any indication or confirmation that there is currently any active malware on your site.

  12. Pioneer Valley Web Design
    Member
    Posted 1 year ago #

  13. ClaytonJames
    Member
    Posted 1 year ago #

    @cjlidua

    Try Chris Olbekson's and prionkor's suggestions if mine doesn't do the trick for you.

  14. The links posted above have nothing to do with the site in question. The 404 JavaScript was not found on the site by the scanner. The scanner trys to hit known exploit files and because of the fatal error the warnings were generated. Scan again and you will see that once the PHP fatal error was fixed the scan was clean.

  15. Pioneer Valley Web Design
    Member
    Posted 1 year ago #

    Scan again and you will see that once the PHP fatal error was fixed the scan was clean.

    I strongly disagree. I have emailed Sucuri to post to this and set this right.

    The site is crashing due to the existence of this now well known base 64 eval code...good for the host!

  16. ClaytonJames
    Member
    Posted 1 year ago #

    That's a pretty bold statement to make based on just the error code presented. Out of curiousity, what tangible evidence relative to this particular site leads you to such a swift and definitive conclusion?

  17. Pioneer Valley Web Design
    Member
    Posted 1 year ago #

    The files listed at the Sucuri scan are well known malware and not a part of WordPress. Please read the links.

  18. ClaytonJames
    Member
    Posted 1 year ago #

    I think it's possible that you could have misinterpreted or might have overlooked what you were actually seeing in the scan results. I took a look at the site and at the scan results, and there didn't appear to be anything in the results that actually indicated that those files were found on the site. In fact, it did not appear as though the scan ever made it past the fatal php error.

    I thought Chris summed it up rather well in the last reply...

    The links posted above have nothing to do with the site in question. The 404 JavaScript was not found on the site by the scanner. The scanner trys to hit known exploit files and because of the fatal error the warnings were generated. Scan again and you will see that once the PHP fatal error was fixed the scan was clean.

    ...and I agree with that opinion.

    I really didn't see any evidence in that scan report that would justify jumping right onto the hacker-alarmist bandwagon. I'm not saying it doesn't happen, because we all know it does. I'm just saying all I saw on the above site and in the scan results was a fatal php error that needed correcting before any real scan could be performed.

    It isn't your intentions I disagree with, it's just the methodology behind reaching your conclusion so quickly that I was curious about. It's fun learning new ways to detect problems in files on sites you don't have any direct access to, and I thought maybe you had a trick that I haven't used yet.

  19. Pioneer Valley Web Design
    Member
    Posted 1 year ago #

    and I thought maybe you had a trick that I haven't used yet.

    = Experience with issue at hand.

    Nobody was being alarmist.

    Note the site now does not have warnings and is using the same theme.

    As the OP has not returned to explain, the above statement:

    Scan again and you will see that once the PHP fatal error was fixed the scan was clean.

    is wholly speculative.

    The scan noted both a fatal error and files with known bad eval base 64 code it found. I am not sure why that is unclear.

  20. prionkor
    Member
    Posted 1 year ago #

    @all: This is getting old! Lets just drop all these debates and help the guy.

    @cjlidua: Whats the current situation?

  21. ClaytonJames
    Member
    Posted 1 year ago #

    @prionkor

    Your concern for @cjlidua's situation is appreciated, however the issue appears to have already been resolved for quite some time now.

    This is just friendly conversation (as far as I'm concerned) surrounding differing opinions regarding the interpretation of the possible cause a fatal php error based on information provided by an online scan tool that many of us frequently use as a point of reference when looking for possible WordPress threats. I'm simply stating that Seacoast Web Design's immediate declaration of a malware infestation was probably a premature decision base on facts not in evidence and -or- misinterpretation of available information.

    The scan noted both a fatal error and files with known bad eval base 64 code it found. I am not sure why that is unclear.

    Neither am I, because the scan results I saw did not support that statement, and what you thought you might be seeing has already been plausibly explained. So, the only thing that is really wholly speculative, is the assertion that the issue must be caused by malware.

    That's okay, though, because it's all part of the learning process for everyone - including me. I'm certainly open to any other non-speculative input that might convince me that I have misunderstood or misinterpreted the same information you were looking at.

    Beyond that, it's just a matter of agreeing to disagree, and then using what we learn to contribute to a more informed decision making process in the future.

  22. Pioneer Valley Web Design
    Member
    Posted 1 year ago #

    Neither am I, because the scan results I saw did not support that statement

    You are correct in that the results were dynamic. This is the nature of this malware - delete a file - all is well - next you know it is back.

    I suggest we wait for OP to note what was done.

    And yes, the community can disagree, even strongly, but we will continue our best to support it.

  23. ClaytonJames
    Member
    Posted 1 year ago #

    You are correct in that the results were dynamic. This is the nature of this malware - delete a file - all is well - next you know it is back.

    I don't really feel like shooting myself in the foot here, but if I'm wrong, I'm wrong. Are my thoughts on this actually too far out into left field to support my opinion?

    - In this particular case -in the presence of the fatal php error - wouldn't it be very likely that any positive interpretation of a result for malware is invalid simply because of the tools inability to progress beyond the fatal error? As in, the scanner can't even complete an analysis because the fatal php error prevents it?

  24. Pioneer Valley Web Design
    Member
    Posted 1 year ago #

    wouldn't it be very likely that any positive interpretation of a result for malware is invalid simply because of the tools inability to progress beyond the fatal error

    I believe the scanner found the well known malware

  25. ClaytonJames
    Member
    Posted 1 year ago #

    ...And I believe the scanner was incapable of returning those results.

    Do you agree with the opinion that the scanner was not actually able to scan the site due to the presence of the fatal php error that resulted in this message being generated by the scan tool itself?

    From Securi:
    PHP Error: Fatal error
    Description: This error happens when a PHP file has a fatal error and is causing the site to crash. It could be related to malware or just a programing error. Either way, it should be fixed because the site is down.

Topic Closed

This topic has been closed to new replies.

About this Topic