Welcome the Technical Support section. Help us in assisting you by providing us with a concise and descriptive elaboration of your issues. Be specific and if possible, provide us with a step-by-step instruction in replicating your problem.
Can't Save Multiple Profile Fields Settings JS v 3.2.1.2
1. I created two Multiple Profiles, Professional and Business.
2. Under the Customize Profile settings I created additional fields that I would use to assign to one of the 2 multiple profiles
3. Then I assigned all the Default Profile Users to the Professional Profile via phpmydamin.
4. I want to disable certain fields on each of the profile types. However, when I change those fields settings to NO, they revert back to YES after I SAVE the profile field settings. See attached screenshot for reference.
Please advise on what is causing this problem. It seems like an obvious bug to me. I am using jomsocial v 3.2.1.2 on Joomla v 3.3. Also, let me know how I can solve this problem. Thanks.
Attachment Screenshot2015-03-1102.21.54.png not found
- Instead of saying: 'it's not working', explain the problem in detail.
- Screenshots with the URL visible in them and the problem marked are more than welcome.
- Tell us how to replicate the problem, we can't fix it if we can't find it.
- Make sure that your site/server meets JomSocial System Requirements
- Make sure to setup JomSocial Cron Job
- Always provide us with access details to the backend and ftp. We need it to debug problems.
- If you have a similar problem, but a solution you found isn't working, open a new thread instead of 'merging' with an existing one.
- Use the "Thank You" feature on any post that helped you
It seems odd to me that this bug would have slipped through the cracks. You are promoting a community site with Multiple Profiles but yet you can not even SAVE the profile settings. Our version of jomsocial has been extended extensively. An upgrade at this point is out of the question. Can you tell me which files exactly were updated to fix this issue? We may have to extend those files ourselves to fix this bug without having to upgrade the entire source code.