Hi there,
as I already said in an earlier mail, we're in the process of moving from Squirrel to RC, for a number of good reasons (the more attractive UI of RC being the least important one).
There are still some issues, though, some of them currently being show stoppers. I'm gonna post them here one by one during the next days and weeks.
One of the show stoppers is the address book, which doesn't seem to work (almost) at all. Well, you can enter and edit contacts, BUT:
- Selecting a contact in the contact list and clicking the "Compose mail
to" button creates an entry in the To: field that looks like this: "real name <>" (without the quotes, of course) So the address gets lost completely, and the upper case characters of the real name are converted to lower case.
- Clicking the "Show Address Book" button in the compose window and
selecting one or more entries in the overlay window will lead to the same result as in 1), except that upper case characters of real names are not converted to lower case. But the addresses get lost as well. Furthermore, the sort order in the overlay window is different to the sort order in the address book itself: In the address book the entries are sorted by last name, the overlay window sorts them by first name (which I prefer).
- The only thing that works flawlessly is typing the first characters of a
contact name in one of the address fields of the compose window, and then selecting one of the proposed entries.
As nobody else seems to have reported these issues in the list yet, I'm wondering if and what we might be doing wrong. 7.5.2 is meant to be a stable version, and I can't imagine that it has an address book implementation which is almost unusable.
- Not a show stopper, but also not very convenient: If you limit the "Rows
per page" in the Personal Settings to say 20 (because you are using the preview pane in the main window and don't want to display more mails than will fit into the space above the preview pane), then the address book does also show only 20 entries per page, although there is of course no preview pane. Is this deliberate? Can I apply a small patch that avoids this behaviour? (I'm a former Turbo Pascal programmer, but my PHP skills are pretty poor.)
If more specific information about our server environment is needed, please let me know.
Any help appreciated and TIA.
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
On 04/09/2012 10:16, Michael Heydekamp wrote:
Hi there,
as
I already said in an earlier mail, we're in the process of moving from
Squirrel to RC, for a number of good reasons (the more attractive UI of RC
being the least important one).
There are still some issues,
though, some of them currently being show
stoppers. I'm gonna post
them here one by one during the next days and
weeks.
One of the
show stoppers is the address book, which doesn't seem to work
(almost)
at all. Well, you can enter and edit contacts, BUT:
- Selecting a
contact in the contact list and clicking the "Compose mail
to" button
creates an entry in the To: field that looks like this: "real
name <>"
(without the quotes, of course) So the address gets lost
completely,
and the upper case characters of the real name are converted to
lower
case.
- Clicking the "Show Address Book" button in the compose
window and
selecting one or more entries in the overlay window will
lead to the same
result as in 1), except that upper case characters of
real names are not
converted to lower case. But the addresses get lost
as well. Furthermore,
the sort order in the overlay window is
different to the sort order in the
address book itself: In the address
book the entries are sorted by last
name, the overlay window sorts
them by first name (which I prefer).
- The only thing that works
flawlessly is typing the first characters of a
contact name in one of
the address fields of the compose window, and then
selecting one of
the proposed entries.
As nobody else seems to have reported these
issues in the list yet, I'm
wondering if and what we might be doing
wrong. 7.5.2 is meant to be a stable
version, and I can't imagine that
it has an address book implementation
which is almost unusable.
- Not a show stopper, but also not very convenient: If you limit the
"Rows
per page" in the Personal Settings to say 20 (because you are
using the
preview pane in the main window and don't want to display
more mails than
will fit into the space above the preview pane), then
the address book does
also show only 20 entries per page, although
there is of course no preview
pane. Is this deliberate? Can I apply a
small patch that avoids this
behaviour? (I'm a former Turbo Pascal
programmer, but my PHP skills are
pretty poor.)
If more specific
information about our server environment is needed, please
let me
know.
Any help appreciated and TIA.
Michael,
Regarding number 1, I can not duplicate your issue on either my production (0.7.2) system, nor on my development (0.8-beta). Selecting one or more addresses and clicking the Compose-to button works perfectly every time for me.
For number 2, can I assume that you are using the compose_addressbook plugin for that? If so, we also use that plugin, and it also works properly for us in 0.7.2. (That plugin will not be necessary in 0.8, the contact list is visible in the compose window by default.)
What address books are you using when you see these problems - the default SQL or an LDAP book?
Arne,
thanks for speedy response. Although your mail didn't make it to the list yet, I'm answering to the copy you sent.
And sorry, I totally confused the RC version number, no idea why. It's 0.7.2, of course (subject line is corrected).
Answers below:
Am 09.04.2012 19:33, schrieb Arne Berglund:
- Selecting a contact in the contact list and clicking the "Compose mail
to" button creates an entry in the To: field that looks like this: "real name <>" (without the quotes, of course) So the address gets lost completely, and the upper case characters of the real name are converted to lower case.
- Clicking the "Show Address Book" button in the compose window and
selecting one or more entries in the overlay window will lead to the same result as in 1), except that upper case characters of real names are not converted to lower case. But the addresses get lost as well. Furthermore, the sort order in the overlay window is different to the sort order in the address book itself: In the address book the entries are sorted by last name, the overlay window sorts them by first name (which I prefer).
Regarding number 1, I can not duplicate your issue on either my production (0.7.2) system, nor on my development (0.8-beta).
That's what I expected. Otherwise this list should have received many more complaints already.
For number 2, can I assume that you are using the compose_addressbook plugin for that?
Right.
If so, we also use that plugin, and it also works properly for us in 0.7.2.
Damn. ;-)
What address books are you using when you see these problems - the default SQL or an LDAP book?
The SQL one.
Any idea where we could look at?
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
General question, as we are pretty new to the RC mailing lists: If there is no helpful response in the users list to a message such as the one quoted below, does it make sense to post the same message to the dev list - after some time of waiting to no avail?
I can see that lots of users have sent messages to the dev list in the past, so it's not really clear to me, what's the best and "correct" place to post (or which issues should be posted to which list).
If we can't find a solution for the (SQL) address book issues below (and some more show stoppers which I didn't mention yet), then we won't be able to finally kick Squirrel and make RC our default webmailer. Which would be quite unfortunate as we really and finally would like to get rid of Squirrel.
(Please note that I have corrected the RC version number in the subject line as well as in the quote below - dunno why I totally confused it in my initial post.)
Regards,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
Am 09.04.2012 19:16, schrieb Michael Heydekamp:
Hi there,
as I already said in an earlier mail, we're in the process of moving from Squirrel to RC, for a number of good reasons (the more attractive UI of RC being the least important one).
There are still some issues, though, some of them currently being show stoppers. I'm gonna post them here one by one during the next days and weeks.
One of the show stoppers is the address book, which doesn't seem to work (almost) at all. Well, you can enter and edit contacts, BUT:
- Selecting a contact in the contact list and clicking the "Compose mail
to" button creates an entry in the To: field that looks like this: "real name <>" (without the quotes, of course) So the address gets lost completely, and the upper case characters of the real name are converted to lower case.
- Clicking the "Show Address Book" button in the compose window and
selecting one or more entries in the overlay window will lead to the same result as in 1), except that upper case characters of real names are not converted to lower case. But the addresses get lost as well. Furthermore, the sort order in the overlay window is different to the sort order in the address book itself: In the address book the entries are sorted by last name, the overlay window sorts them by first name (which I prefer).
- The only thing that works flawlessly is typing the first characters of a
contact name in one of the address fields of the compose window, and then selecting one of the proposed entries.
As nobody else seems to have reported these issues in the list yet, I'm wondering if and what we might be doing wrong. 0.7.2 is meant to be a stable version, and I can't imagine that it has an address book implementation which is almost unusable.
- Not a show stopper, but also not very convenient: If you limit the "Rows
per page" in the Personal Settings to say 20 (because you are using the preview pane in the main window and don't want to display more mails than will fit into the space above the preview pane), then the address book does also show only 20 entries per page, although there is of course no preview pane. Is this deliberate? Can I apply a small patch that avoids this behaviour? (I'm a former Turbo Pascal programmer, but my PHP skills are pretty poor.)
If more specific information about our server environment is needed, please let me know.
Any help appreciated and TIA.
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
On 04/10/2012 15:23, Cor Bosman wrote:
If so, we also use that plugin, and it also works properly for us in 0.7.2.
Damn. ;-)
Are you using the correct version of the compose_addressbook plugin? You need 5.0b3. I dont know of any problems with the SQL addressbook with 0.7.2
OK, so your address book is totally SQL, no LDAP. That's a pretty simple setup. I've got a couple of questions about it.
1.) Is there a global SQL address book for all users, or are these all individual users' personal address books?
2.) How were the SQL address books(s) populated? Where did the data come from?
-- Arne Berglund System Administrator, Internet Services Lane Education Service District Eugene, OR ____________
On 11.04.2012 00:07, Michael Heydekamp wrote:
General question, as we are pretty new to the RC mailing lists: If there is no helpful response in the users list to a message such as the one quoted below, does it make sense to post the same message to the dev list - after some time of waiting to no avail?
I think most developers also read users list so there's no need to post the same topic to both lists.
About your issues: 1-3 are probably because of a broken plugin, 4. is fixed in svn-trunk version (by two separate config options).
Am 11.04.2012 00:23, schrieb Cor Bosman:
If so, we also use that plugin, and it also works properly for us in 0.7.2.
Damn. ;-)
Are you using the correct version of the compose_addressbook plugin? You need 5.0b3.
Uh, good question! I had to x-check with my main admin and he is believing that he may simply have copied the compose_addressbook plugin from our Debian distribution (Squeeze) to the RC 0.7.2 installation. Debian Squeeze is bringing RC 0.5.4 and compose_addressbook 4.0 with it, but due to the vast improvements we decided to a parallel install of the latest stable RC version 0.7.2.
If his memory serves him well (he didn't find the time to verify it yet), then he may have combined compose_addressbook 4.0 with RC 0.7.2. Well, this may indeed explain the problems.
We will make sure to install compose_addressbook 5.0b3 and I will post here if the problems are gone or not. If they are gone, sorry for bothering. I wasn't aware of this (probable and problematic) combination.
I dont know of any problems with the SQL addressbook with 0.7.2
Good to hear and fingers crossed...
Thanks for your response, Cor.
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
Am 11.04.2012 00:36, schrieb Arne Berglund:
On 04/10/2012 15:23, Cor Bosman wrote:
If so, we also use that plugin, and it also works properly for us in 0.7.2.
Damn. ;-)
Are you using the correct version of the compose_addressbook plugin? You need 5.0b3. I dont know of any problems with the SQL addressbook with 0.7.2
See my response to Cor's message. We may have combined incompatible versions (compose_addressbook 4.0 with RC 0.7.2).
We'll see how it will work with compose_addressbook 0.5b3.
Nonetheless the answers to your questions:
OK, so your address book is totally SQL, no LDAP. That's a pretty simple setup. I've got a couple of questions about it.
1.) Is there a global SQL address book for all users, or are these all individual users' personal address books?
Both - one global and many personal ones.
2.) How were the SQL address books(s) populated? Where did the data come from?
Manually entered through the RC interface.
But let's put this issue on hold until we had the chance to install compose_addressbook 5.0b3 and run the tests again.
It was my impression from the beginning that the problem is more at our end...
Thanks,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
On 04/11/2012 12:46, Michael Heydekamp wrote:
Am 11.04.2012 00:36, schrieb Arne Berglund:
On 04/10/2012 15:23, Cor Bosman wrote:
See my response to Cor's message. We may have combined incompatible versions (compose_addressbook 4.0 with RC 0.7.2).
We'll see how it will work with compose_addressbook 0.5b3.
Nonetheless the answers to your questions:
OK, so your address book is totally SQL, no LDAP. That's a pretty simple setup. I've got a couple of questions about it.
1.) Is there a global SQL address book for all users, or are these all individual users' personal address books?
Both - one global and many personal ones.
2.) How were the SQL address books(s) populated? Where did the data come from?
Manually entered through the RC interface.
But let's put this issue on hold until we had the chance to install compose_addressbook 5.0b3 and run the tests again.
It was my impression from the beginning that the problem is more at our end...
Thanks,
Keep us posted, Michael. I think we can get this worked out.
FWIW, my organization migrated from squirrelmail to RC back at v. 0.3 or so. Feel free to contact me if I can be of any assistance.
Am 11.04.2012 21:51, schrieb Arne Berglund:
Keep us posted, Michael. I think we can get this worked out.
FWIW, my organization migrated from squirrelmail to RC back at v. 0.3 or so. Feel free to contact me if I can be of any assistance.
Don't be too surprised if I take your word for it some day. :-)
Just great to see how responsive, friendly and helpful the folks in this list are. Chapeau! (Another good reason to move to RC finally.)
Am 11.04.2012 08:20, schrieb A.L.E.C:
On 11.04.2012 00:07, Michael Heydekamp wrote:
General question, as we are pretty new to the RC mailing lists: If there is no helpful response in the users list to a message such as the one quoted below, does it make sense to post the same message to the dev list - after some time of waiting to no avail?
I think most developers also read users list so there's no need to post the same topic to both lists.
Understood. Should I hit a brick wall here some day, I may give it a try it in the dev list, though (with regards to the terms "think" and "most" in your response ;-)).
About your issues: 1-3 are probably because of a broken plugin,
That may very well be (see my previous posts). Well, not because the plugin is broken, but because we probably combined and older plugin with a newer RC version. I'm pretty sure that this particular problem is at our end.
As a general question: A broken or incompatible plugin can also break core functions, right? I'm asking as issue 1) indeed IS a core (and not a plugin) function and would like to understand the two-way influence of plugin and core code. Not in detail, just in general.
- is fixed in svn-trunk version (by two separate config options).
Ah! I did not have the chance to dig too deep into the svn list yet, can you point me to the checkin/diff post?
Thanks for response,
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
On 11.04.2012 23:16, Michael Heydekamp wrote:
As a general question: A broken or incompatible plugin can also break core functions, right? I'm asking as issue 1) indeed IS a core (and not a plugin) function and would like to understand the two-way influence of plugin and core code. Not in detail, just in general.
Yes.
- is fixed in svn-trunk version (by two separate config options).
Ah! I did not have the chance to dig too deep into the svn list yet, can you point me to the checkin/diff post?
r5662, but there were some additional commmits. The best is to use svn-trunk version which will be released as 0.8-rc in a few days.
Am 11.04.2012 21:51, schrieb Arne Berglund:
On 04/11/2012 12:46, Michael Heydekamp wrote:
Am 11.04.2012 00:36, schrieb Arne Berglund:
On 04/10/2012 15:23, Cor Bosman wrote:
See my response to Cor's message. We may have combined incompatible versions (compose_addressbook 4.0 with RC 0.7.2).
We'll see how it will work with compose_addressbook 0.5b3.
[...]
It was my impression from the beginning that the problem is more at our end...
Keep us posted, Michael. I think we can get this worked out.
Ok, here is an update:
Afer installation of compose_addressbook 5.0b3, item 2) of my initial post in this thread is solved.
The only issue with this plugin still is: It does not honor the "Sorting column" setting under Settings/Address Book - it is always sorting by first name, no matter what.
But that's a minor issue I can live with for the moment. Should be solved some day, though.
OTOH, what is pretty convenient with this plugin: That it DOES honor the fact whether a contact has more than just one mail address (then the entry gets listed as many times as mail addresses do exist for a specific contact).
With regards to item 1) of my initial post, this is solved as well, after we had updated the compose_newwindow plugin from 2.05 to 3.0. Now neither the mail address does get lost nor are upper case chars of the real name converted to lower chars anymore.
Nonetheless there are still two issues with this core function:
- If a contact has more than just one mail address, clicking the "Compose
mail to" button does not allow me to choose between these several addresses. In my case, it takes the "Work" one ("Other" being the, well, other one of two in total).
- To avoid 1), I can click on one of the address links in the "Properties"
tab, but then the real name does not get transferred to the To: field in the compose window (just the address itself).
This is also the case if I disable the setting "compose in new window". It totally escapes me BTW, why I should NOT want to compose a new mail in a new window, as I would otherwise have no access to my entire message base during composing, so this should really become a core function at some stage.
Anyway, comments and help still welcome and appreciated.
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany
-
A.L.E.C -
Arne Berglund -
Cor Bosman -
Michael Heydekamp