I just experienced a similar problem. Reporting here because the code here fixed it for me.
- User visits a page that displays a custom profile field using S2get
- User updates custom profile field using the profile page
- User revisits page that displays a custom profile field using S2get
- The page displays the old data
- User revisits the profile edit page and it displays the updated data (and so does the admin page)
First I thought this had to do with moving to a new host and caching because it was reported by a user days after a host move, but I was able to replicate on a local install with no caching. I tried downgrading to the last few s2 versions along with a random one from 2023 and still experienced the error.
I put Gerard’s code into my theme functions.php file and changed the custom profile field s2gets to that one and it worked as expected. Note, though, that it only worked with the custom fields. Using the new shortcode on non-custom fields gave blank responses. So what’s currently working is s2Get for the native fields and s2GetPro for the custom ones.