Duplicate Custom user fields is not showing up

KSA

Well-known member
Affected version
2.1.0
After upgrading, custom user fields is not showing up despite having the option checked in Style Properties. It requires users to re fill the custom user fields again. It should respect the first attempt.
 
Last edited:
I'm now sure that this is the same issue as that report, though you'll see that we're still investigating the necessary fix.
 
Last edited:
I'm about 95% sure this is the same fundamental issue as this: https://xenforo.com/community/threads/serialised-content_info-array-not-converted-to-json.156525/ (All of the JSON conversions use basically the same code.)

I'll be posting a possible fix there momentarily. If you're able, please restore to a 2.0 backup and try the upgrade again after the code change.

unfortunately I wont be able to restore to a backup as the one I have is way old as my host supposed to do that periodically but just got their response that they have not done a backup yet :(

Is there a way to rebuild the user fields and bring it back again?
 
Don't you think it is slightly irresponsible that you upgraded to an unsupported version of the software, that is in its first beta, despite many warnings that you should only do so on a dev/test environment and even then only when you've explicitly done a backup?

As it happens, you should be able to use the "Rebuild users" rebuild in the Admin CP for this specific case, which is lucky, but unfortunately we'd have no way of knowing if there is other data which has been affected.

Luckily we may be able to help you fix this retroactively but, seriously, we don't give people these warnings for the sake of it. It really does matter.
 
Don't you think it is slightly irresponsible that you upgraded to an unsupported version of the software, that is in its first beta, despite many warnings that you should only do so on a dev/test environment and even then only when you've explicitly done a backup?

As it happens, you should be able to use the "Rebuild users" rebuild in the Admin CP for this specific case, which is lucky, but unfortunately we'd have no way of knowing if there is other data which has been affected.

Luckily we may be able to help you fix this retroactively but, seriously, we don't give people these warnings for the sake of it. It really does matter.

I admit my mistake but I thought since my host do backups every 24hrs is enough for me to find it at my disposable in time of need.

Now I have learned my lesson of the day.
 
Sometimes that's the best way to learn 😉

If you can do the "Rebuild users" rebuild under Tools > Rebuild caches in the Admin CP and let us know if that solves it. It may be worth us talking you through re-running the steps that might have gone wrong after Beta 2 is released but do let us know if you find anything else that doesn't work.
 
Sometimes that's the best way to learn 😉

If you can do the "Rebuild users" rebuild under Tools > Rebuild caches in the Admin CP and let us know if that solves it. It may be worth us talking you through re-running the steps that might have gone wrong after Beta 2 is released but do let us know if you find anything else that doesn't work.

Unfortunately doing the rebuild does not fix the issue.😟
 
Can you submit a ticket with the following:
  • Admin CP login
  • Database login (PhpMyAdmin is ideal)
  • Details of an account/accounts where we can see the problem for ourselves
 
Cancel that, we've just spotted an issue with that approach.

The update to Beta 2 should fix the issue for you, as long as you can wait until tomorrow.
 
Cancel that, we've just spotted an issue with that approach.

The update to Beta 2 should fix the issue for you, as long as you can wait until tomorrow.

Sure I can wait. Also the reaction does not show the username of that person who gave the reaction. It says 1 Person and if more it say x people. Not sure if this is a bug or what it is.
 
Back
Top Bottom