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.
Required to log in when accessing detail page of private message
After I upgrade Jomsocial to 3.2.0.5, System required new user to log in when they want to read their private message.
This problem only occur with new user who registering to system after upgrading Jomsocial 3.2.0.5
I request my developer to investigate and the problem is record for new user in Joomla database lack of a param.
That param is ' "update_cache_list":1'.
We found that Jomsocial create and use this information.
Currently, It is very hard for us to fix this because we don't understand source code of Jomsocial.
We need help from you to fix this.
Reproduce steps:
- Create new user.
- Send a private message to above user.
- Log in by user have just created.
- Read detail of private mesage.
I am very appreciated if you can help me resolve this.
Thank you and best regards.
Please, upgrade to JomSocial 3.2.0.7 and check if issue persist.
- 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
This problem is resolved after upgrading Jomsocial.
But I did that on our test site but production site.
Could you please help me to quickly resolve this problem in 3.2.0.5 ?
We have a lot of customization on Jomsocial. Therefore, We still not update Jomsocial now on production site.
Hmmm, many files and code parts was fixed from 3.2.0.5 to 3.2.0.7... so it will be extremely hard to provide separated fix... As it's bundled...
I'm afraid that you'll have to upgrade... or try so search forum for similar issue. If thread will be solved it could contain fix files for that issue or fix code...
That's only I can advise...
- 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