Hi guys,
I am encountering the following PHP warning related to the mod_jevents_latest module:
Error Log:
This warning appears when the cache is cleared, particularly by the "System - Rapi Auto Cache Cleaner" plugin, which I have set to clear cache every 360 minutes. The errors consistently coincide with the cache clearing schedule.
I applied a temporary fix by defining $limitstart at the beginning of latest.php to resolve the warning:
Here's the original:
And the updated code:
The error was displaying on 3 subdirectories (Florida, California and New York) and I updated the core file on Florida only on Feb 6, 2025 and there have been no more errors since. But California and New York still are producing the error.
However, I prefer not to modify core files directly to avoid the changes being overwritten during future updates. Could you verify if this is the best approach and consider implementing a permanent fix in the module's core?
Thank you!
Adina
I am encountering the following PHP warning related to the mod_jevents_latest module:
Error Log:
2025-02-12 14:52:50.147485 [NOTICE] [2224663] [T0] [127.0.0.1:56592#APVH_XXXXX.com:443] [STDERR] PHP Warning: Undefined variable $limitstart in /home/XXXXX/public_html/XXXXX/modules/mod_jevents_latest/tmpl/default/latest.php on line 470\n
This warning appears when the cache is cleared, particularly by the "System - Rapi Auto Cache Cleaner" plugin, which I have set to clear cache every 360 minutes. The errors consistently coincide with the cache clearing schedule.
I applied a temporary fix by defining $limitstart at the beginning of latest.php to resolve the warning:
Here's the original:
$limitstart = intval($limitstart);
And the updated code:
$limitstart = isset($limitstart) ? intval($limitstart) : 0;
The error was displaying on 3 subdirectories (Florida, California and New York) and I updated the core file on Florida only on Feb 6, 2025 and there have been no more errors since. But California and New York still are producing the error.
However, I prefer not to modify core files directly to avoid the changes being overwritten during future updates. Could you verify if this is the best approach and consider implementing a permanent fix in the module's core?
Thank you!
Adina