@matzgmb - To be more informative, there were plans to move all processes of this mod to the admin, but the changes in 1.5.0 put that on hold till registration is better understood and we can verify that PCI and sanitation will not be broken. All are advised to rename the folder for now and, in some cases, an underscore can be added to the beginning of the directory name. As it is now, the database connection passes PCI scan in all the stores we've installed it in. Of course, you could always put it in it's own database.

@gemae - That would be a major change to the concept that events are helpful "Information" for the customer. Of course, the beauty of open source is that you can "adjust as required."

@slingblade01 - There is no database correlation between the event table and purchases. Even an extraction of orders made during event dates could not provide accurate numbers without knowing if all orders were, in fact, because of the event and not just someone arriving after searching Google.

@jazzman2 - If you are having problems with one-day events or events dropping off the list early, you might find this fix will work.

In includes/modules/pages/events/header_php.php find
$result = $db->Execute("SELECT * FROM " . TABLE_EVENTS . " WHERE (event_stop >= NOW()-1) ORDER BY event_start");
and replace with
$result = $db->Execute("SELECT * FROM " . TABLE_EVENTS . " WHERE (event_stop >= CURDATE()-1) ORDER BY event_start");
Since some ISO's work the date differently, it's a better way of handling the event_stop date anyway.
If we learn from our mistakes, shouldn't I have multiple doctorates by now?