6.0.0-beta1
9/24/25

[#4775] adv_results_placement preference has no effect
Summary adv_results_placement preference has no effect
Queue Turba
Queue Version 2.1.3
Type Bug
State Resolved
Priority 1. Low
Owners
Requester Otto.Stolz (at) uni-konstanz (dot) de
Created 12/13/2006 (6860 days ago)
Due
Updated 12/13/2006 (6860 days ago)
Assigned
Resolved 12/13/2006 (6860 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
12/13/2006 04:33:29 PM Chuck Hagenbuch Comment #2
State ⇒ Resolved
Reply to this comment
I've removed the preference since it's not used anymore and the search 
forms have been unified for a while now.
12/13/2006 02:46:51 PM Otto (dot) Stolz (at) uni-konstanz (dot) de Comment #1
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ adv_results_placement preference has no effect
Queue ⇒ Turba
New Attachment: turba-prefs.txt Download
Reply to this comment
Regardless of the user's current adv_results_placement setting, the 
results of both Basic and Advanced Search are placed below the search 
form.



I have defined two addressbooks:

- localsql: personal addressbook per user,

- localldap: common addressbokk, no browsing, no export (would like to 
have it read-only, but did not succeed yet in configuring it so)

I have tested this issue with both of them: always the same result. I 
have also checked the pertinent horde_prefs entry (in MySQL database) 
to be sure that the option had indeed be set for this user (cf. 
attacment).

Saved Queries