Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • GldRush98

    (@gldrush98)

    Thanks for the fix David. This plugin’s coding was destroying my error logs making them useless. That stopped the error spam.

    Thread Starter GldRush98

    (@gldrush98)

    Indeed it does not seem like the plugin itself but rather something in my environment that is colliding with the plugin some how. I have not figured out what it is.

    I took the time to set up something completely fresh and your plugin works fine under php 8.4 in that environment. Thanks and sorry for the false report.

    • This reply was modified 1 year, 1 month ago by GldRush98.
    Thread Starter GldRush98

    (@gldrush98)

    I deactivated all plugins aside from the Event Calendar and this plugin and I am still getting crashes directly caused by placing the shortcode on the home page.

    [03-Mar-2025 19:42:07 UTC] PHP Fatal error: Possible integer overflow in memory allocation (2 * 3578 + 32) in [DOCROOT]\wp-includes\shortcodes.php on line 273
    [03-Mar-2025 19:42:46 UTC] PHP Fatal error: Possible integer overflow in memory allocation (2 * 3578 + 32) in [DOCROOT]\wp-includes\shortcodes.php on line 273
    [03-Mar-2025 19:43:16 UTC] PHP Fatal error: Possible integer overflow in memory allocation (2 * 3578 + 32) in [DOCROOT]\wp-includes\shortcodes.php on line 273
    [03-Mar-2025 19:43:25 UTC] PHP Fatal error: Possible integer overflow in memory allocation (2 * 3578 + 32) in [DOCROOT]\wp-includes\shortcodes.php on line 273
    [03-Mar-2025 19:43:29 UTC] PHP Fatal error: Possible integer overflow in memory allocation (2 * 3578 + 32) in [DOCROOT]\wp-includes\shortcodes.php on line 273
    [03-Mar-2025 19:43:47 UTC] PHP Fatal error: Possible integer overflow in memory allocation (2 * 3578 + 32) in [DOCROOT]\wp-includes\shortcodes.php on line 273

    Here is the shortcode I use, but ANY shortcode is causing the crash with this plugin.

    [events-calendar-templates template="default" style="style-1" category="all" date_format="full" start_date="" end_date="" limit="6" order="ASC" hide-venue="no" time="future" featured-only="false" columns="2" autoplay="true"]

    If you’re not seeing this, then it could be something unique to my system, but I’m not sure what or what. It’s a fairly basic site, and I run multiple other WP sites with various plugins. So far this has been the one snag with going to 8.4. I can’t figure out why.

    • This reply was modified 1 year, 2 months ago by GldRush98. Reason: redacted site name
    • This reply was modified 1 year, 2 months ago by GldRush98.

    Confirmed fixed here as well. Thanks so much!

    For others experiencing this, it seems to be 3.52 and up. 3.50 is still working fine for me on a windows system.

    Same problem, also on xampp on windows. Every version above 3.50 crashes.

    This path and filename in the error show it’s completely mangled:

    [27-Dec-2023 20:58:24 UTC] PHP Fatal error: Uncaught RuntimeException: C:[REDACTED]\wp-content\plugins\nextgen-gallery/templates\C:[REDACTED]\wp-content\plugins\nextgen-gallery\templates\Thumbnails\default-view.php.php is not a valid MVC template in C:[REDACTED]\wp-content\plugins\nextgen-gallery\src\Display\View.php:284

    • This reply was modified 2 years, 4 months ago by GldRush98.

    Yeah, the “updated” design is pretty awful in every aspect. With the removal of the superior legacy view in 6.0 I have frozen my events calendar plugin version and am blocking all future updates on it. I have spent hours trying to make the new views look nice and actually functional and I’m done wasting my time with it.

    Thank you for the link! 5.1 is a pile of hot garbage; it’s completely broken

    Thanks for this fix. This bug is pretty critical in that it breaks the most commonly used method of updated wordpress sites, using the built-in ftp functionality.
    Took me quite a while to find this page with the fix to get updating working again.
    Such a critical bug like this should have really been caught by WordPress QA before release :-\
    Guess it’s fixed now though. Thanks.

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