You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating to 3.0 and changing from meta to data as prescribed, point values are not transferring and not showing in badges created previously. This also is showing up as zero in badge edit mode in the points section.
Steps to Reproduce
To find old points data in MySQL: SELECT u.ID, u.display_name, u.user_email, p.post_date, pm.meta_value FROM wp_posts p JOIN wp_users u on u.ID = p.post_author JOIN wp_Postmeta pm on pm.post_id = p.id WHERE pm.meta_key = "_badgeos_awarded_points"
2. Compare to SELECT * FROM wp_badgeos_achievements
Find all old point values: SELECT p.ID, p.post_title, p.post_content, pm.meta_key, pm.meta_value FROM wp_posts p JOIN wp_postmeta pm on p.ID = pm.post_id WHERE pm.meta_key = "_badgeos_points"
Actual result:
Got zeros for any new badges achieved so far.
Expected result:
Get old point values for new badges achieved.
Product Versions
BadgeOS: 3.0
WordPress: 5.2.2
The text was updated successfully, but these errors were encountered:
After updating to 3.0 and changing from meta to data as prescribed, point values are not transferring and not showing in badges created previously. This also is showing up as zero in badge edit mode in the points section.
Steps to Reproduce
SELECT u.ID, u.display_name, u.user_email, p.post_date, pm.meta_value FROM wp_posts p JOIN wp_users u on u.ID = p.post_author JOIN wp_Postmeta pm on pm.post_id = p.id WHERE pm.meta_key = "_badgeos_awarded_points"
2. Compare to
SELECT * FROM wp_badgeos_achievements
SELECT p.ID, p.post_title, p.post_content, pm.meta_key, pm.meta_value FROM wp_posts p JOIN wp_postmeta pm on p.ID = pm.post_id WHERE pm.meta_key = "_badgeos_points"
Actual result:
Got zeros for any new badges achieved so far.
Expected result:
Get old point values for new badges achieved.
Product Versions
The text was updated successfully, but these errors were encountered: