Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: Liferay files/folders are not getting synced with the sync connector v6
I have used Liferay version 6.2.
Liferay files or folders are not getting synced with the sync connector for following reasons :
1. The liferay table which store all the files & folder information for the data syncing name as "syncdlobject"
2. The column which will create the reference for each resource with the resource master table ( "dlfolder", "dlfileentry") is "typeuuid". The referenced column for 'dlfileentry' & 'dlfolder' is :" uuid_".
3. I have deleted one resource record from the "syncdlobject" table ( the liferay instance where sync is working ) I tried to connect the sync client but the sync client can not find the resource which got deleted from the db record .
4 .So only "syncdlobject" is responsible to get connected with the sync client & somehow the data inconsistency rather reference mismatch happened , resulting the sync problem at Liferay instance .
5 . I have not got any possible solution to revert the data if there is any inconsistency at that sync table . I have tried with below property change in portlet properties :"sync.verify=true"but it did not work . .
PLEASE HELP ME WITH POSSIBLE SOLUTION IF THIS TYPE OF PROBLEM OCCURRED .
Liferay files or folders are not getting synced with the sync connector for following reasons :
1. The liferay table which store all the files & folder information for the data syncing name as "syncdlobject"
2. The column which will create the reference for each resource with the resource master table ( "dlfolder", "dlfileentry") is "typeuuid". The referenced column for 'dlfileentry' & 'dlfolder' is :" uuid_".
3. I have deleted one resource record from the "syncdlobject" table ( the liferay instance where sync is working ) I tried to connect the sync client but the sync client can not find the resource which got deleted from the db record .
4 .So only "syncdlobject" is responsible to get connected with the sync client & somehow the data inconsistency rather reference mismatch happened , resulting the sync problem at Liferay instance .
5 . I have not got any possible solution to revert the data if there is any inconsistency at that sync table . I have tried with below property change in portlet properties :"sync.verify=true"but it did not work . .
PLEASE HELP ME WITH POSSIBLE SOLUTION IF THIS TYPE OF PROBLEM OCCURRED .
Did you re-deploy the portlet after setting "sync.verify=true"? Can you enable logging for com.liferay.sync.* and share the logs? You should see messages regarding the verification process when the portlet is redeployed.
Thanks Dennis,
version used :
Instance version 6.2 GA6; sync connector version : liferay-sync-3.4.4-ga5
I have stopped the server & changed the property going to following path . Then I have restarted the server . Will that work? path : liferay-portal-6.2-ce-ga5\tomcat-7.0.62\webapps\sync-web\WEB-INF\src\portlet.properties
I could not get the war file to redeploy the sync web portlet as it is out of box portlet . Please suggest me how to get the portlet to change in war file to re deploy .It will be good if I get the steps .Thanks in advance
version used :
Instance version 6.2 GA6; sync connector version : liferay-sync-3.4.4-ga5
I have stopped the server & changed the property going to following path . Then I have restarted the server . Will that work? path : liferay-portal-6.2-ce-ga5\tomcat-7.0.62\webapps\sync-web\WEB-INF\src\portlet.properties
I could not get the war file to redeploy the sync web portlet as it is out of box portlet . Please suggest me how to get the portlet to change in war file to re deploy .It will be good if I get the steps .Thanks in advance
Try using the latest version of the Sync Connector available on the Marketplace here: link. Try running sync.verify again on the latest version.