stretchwickster

Sure, there are a number of results tables on this page…
https://www.churchrunner.co.uk/results/

1) Regarding the missing age category…
a) From the plugin’s Manage Results facility, pick a result where the age category is missing and note down all the details connected with that result
b) In the wp_wpa_result table, find that same result and let me know what the age_category field is set to.
c) In the wp_options table, find the row where option_name='wp-athletics_age_cats' and let me know what the option_value field is set to.

2) To update the gender of one of your runners…
a) In the wp_users table, note down the number in the ID field for the user you wish to edit
b) In the wp_usermeta table, find the row where user_id matches the number you noted in Step 1 AND meta_key='wp-athletics_gender'
c) In the row found in Step 2, set meta_value to M or F as appropriate

Android browser exhibits the same issue.

Hi Conor,

I believe the storing of a string in an escaped format is not necessary (see https://stackoverflow.com/a/14795856/2047725). Unfortunately, I’m not up to speed in finding my way round the structure of a plugin, but is it possible that backslashes are being passed through to $wpdb->update in the create_user function in wp-athletics-db.php? Interestingly, there’s a comment in the codex that says the $data argument should be raw and not SQL escaped (https://codex.www.ads-software.com/Class_Reference/wpdb#UPDATE_rows). Alternatively, perhaps wp_create_user is adding the backslashes.

If backslashes can’t be kept out of the database, then the best place to remove them would be immediately after querying the database, with a call to stripslashes. I wasn’t certain where to do this, so I opted for the front-end mod instead, as I could clearly see where the data was being displayed.

Hope that helps,
Clive

The User Profile is also a place where the backslash is displayed so I had to edit the appropriate line of WPA.Ajax.getUserProfile to correct it:
jQuery('#wpa-profile-name').html(WPA.stripSlashes(result.name));

Hi Conor,

No problem at all.

The issue was due to the fact that wp_wpa_result.age_category field was defined as a varchar(4) and therefore wasn’t fully storing the age category identifiers which were longer than 4 chars. For example, “C1115” which represents the 11-14 age group was being stored as “C111”. I changed the data type of the aforementioned field to varchar(7) and ran a few SQL UPDATE queries to correct the truncated identifiers. Now everything is working nicely.

In the next release, I’d therefore recommend changing the data type of the wp_wpa_result.age_category field from varchar(4) to varchar(7) to avoid this issue reoccurring.

Hope that’s useful,
Clive

Thanks for the pointer Conor – I’ve added an item to the “default_terrain_categories” array and that works nicely.

Hi Conor,

Once I’ve got some studying out of the way, I’ll have a stab at this and pass it to you for review.

Cheers,
Clive

Thanks Conor.