Tickets :: Comment on [#7319] Add different import methods or logics for syncml vs. inter-application imports

* Your Email Address
* Spam protection	Enter the letters below: .___. ..__ .__ .__ [__ \|__\|[__)[ __[ __ [___\| \|\| \[_./[_./
Comment	>>>> Upgrading from Horde 3.1 to Horde 3.2 raises an issue about the > >>>> format of the pref['default_dir'] which contained 'localsql' (Horde > >>>> 3.1) and should now contain 'firstname.lastname' (Horde 3.2). > >>> > >>> I have no idea what you mean with this sentence. > >> > >> We had a Horde 3.1 platform, and now we are moving to Horde 3.2 but > >> we are keeping the same database. So values of user options are kept > >> (from horde_prefs table). We notice that the format of the > >> ['default_dir'] option has changed between Horde 3.1 (it was > >> localsql) and Horde 3.2 (it is now firstname.lastname). > > > > Is "firstname.lastname" the user name, i.e. the name that users use > to login with? Otherwise it doesn't make any sense, because the > address book names have nothing to do with names. > > > > If this is the user name, then this is the correct behavior, if you > use shares with the localsql source. Read the upgrading instructions > and check the mailing list archive. > > > > Regarding the default_dir vs. sync_books, there is not much we can do > at the moment, because the import function is not only used for > SyncML but for other imports too.
Attachment
Watch this ticket