- change the processing of slowsync, to use the content_map instead of
trying to build a new one. This caused duplication issues on the
client if multiple similar records where stored, because only the first
one found in the server-db was matched, These duplicate entries at client
side had no entry at serverside, so deleting the wrong one
on the client (the content with a valid map entry) could cause
unwanted data loss at server side, because it is impossible for the
user to see what is a duplicate, and what is not.
see also:
http://www.nabble.com/again---syncml-duplication-issue-to20333619s3741.html
- reenabled UID from syncml clients, because it was partly used this caused
issues during SlowSync if the content was changed.
- infolog, calendar if a uid is found in the provided data, allway try to
find the corresponding content first using only the UID, instead of
using the content-id taken from content_map.
also fixed:
- a few fixes in ./notes
- creating an entry on the client that can not be imported,
(Example, Nokia E Series Appointment without a Title)
will no longer create an invalid content-map entry
However, at client side this is still counted in the Protocol as
Server-Add
get_rows($value,$rows,$readonlys) instead get_rows($value,$value['rows'],$readonlys)
because $values['rows'] as reference would be stored in the session, when apps store $query parameter in the session
"
- check and give error message if perms could not be changed
- added sudo feature to file preferences allowing to get VFS root access
+ setup config user/password can always be used
+ further eGW users can be configured in setup >> configuration
--> allows eg. to create free folders in the vfs root
--> should be used with caution and respect to users privacy
- added file preferences icon to opened directory (eg. for the root dir)
link)
- made bo_tracking abstract
- added default return null to bo_tracking::get_config and removed it
from extensions implementing no config
- fixed signature of get_config($name,$data,$old=null)
manufacturer and the recogniced GroupDAV client as product name.
This way we are able to handle different GroupDAV clients, as we
allready do with different SyncML clients.
Also removed the no longer needed code enabling the use of the real UID,
as SyncML does no longer misuse the UID for it's GUID.
