We work with a dev. and test enviroment. When pushing the dev to live we overwrite the SQL tables and hence delete any activity since last deployment.
Can you tell us which tables not to overwrite in "community" to avoid deleting activity? Our guess would be activity, group discussions, and users? Would the system work, if we push new tables/ overwrite the other tables, but not the selected ones. I assume it would out of sync in terms of activity ID etc.?
Of course the safe bet would be not to overwrite anything in "Community", but certain new extensions add to these tables, and that would need to be carried over manually with the risk of missing key changes.
Thank you for contacting us.
Could you tell me a bit more what you're trying to achieve?
What will be the difference between those two databases? What you actually customize?
As far I understand your dev site will be for tests... no real activity will be created there.
And what you're customizing is layout... if so, then you don't need to fiddle with database.
Am I right?
- 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
Yes, it is for testing. But not only layout also implementation of new modules such as InviteX or Social ADs . To my knowledge they amend to the community DB. But it is a general question as new modules/ plugins/ custom code will be added over time.
So it's rather about 3rd party extensions tables. They have own tables and do not add anything into JomSocial tables AFAIK.
But the key is user and members tables as 3rd party cross-relate with them.
At dev site you'll have only test users... there is also no use to move user table.
- 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
