Just trying to bump this to the top. Having been assured that updating our forum from 3.3.10 to at least 3.3.11 would fix the SQL issue with new registrations custom fields causing a general error as previously posted, but the upgrade did not fix the issue.
I was wondering. Our consultant upgraded us from 3.3.10 to 3.3.12. Could he have jumped right to .12 or would he have had to upgrade to .11 first then to .12. I'm wondering if thats what went wrong if that is what he did? I'd think 3.3.12 and all newer would also have to have the fix and this wouldn't matter, but maybe not.
We really need to get the custom fields working for all new registrations as well as those accounts created since we upgraded to 3.3.10. We are stuck with no direction. Any help would be greatly appreciated.
Thanks
Bruce
I was wondering. Our consultant upgraded us from 3.3.10 to 3.3.12. Could he have jumped right to .12 or would he have had to upgrade to .11 first then to .12. I'm wondering if thats what went wrong if that is what he did? I'd think 3.3.12 and all newer would also have to have the fix and this wouldn't matter, but maybe not.
We really need to get the custom fields working for all new registrations as well as those accounts created since we upgraded to 3.3.10. We are stuck with no direction. Any help would be greatly appreciated.
Thanks
Bruce
Statistics: Posted by brucefenster — Tue Aug 20, 2024 12:14 am