Errors following upgrade to 8.4.6

Resolved aeonflow
(@aeonflow)

6 years, 1 month ago

Hi,

I upgraded from v8.4.5 to v 8.4.6 of Quick Event Manager this morning but when I looked at my website, the following errors appeared at the top of the page:

Warning: date() expects parameter 2 to be integer, string given in /<my-path>/wp-includes/functions.php on line 104

Warning: date() expects parameter 2 to be integer, string given in /<my-path>/wp-includes/functions.php on line 106

Warning: date() expects parameter 2 to be integer, string given in /<my-path>/wp-includes/functions.php on line 109

Any idea what might be causing this?

Excellent plugin by the way. Very pleased with it. Thank you.

The page I need help with: [log in to see the link]

Viewing 13 replies - 1 through 13 (of 13 total)

jafoca
(@jafoca)

6 years, 1 month ago

I had the same issue this morning on one site I manage. I disabled the plugin temporarily, trying to roll back to an older version now.

Thread Starter aeonflow
(@aeonflow)

6 years, 1 month ago

I reverted mine back to v8.4.5 using last night’s backup. Won’t be upgrading until I know what has caused this to happen.

Tried disabling my other plugins in case it was a conflict issue but that didn’t seem to make any difference, the errors still appeared.

Graham
(@aerin)

6 years, 1 month ago

Disable debugging or logout from your dashboard. I’m not seeing the issue on any of my sites so It’s a but difficult to diagnose.

All of the date() calls in the plugin are properly formatted. It doesn’t even need a second parameter so it’s all very confusing.

jafoca
(@jafoca)

6 years, 1 month ago

I did have debugging disabled, and the error was appearing in the header regardless of login status.

The issue was something to do with the styling / js block that the plugin outputs to the site’s header. Let me know if I can help in some way, but I have since rolled back to previous version.

Thread Starter aeonflow
(@aeonflow)

6 years, 1 month ago

I also had debugging disabled and I was logged out when I first saw the error. I’ve since checked a second website I use QEM on and that has the same problem. The second website uses a different membership access system and a different theme too.

I’ve rolled both my websites back to v8.4.5.

Graham
(@aerin)

6 years, 1 month ago

Hmmm….

The plot thickens. I’ve just updated three sites and none of them display any errors. I’ve also looked at the changes in the late update and none of them were to any functions that use the date() function.

Do you have the pro or standard version of the plugin?

Graham
(@aerin)

6 years, 1 month ago

The date function isn’t used anywhere in the styles and JS doesn’t apply to the WP functions.php

And because I can’t replicate the error I’m not sure what to do to fix things

alinesommer
(@alinesommer)

6 years, 1 month ago

We have the same error on https://www.martina-dittmann.de/
Could you please advice what we should do or maybe you can support us with the previous version of quem. Thank you

Graham
(@aerin)

6 years, 1 month ago

The error only seems to be on the event list. There are no errors on single events.

Which lead me to a possible solution.

Please try this update: https://quick-plugins.com/quick-event-manager/qem-update/

alinesommer
(@alinesommer)

6 years, 1 month ago

Thank you, but I have installed the previous version now. And there is no error.

Thread Starter aeonflow
(@aeonflow)

6 years, 1 month ago

@aerin

I just installed the QEM update you posted above and it seems to have solved the problem. No more errors and I’m running v8.4.6!

Excellent! Thank you for your help.

Graham
(@aerin)

6 years, 1 month ago

Excllent!

I’ve updated the version in the repository so this should sort out the problems.

murklan
(@murklan)

6 years, 1 month ago

Thanks for the quick fix! Did’nt seem to update automatically so I had to replace it through ftp. Working now.

Viewing 13 replies - 1 through 13 (of 13 total)

The topic ‘Errors following upgrade to 8.4.6’ is closed to new replies.