I could recommend backing up your database (just in case) installing Register Plus Redux, mirror your settings from Pie Register, and then disable Pie Register. All the data is stored in the same manor, the only breaking changes are for select (dropdown) fields. Plain text fields should migrate without issue. If it doesn’t work the way you expect, you should be able to just disable Redux and enable Pie Register (and you have a backup for worse case scenario).
Could you explain how this will fix the existing website profile field issue? Will it wipe out what’s there and make a new table in the database?
It will not wipe out what is there, however, it’s not going to fix any issue either (in regard to the Website field) because there is no issue, that was a Register Plus (and subsequent Pie Register) issue, which I resolved. That’s kind of mumbo jumbo… The thing is, you could stop using your “website” field and use WordPress’ defined website field, however, the website of your existing 274 users is stored in your “website” field, not the WordPress one, so you need to move that data over somehow, or just keep using your “website” field. Does that make any sense? I have a hard time conveying these things sometimes.
Ok. I’ll try this and see what she does.
Wait hold on…
I just reread what you wrote. It doesn’t fix my problem…
however, the website of your existing 274 users is stored in your “website” field, not the WordPress one, so you need to move that data over somehow, or just keep using your “website” field
This is the problem. None of these existing subscribers can edit the website field. That is the entire problem and what I am looking to get fixed.
Now, if this visibly disables the old website field and uses the correct one, I can just send out an email to let them know they need to update their profiles.
Had a chance to install Redux and it did not fix the problem. The website field is still not editable.
