Apache OpenOffice (AOO) Bugzilla – Issue 16924
File/Templates/Organize is incomplete
Last modified: 2013-02-07 22:33:18 UTC
Set-up: Put new templates in the ~/user/template folder. Put other templates in the <wherever>/OpenOffice.org1.1/share/template/english folder. Test: 1) File/Template/Edit gives the complete list of templates. 2) File/New/Templates and Documents gives the complete list of templates. 3) File/Template/Organize gives only those templates in the "net" directory. Expected behavior: All methods should show all templates from all directories found in Tools/Options/OpenOffice.org/Paths.
CORRECTION: (Reminder to Self: Self -- never rely on memory!) File/Template/Edit is the one that gives me only the list of subdirectories in the system directory. It does NOT give me any of the user templates. This behavior was not seen in 1.0.1, 1.0.3.1 or 1.1beta2. It is a new "feature" of 1.1 RC1.
I don't know if this is the same issue. But when I am in the Template management window (File/Template/Organize), and choose Commands/New, when I have one category selected, nothing happens. This is new in 1.1RC compared to 1.0.3
move to component framework
Reassign issue to owner of selected subcomponent
I will check this tomorrow in RC3 and see if it works. I hope it does. will report.
RC3: File/New/Templates and File/Templates/Organize show the full collection of templates. File/Templates/Edit shows only the templates in the system installation -- every time it is loaded, so I have to go through quite a collection of steps to navigate to the actual template directory. It's a change from RC2, but not a good one.
Ran "repair" both as root (./setup -net) and as user. It found Java (apparently did not when running install.sh). I had to remove the system folder reference to templates and add it so it would be second and not first. Now it works. Perhaps we should think about where templates are normally put. If put in the system folder, the default setup is okay, but if placed in the user folder, the default setup is simply wrong. A simpler setup might be to have the files movable (up and down keys for the Tools > Options / OpenOffice.org > Paths) so that multiple entries could be easily changed by users. That would certainly be easier than asking a novice to search through the folders to find files and having to "know" what to do to fix the problem.
.
TM->BH: I changed this from DEFECT to ENHANCEMENT because of a bad usability. Please have a look and decide if the setup should act and create path-entries in a different way to avoide those problems. Thanks !
1.1.1rc (linux). File > Templates > Organize shows the templates for the first of the paths listed in the Tools > Options > OpenOffice.org: Paths, but none of the other templates. Further, there is no way to navigate to the other paths to find the full collection of templates. This makes File > Templates > Organize useless where the majority of templates are stored other than in /opt/OpenOffice.org1.1.1/share/templates/english unless that directory is deleted and then readded so it comes at the end of the list. Unfortunately, doing that means that templates in the system file (.../templates/english) are then unavailable to the Organizer dialog. The same issue exists with File > Templates > Edit, except that navigation is possible, but the navigation makes a mockery of the Path declaration in the Options dialog as it is not automatically included or automatically selectable. I might ask why the Path declaration permits more than one path when only one path is actually used and you can freely navigate all over the place using the Edit mode. It would seem to me that the templates in all declared paths would be shown.
1.1.2rc: Files > Templates > Organize shows names of files from File > Properties. Files > New > Templates and Documents AND Files > Templates > Edit shows the actual file names. Sometimes the two differ. Expected: All versions should show the same options -- a name from Files > Properites or the file name when Files > Properties has a blank for the name.
To grep the issues easier via "requirements" I put the issues currently lying on my owner to the owner "requirements".