Version 1.3.0b1:
- Change: chart_change, chart_direction and chart_new_entry now compare an item's position with the same chart 7 days earlier, filtered the same way - they used to compare with the item's all-time rank
- Change: A computed chart is cached per chart and viewing user, so showing the same chart list again no longer recomputes it
- Change: If a chart's start day has no stored history, the nearest earlier day (up to 7 days) is used
- Change: A chart that cannot be built (no item has the chart field, or no history for chart_day_end) shows no results instead of an unordered list
- Change: Chart history and the Chart Fields tool only use DataStore keys ending in "_count", and the tool marks Disabled Modules
- Bug Fix: Chart lists failed with a PHP 8 error when a quota did not allow charts and no allowed item had a value for the chart field
- Bug Fix: Chart history for a field larger than the MySQL max_allowed_packet setting could not be stored, and the error ended the nightly maintenance run
- Bug Fix: A chart with a search condition and a limit showed fewer items than the limit
- Bug Fix: Chart positions on page 2 and later were one lower than they should be
- Bug Fix: A chart list that only counted items added chart values to the next list of the same module
- Bug Fix: Text fields with "_count" in the key name (i.e. user_country) were stored as chart history
- Bug Fix: PHP 8 warning for charts using chart_day_start or chart_day_end
- Developer: Chart history is stored in rows of up to 1MB, written with as few multi-row INSERT queries as MySQL max_allowed_packet allows (the history table is updated when the module is upgraded)
Version 1.2.1:
- Change: Repair functions that were being run during an Integrity Check moved to Repair Check
Version 1.2.0:
- New: Updated nightly chart history inserter to work regardless of MySQL max_allowed_packet setting
- Change: Updated view structure to support new updates in Jamroom Core 6.5.12+
- Change: Nightly maintenance event updated to be lighter on the system when inserting history
Version 1.1.3:
- Change: Updated to use Core provided DS functions when generating chart history to save memory
- Bug Fix: Date nightly chart history was being generated for could by off by 1 day
Version 1.1.2:
- Bug Fix: Some chart comparison values could be ordered incorrectly
Version 1.1.1:
- Change: SQL Query updates to make daily chart creation a bit faster
Version 1.1.0:
- New: "Disabled Modules" global config option to disable storing of Chart History for specific modules
Version 1.0.9:
- Bug Fix: chart history table not being reset during a Developer Tools -> System Reset
Version 1.0.8:
- Change: Updated module icon
Version 1.0.7:
- Bug Fix: Previous position number could be incorrect on multi-page charts
Version 1.0.6:
- Bug Fix: Chart ordering not always correct
Version 1.0.5:
- Bug Fix: Chart Fields Tool checks that module is using a DataStore before listing keys
Version 1.0.4:
- Bug Fix: invalid chart history entries now removed during an integrity check
Version 1.0.3:
- Bug Fix: If order_by parameter is not set, set to chart_field numerical_desc
Version 1.0.2:
- Change: Checks to ensure DS table exists before running count query
Version 1.0.0:
- Initial Release