Empty existing profile fields on existing site

[NoobyNoob1966]

When I install profile manger and create different profile types on existing site, all existing users profile pages do not display any of their fields that were filled before.
All "Default" profile fields were imported through manager and added to "free user" profile category/profile type. This profile type is set to be a default in manager. When I go to edit these profiles, all fields data are still populated but until I click save, these fields do not display on profile page.

This is a problem on a site with lots of existing users. Any quick workarounds for this?
Thanks.

[NoobyNoob1966]

I looked into profile_manager\views\default\profile\edit.php and compared with default profile\edit.php file, profile manager calls $value = $user->$metadata_name; while default profile edit file calls $value = $user->$shortname;
So it seems like user metadata has not been saved yet (until you click save) therefore it's not displaying even with default fields imported and info in those fields are still visible.
Maybe some kind of php if statement that checks if default fields exist and have any values in them could solve it.

[jdalsem]

This will not be solved, as it makes sense that it works in this way. The default profile type is only applied for new users. If you move all default profile fields to the 'free user' profile type, the will not be visible on existing users as they are not a 'free user'.

Why not use the default profile type as the free user? If that is not an option you will have to create a script to add all users to the new profile type.

[NoobyNoob1966]

Thanks for looking into the issue.

The problem with using "Default" for free user is that "Default" category/fields are displayed in any profile type so that beats purpose of having different profile category/profile type.
I've tried what you suggested but like I said "Default" fields were showing in my other profile type as Category.

Can you look into that aspect?

[jdalsem]

Default is supposed to be on all profile types, as they are the default fields for all users. If you have specific fields per profile type, you need to move them to profile types (with their own categories). However if the usecase is that you have fields that are for "default", but not for a specific profile type, you can not use this approach.