On 04/20/2012 14:46, Michael Heydekamp wrote:
When I started RC 0.7.2 for the first few times, I saw the columns "From" and "To" in each of the folders. I found that pretty cool (as I'm using multiple identities) and did miss this a lot in Squirrel.
Then I made a "mistake": Just for testing purposes, I activated the Threads view mode by using the List Options drop-down button. But after I switched back to the List mode, all of a sudden one of the columns was gone (depending on the folder): INBOX just shows the "From" column, Sent folder just the "To" column", and so on.
I'm wondering how I can return to the "virgin" state (= having both "From" and "To" columns in all folders) and how to keep this state persistent, even after a forth-and-back change of the view mode.
I'm not 100% certain, as we don't show both columns by default. I see that both 'from' and 'to' are available choices, but I don't see any way to view them both at the same time. It's been a very long time since I started with RC, long before many of these options were available.
So I have a second instance of RC (connecting to the same database) that is an exact mirror of the production system, except that multiple identities are allowed.
Ah, interesting! How exactly did you do that? If you feel that this is not an issue for the list, I'm happy to receive an e-mail off-list.
Apache aliases all pointing to different folders. I actually have multiple instances running concurrently on the same web server, currently 4 instances of RC and one legacy squirrelmail instance. The two 0.7.2 RC instances are pointed at the same database, while the svn and 0.6 instances each have their own database.
# Production aliases Alias /webmail /hpsw/web/configs/roundcubemail-0.7.2 Alias /basic /hpsw/web/configs/squirrelmail-1.4.22
# Testing, special and rollback aliases Alias /devel /hpsw/web/configs/roundcubemail-svn Alias /previous /hpsw/web/configs/roundcubemail-0.6 Alias /identities /hpsw/web/configs/identities-0.7.2
Part of this comes from how I do release upgrades. I never upgrade an existing instance. I always load it totally fresh and connect to a *copy* of the previous version's database. That way roll-backs are easy
- just change the alias in Apache and restart the service.