PHP Fatal Error get

[Derrill]

[18-Dec-2015 20:43:04 UTC] PHP Fatal error: Call to undefined method WP_Error::getNextDate() in /plugins/events-calendar-prosrc/Tribe/Recurrence.php on line 119

Also am getting this PHP Warning: Invalid argument supplied for foreach() in /plugins/events-calendar-pro/src/Tribe/Recurrence_Meta.php on line 848

Any help is appreciated!

Note: These PHP errors are recurring and are being reported by BPS Pro, which states in their README file:
PHP Error Log General Information
BPS is alerting you that php errors have occurred on your website and logging these errors. BPS is not generating these php errors. In general php errors are a natural thing that will occur on every website intermittently. What is not natural or normal is to see the same php error happening repetitively and continuously. Logged PHP errors should be considered as helpful. PHP errors very accurately display exactly where coding issues or problems are occurring on your website that need to be either looked into or fixed. Fatal php errors need your immediate attention and should be fixed right away.

[George]

Hey @Derrill,

Sorry to hear about these errors. I cannot recreate them and so to get started with some deeper investigating here, can you share your System Information with us? Here’s how to do that → https://theeventscalendar.com/knowledgebase/sharing-sys-info/

Thank you!
George

[Derrill]

This reply is private.

[George]

Thanks for this information! Nothing looks outright problematic here, and I am still unable to recreate these errors on my own testing site, so I’m a bit stumped about why this issue would be appearing.

In your first thread, you mention how this error is being reported by BulletProof Security Pro – to be clear, does that mean that you do not see this error anywhere on your site except for some sort of diagnostic section of the BulletProof Security Pro plugin?

If you do see this error anywhere on your site other than within the sections of the BulletProof Security Pro plugin, can you please clarify where and when on your site this issue arises? Is it when you go to create an event for example? Is it when you click “View All” on a recurring event? Is it when you try and delete an event? Any sort of information like this that you can provide will help.

Thanks for your patience with this! 🙂

Sincerely,
George

[Derrill]

This reply is private.

[George]

Thanks for this extra information!

I unfortunately still cannot recreate this error anywhere on my own testing site, nor do we have any other reports, and so this indeed could just be some sort of “false positive” or misplaced error reporting by that BulletProof plugin. For the record, I have never heard of this plugin – that doesn’t mean much, and I am not downplaying the need for you to tighten down on security, but I am wondering if this error is indeed just arising as a result of some of BulletProof’s “diagnostic” tools.

Any chance you could temporarily disable this plugin, and then instead see if any errors pop up on your site if you head to your site’s wp-config.php file and change this line of code:

define('WP_DEBUG', false);

to this:

define('WP_DEBUG', true);

If the same errors show up when you deactivate that plugin and make the above change, then there is something substantive here and I can rope in a more senior developer than I to investigate this a bit more closely.

For now, however, this does seem to be an erroneous error part on part of BulletProof Security.

Thank you!
George

[Derrill]

This reply is private.

[George]

Hey @Derrill,

Thanks for this update. To be clear, what I meant was to disable that plugin and then also make the changes to wp-config.php that I described, which are as follows:

Head to your site’s wp-config.php file and change this line of code:

define('WP_DEBUG', false);

to this:

define('WP_DEBUG', true);

This step will display errors on your site outside of the context of that plugin, which is the important step here. If the errors only show up in that plugin, but not after making the WP_DEBUG changes above, then this error is something that plugin is erroneously reporting but thus would not actually exist.

I hope this is clear! Apologies for not elaborating earlier.

Please let me know if you make those wp-config changes and, if so, what errors arise if any.

Thank you,
George

[Derrill]

This reply is private.

[George]

Thanks for this information – and for your patience with this issue!

When you set WP_DEBUG to true, if there is an error it will display literally at the top of any page on your site.

Is this the case? The “error” reported earlier is claiming to be a FATAL ERROR, which means that your site should literally be a blank white screen with this error on it once you change WP_DEBUG to true.

1. Does this happen?

2. Does the error display anywhere at all, on the actual front-end of your site?

To clarify, what I would recommend is to head to your site’s wp-config.php file and make the following changes:

Find this code:

define('WP_DEBUG', false);

Change that to this:

define('WP_DEBUG', true);

AND THEN add the following line of code RIGHT BELOW that line:

define('WP_DEBUG_DISPLAY', true );

Save the file, and then see if the error displays on the actual pages of your website itself – not in any logs, not in that plugin, but just literally on the output of the page itself.

Let me know what you find,
George

[Derrill]

This reply is private.

[George]

Thank you for doing this. If the “fatal error” is being reported but your site is still fully operational, then for now I unfortunately cannot see another course of action here except for chalking this up to a fluke from the BulletProof Security plugin’s reporting system.

I cannot recreate this bug anywhere; and it is allegedly a fatal error but is not stopping page load, which a fatal error will do. So I unfortunately cannot see another cause of this other than that plugin causing the weirdness.

This sort of thing can happen – “diagnostic” tools can often misfire or can be too aggressive in pointing out a problem. Even Google’s webmaster tools do this with 404 pages, for example…

Do you have any final thoughts on this matter?

If this error persists but you do not notice any actual problems on your site, then I would recommend considering this a diagnostic error with the BPS plugin and not an actual Fatal Error that occurs on the site.

I appreciate your patience with all of this!

Sincerely,
George

[Derrill]

This reply is private.

[George]

@Derrill, I appreciate your patience with this immensely and am sorry that we couldn’t arrive at a more concrete solution here!

The closing of this thread is not the closing of this “issue” outright – if you ever do start seeing real issues arising on your site, and this error persists and it seems like things are genuinely having problems all of a sudden, please do not hesitate to come back and open a new thread so we can help again.

I will close this thread for now – I wish you the best of luck with your project in the meantime! And once more: come back any time to open a new thread if issues arise again 🙂

Thanks for your patience and politeness throughout our exchange.

Sincerely,
George

[Author]

Posts