4.2.7 has been released

  • Improvement: New shortcode for user settings [wlt-user-settings] – Read more: https://weight.yeken.uk/shortcodes/
  • Improvement: New option added to [wlt-chart] “ignore-login-status”. If set to true, will display the chart’s data in the event the user is not logged in (should be used alongside user-id attribute) – Read more: https://weight.yeken.uk/shortcodes/
  • Improvement: Added “Redirect URL” to Form Widget.
  • Improvement: Optimised speed of user preference lookup (if non specified). Previously if the user hadn’t specified any user preferences the DB would have be queried for every key lookup. This was due to an empty array not being cached. Rules have changed to store an empty array to save querying DB for each user preference.
  • Improvement: Standardised Hook / Filter names (possible breaking change if you use these). Read more: https://weight.yeken.uk/hooks-and-filters/
  • Improvement: Added “Neck” measurements.
  • Bug fix: Fixed issue with cache keys for pounds and Kgs conflicting and replacing each other when querying extremes.
  • Bug fix: Ensure both cron jobs are removed on plugin deactivation.

Survey results for new admin area – Version 5.0

Recently I mailed plugin users asking for their opinion on improving the admin side of the plugin;  In particular, I wanted them to focus on methods / interfaces for accessing their members data in meaningful ways and allow their coaches to aid their members better.

Firstly, thank you all for your replies – they have been great. Besides showing me I’m thinking in the right direction, they have given me some great ideas.

Draft 5.0 Release

I’ve decided that the new admin area will be version 5.0 as it will hopefully bring a large improvement to the plugin. From your feedback, it will have (at least) the following features:

  • An admin summary page with the following features:
    • Stats around the number of members that have added weight entries.
    • Stats around who has lost the most weight over a filterable time scale.
    • A search bar that allows administrators to search for a given member.
  • Each member will have a “record card” which allows administrators to quickly see the following:
    • Quick summary data: Start weight / date, recent weight / date, target weight, height, current BMI, etc.
    • All of their entries in tabular format (with the 10 most recent displayed first).
    • A graph showing their entries (to replicate what the user would see in the front end).
  • Ability to add, edit and delete all user entries.
  • Improved data tables.
    • View all columns at once without the need to expand rows.
    • Toggle on and off columns that are not of interest.
    • Sort by all columns.
    • Visual indicator to show whether the user gained or lost weight between entries.
  • Ability to print charts (this requires further research to see if possible)
  • Increase granularity of entries. Some users are interested in knowing additional data about a person’s entry. So I’ll look into adding extra information like timestamps, IP addresses, user agents, etc.
  • Export data in CSV / JSON formats.

Timescales

Currently I’m on track with my aims, however before really starting on 5.0 I want to work a little more on 4.2. I have some small enhancements logged that would be quick wins to add.

So hopefully I will do some wire frames over the next few weeks and then take it from there.

So guess we maybe around June / July – hopefully earlier.

4.2 Release coming soon

Hi folks,

Just to let you know, 4.2 release is progressing well and now going into the testing stage. You can track it’s progress on our GitHub page:

https://github.com/yekenuk/Weight-Loss-Tracker/projects/2

A preview of 4.2’s release notes:

  • New feature: Message shortcode to motivate people when they gain weight x number of times or congratulate if they lose weight x number of times. – Read more: https://weight.yeken.uk/shortcodes/
  • New feature: Reminder shortcode to display reminder messages for users to add a target weight or weight / measurement entry for the day. – Read more: https://weight.yeken.uk/shortcodes/
  • New feature: Progress bar towards target [weight-loss-tracker-progress-bar] – Read more: https://weight.yeken.uk/shortcodes/
  • New Feature: Added widget for progress bar shortcode above. – Read more: https://weight.yeken.uk/widgets/
  • New feature: Email notifications for update of user’s target or adding / editing a weight entry: https://weight.yeken.uk/email-notifications/
  • New feature: New attribute “redirect-url” added for the shortcode [ws_ls_shortcode_form]. If specified and once the data has been saved, the user will be redirected to the given URL. Please note, the URL has to be one for the current site, otherwise the redirect will not happen (URL is passed through wp_safe_redirect()). Read more https://weight.yeken.uk/shortcodes/
  • New feature / improvements: Additional hooks and filters added. Read more:
  • Improvement: Added the following to [weight-loss-tracker] shortcode: ‘hide-first-target-form’, ‘hide-second-target-form’ and ‘show-add-button’. Read more: https://weight.yeken.uk/shortcodes/
  • Improvement: Every license activation is now sent to YeKen.
  • Improvement: Stats now sent weekly (instead of monthly) using a WP cron job. If “Send usage data to YeKen” is enabled, usage stats will be sent on weekly basis to YeKen by a scheduled WP cron job (instead of relying on an expired cached value to trigger the send).
  • Improvement: Upgraded Chart.js to 2.5.0.
  • Bug fix: Setting “min-chart-points” attribute to 0 will now display the chart if no weight data has been entered.
  • Bug fix: Issue generating stats for a user when a target weight is entered but no user weights exist (division by zero).
  • Bug fix: Stats are instantly tidied up / re-generated if all user data is delete or an individual user deletes their data.
  • Bug fix: If no target weight has been set, the shortcode will now inform the user when the shortcode [ws_ls_weight_difference_target] is rendered.
  • Bug fix: Weight loss comparison figures shown properly when in stone / pounds.
  • Bug fix: When using [weight-loss-tracker-total-lost], Kg values are now rounded to two decimal places.