[Tickets #2874] Not prefixing with personal namespace
bugs@bugs.horde.org
bugs at bugs.horde.org
Mon Nov 7 17:45:44 PST 2005
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/?id=2874
-----------------------------------------------------------------------
Ticket | 2874
Updated By | Michael Slusarz <slusarz at mail.curecanti.org>
Summary | Not prefixing with personal namespace
Queue | IMP
Version | HEAD
State | Assigned
Priority | 2. Medium
Type | Bug
Owners | Jan Schneider, Michael Slusarz
-----------------------------------------------------------------------
Michael Slusarz <slusarz at mail.curecanti.org> (2005-11-07 17:45) wrote:
So this is happening because cyrus must have a private or public namespace
defined that is empty (i.e. ''). Fixing this by always using the default
namespace won't work because then it is impossible to create folders in an
empty namespace.
A workaround would be to go back to the old way of displaying folders (i.e.
if the default namespace is INBOX, display all folders under INBOX). But as
discussed previously, this is bad because 1) it *is* more confusing to users
(see Bug 2422 for discussion) 2) if create is selected without clicking a
folder, the folder is created in the blank namespace *not* the personal
namespace (which is almost certainly what the user and/or admin wants) and
3) this will require the user to *always* insert the personal namespace
information ('INBOX.foo' for example) when renaming, which most certainly is
not what we should be asking users to do.
Quite honestly, this appears to be an issue with the web interface vs. a
OS-specific GUI interface. On an OS-specific GUI interface, all sorts of
boxes and drop down menus can be provided to explicitly ascertain what the
user wants, or a user can right-click on the mailbox where he wants to add a
folder, etc.. In our (current) web interface, it is difficult to accomplish
this without adding a bunch of javascript or something similar
(bloat/possibly not cross-browser compliant).
One solution - we add an intermediate confirmation page in the instances
where the user's input is unclear - this would only occur on systems where
there is a blank non-personal namespace and only when renaming folders or
creating folders without selecting a folder on the folders page.
Comments/suggestions would be great.
More information about the bugs
mailing list