Bug 99716 - Store recent documents list and thumbnails apart from registrymodifications.xcu
Summary: Store recent documents list and thumbnails apart from registrymodifications.xcu
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: framework (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevEval, topicUI
: 90094 103445 (view as bug list)
Depends on:
Blocks: User-Profile
  Show dependency tree / graph
 
Reported: 2016-05-07 00:37 UTC by Todd
Modified: 2017-06-11 11:45 UTC (History)
7 users (show)

See Also:
Crash report or crash signature:
Regression By:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Todd 2016-05-07 00:37:04 UTC 
LibreOffice_5.1.2_Linux_x86-64_rpm.tar.gz

Dear Libre Office,

User profiles corrupt a lot after upgraded.  (It is really a common occurrence for me.)  See bug 99490 for lost spell checker.

Now the custom dictionary is easy to copy back from the old corrupted profile but the recents are not as it is included in registrymodifications.xcu.

Request for Enhancement:  Please break the recents into their own file so they can be easily restored after having to create a new profile.

Many thanks,
-T
Comment 1 Cor Nouws 2016-05-07 08:31:10 UTC 
Thanks Tod.

The idea is logic. Not sure if in the end the price (engineering, performance, maintenance) is worth the gain, but others can decide that.

Cor
Comment 2 m.a.riosv 2016-05-07 16:14:28 UTC 
Usually it's enough renaming/deleting the file "user/registrymodifications.xcu",  it affects all the options in Menu/Tools/Options, and the files "user/basic/dialog.xlc" and "scrip.xlc" are overwritten, additionally custom colors in "user/config/standard.soc" are lost.

Maybe this could help in your case.
Comment 3 Heiko Tietze 2016-09-16 08:56:21 UTC 
Closing as WONTFIX since suggestion from m.a.riosv is a good workaround. Basically updates must not break old profiles. Please file a bug report if this happens again.
Comment 4 Heiko Tietze 2016-09-16 08:57:35 UTC 

*** This bug has been marked as a duplicate of bug 57466 ***
Comment 5 Cor Nouws 2016-09-19 16:37:27 UTC 
(In reply to Todd from comment #0)

> Request for Enhancement:  Please break the recents into their own file so
> they can be easily restored after having to create a new profile.


(In reply to m.a.riosv from comment #2)
> Usually it's enough renaming/deleting the file
> "user/registrymodifications.xcu",  it affects all the options in
> ....
> Maybe this could help in your case.

deleteng registrymodifications.xcu also deletes the recent files, so I don't see how this can be a solution.

(In reply to Heiko Tietze from comment #3)
> Closing as WONTFIX since suggestion from m.a.riosv is a good workaround.

nor a work around ;)
Comment 6 V Stuart Foote 2016-09-19 17:21:56 UTC 
If you delete the profile, the MRU list and support for thumbnail views is purged. 

Moving the Histories stanzas from the registrymodifications.xcu to a HISTORIES directory would make it a bit easier to copy that directory prior to clearing profile, and then restore it reliably.

To be honest when QA testing I am sometimes reluctant to clear my profile because I would prefer to keep my MRU list and the Thumbnail views. Placing the MRU and history into its own folder would encourage me to work with a clean profile more often knowing I could restore my MRU list without fuss.
Comment 7 Regina Henschel 2016-10-24 15:24:51 UTC 
I support the request to store the recent files list becide the registrymodifications.xcu.
Storing the history, more exact the link and the thumbnail of each file in the registrymodifications.xcu, makes the file huge.
Comment 8 Kumāra 2016-10-25 04:03:52 UTC 
*** Bug 103445 has been marked as a duplicate of this bug. ***
Comment 9 Stephan Bergmann 2016-10-25 08:52:17 UTC Comment hidden (obsolete)
Comment 10 V Stuart Foote 2016-11-15 13:37:26 UTC 
*** Bug 90094 has been marked as a duplicate of this bug. ***