Dev October 2005

dev@lists.roundcube.net

238 participants
355 discussions

FW: Performance issues
by Dan Metcalf 12 Oct '05

12 Oct '05

> > I have a mailbox w/ 10k emails, on squirrelmail it loads > pretty quick, > > on roundcube its not usable > > > > Any ideas? -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.13/126 - Release Date: 10/09/2005

1 0

Re: Another solution: Courier-IMAP unread mail bug
by Maksim Rubis 12 Oct '05

12 Oct '05

Hello. I displayed fixes very badly, that's why it didn't work for you. I hink you missed changed line with "while" which is very important (key fix :)). I attached my version of imap.inc. Beware that there may be other fixes. :) Maksim >From: Sebastian Wolfgarten <sebastian(a)wolfgarten.com> >Reply-To: sebastian(a)wolfgarten.com >To: dev(a)lists.roundcube.net >Subject: Re: Another solution: Courier-IMAP unread mail bug >Date: Wed, 12 Oct 2005 14:06:31 +0000 > >Hi Maksim, > > > Hello everyone. I fixed this problem after 3 hours of diging the code >:). > >can you send the changed source code files to the list as well? I have >applied >the fixes provided here but none of them did work out so far :-( I will >your >one a try and otherwise I will dig into the code myself tonight... > >All the best & cheers, >Sebastian > > _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

2 3

<kein Betreff>
by Sascha Jafari 12 Oct '05

12 Oct '05

Hi List, Ive two small problems left until my webmail is up and running really smooth. The first one I guess is more complicated than the second one, right know the mails are correctly displayed in the list (with a blue star) but when you click on them, nothing happens and you have the feeling the system crashed (window). Unfortunately there is nothing in the logs. I had a lock in the mail folder, and it is being moved from "new" to "cur" but as I already said, not displayed. When I check my mails via pop3 and my normal client the blue star vanishes and I can read the mail without any problem, only new mails with blue stars are the problem old mails are fine :) The second problem is not an actual problem I couldnt solve, but I like to change the php script itself but dont know exactly how, also after several trials :) Ive the problem that when I upload a file it gets into /tmp/xxxxx but Apache does not have read/write right in that folder, so I want to change the temporary folder from /tmp to something like /var/www/webmail/tmp how can I do that? I already tried in the global config file php.ini but no effect :( Thanks a lot in advance and I hope to enjoy this nice program really soon with all its features :) Take care ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

1 0

Multiple domain drop down
by Praneet Kandula 12 Oct '05

12 Oct '05

if it's an array, it should be ['sitea.com <http://sitea.com>', 'siteb.com<http://siteb.com>', 'sitec.com <http://sitec.com>'] etc. On 10/11/05, Greg Miller <gmiller(a)mainstaydata.com> wrote: > > I have tried everything I can think of to get the drop down box with > multiple domains for selection at login to work. What do I have to do? > I have tried: > 'sitea.com <http://sitea.com> siteb.com <http://siteb.com>' > 'sitea.com <http://sitea.com>, siteb.com <http://siteb.com>' > 'sitea.com <http://sitea.com>' > siteb.com <http://siteb.com>' > > I'm pretty sure it's something stupid that I'm overlooking. Thanks in > advance for the help. > -- > Greg Miller > www.mainstaydata.com <http://www.mainstaydata.com>

4 4

Re: Multiple domain drop down
by Thomas Bruederli 12 Oct '05

12 Oct '05

With the latest version, you can also set an associative array to have a 'nice' label displayed in the hosts pulldown: array('sitea.com' => 'Server A', 'siteb.com' => 'Server B'); or if you have to specify different connections: array('ssl://server.com' => 'Secure Server', 'server.com' => 'Unsecure Server'); Thomas 2005/10/12, justin randell <justin(a)babel.com.au>: > try this: > > $rcmail_config['default_host'] = array('sitea.com', 'siteb.com', > 'sitec.com'); > > or: > > $rcmail_config['default_host'][] = 'sitea.com'; > $rcmail_config['default_host'][] = 'siteb.com'; > $rcmail_config['default_host'][] = 'sitec.com'; > > cheers > justin > > > Greg Miller wrote: > > >That's what I thought. When I put in my domain like that I get the > >following error in firefox: > > > >Parse error: parse error, unexpected '[' > >in /var/www/localhost/htdocs/roundcubemail/config/main.inc.php on line > >33 > > > >Line 33 of main.inc.php: > > > >$rcmail_config['default_host'] = ['sitea.com', 'siteb.com', > >'sitec.com']; > > > >Thanks for the help! > > > >On Wed, 2005-10-12 at 00:09 -0400, Praneet Kandula wrote: > > > > > > > >>if it's an array, it should be ['sitea.com', 'siteb.com', 'sitec.com'] > >>etc. > >> > >> > >> > >> > >>On 10/11/05, Greg Miller <gmiller(a)mainstaydata.com> wrote: > >> > >> I have tried everything I can think of to get the drop down > >> box with multiple domains for selection at login to work. > >> What do I have to do? > >> I have tried: > >> 'sitea.com siteb.com' > >> 'sitea.com, siteb.com' > >> 'sitea.com' > >> siteb.com' > >> > >> I'm pretty sure it's something stupid that I'm overlooking. > >> Thanks in advance for the help. > >> -- > >> Greg Miller > >> www.mainstaydata.com > >> > >> > >> > >> > >> > > > >-- > >Greg Miller > >www.mainstaydata.com > > > > > > > > >

1 0

Postgres problems
by Zac Ariel 12 Oct '05

12 Oct '05

Hi all, I've been having a considerable deal of difficulty making the latest release of Roundcube play nice with PostgreSQL. After fixing up my own stuff ups with permissions (it kinda helps if the database user actually has permission to look at the table you want to select from ;-)), I found that postgres.initial.sql is missing the 'ip' column (from the 'session' table). Doing the below fixed this for me: ALTER TABLE session ADD ip character varying(15) NOT NULL; ALTER TABLE session ALTER COLUMN ip SET DEFAULT ''::character varying; However, it's still not working, and the current problem has got me stumped. I think it's due to the php being used, but my code-foo ain't that good. I receive this in the browser: -----ooooo----- DB Error in /var/www/roundcubemail/program/include/rcube_db.inc (124): DB Error: unknown error DB Error in /var/www/roundcubemail/program/include/rcube_db.inc (210): DB Error: unknown error Query: SELECT vars, ip, UNIX_TIMESTAMP(changed) AS changed FROM session WHERE sess_id='74bfac980c44f3d2db46c4b0c49d22f0' Fatal error: Call to a member function on a non-object in /var/www/roundcubemail/program/include/rcube_db.inc on line 202 -----ooooo----- .and in the Postgres log I get this: -----ooooo----- 2005-10-12 16:49:16 [15138] ERROR: function unix_timestamp(timestamp with time zone) does not exist HINT: No function matches the given name and argument types. You may need to add explicit type casts. -----ooooo----- Um ... any ideas? Google hasn't been especially useful, save referring to PHP information that I don't pretend to understand. What other information can I provide that would be useful? Many thanks. ~ z.

2 1

SF Bug # 1323578 - Adding multiple Re: to subject
by Ross Poulton 12 Oct '05

12 Oct '05

I've corrected this bug and am copying the fix here as with the current changes I'm not sure where things should be submitted, so sorry for the duplication. Can somebody please confirm my fix (It's working for me, but as always YMMV) and close the bug if you find it appropriate? In file program/steps/mail/compose.inc, replace lines 404-410, which are currently: // create a reply-subject else if (isset($REPLY_MESSAGE['subject'])) $subject = 'Re: '.$REPLY_MESSAGE['subject']; // create a forward-subject else if (isset($FORWARD_MESSAGE['subject'])) $subject = 'Fwd: '.$FORWARD_MESSAGE['subject']; with the following: // create a reply-subject else if (isset($REPLY_MESSAGE['subject'])) { if (eregi("^Re: ", $REPLY_MESSAGE['subject'])) { $subject = $REPLY_MESSAGE['subject']; } else { $subject = 'Re: '.$REPLY_MESSAGE['subject']; } } // create a forward-subject else if (isset($FORWARD_MESSAGE['subject'])) { if (eregi("^Fwd: ", $FORWARD_MESSAGE['subject'])) { $subject = $FORWARD_MESSAGE['subject']; } else { $subject = 'Fwd: '.$FORWARD_MESSAGE['subject']; } } This will only put a 'Re:' (or 'Fwd:' if it's a foward) if one doesn't already exist. It's case-insensitive, so if there is a RE:/Re:/re: at the start of the subject it won't add another one. It also checks for the colon character (':') so that if the subject is 'Rewards Program' the Re: will still be created. Also can somebody clarify the correct procedure here - when fixing bugs from SF should I post the response on SF, here, or both? Best Regards, Ross Poulton

1 0

Multiple domain drop down
by Greg Miller 11 Oct '05

11 Oct '05

I have tried everything I can think of to get the drop down box with multiple domains for selection at login to work. What do I have to do? I have tried: 'sitea.com siteb.com' 'sitea.com, siteb.com' 'sitea.com' siteb.com' I'm pretty sure it's something stupid that I'm overlooking. Thanks in advance for the help. -- Greg Miller www.mainstaydata.com

1 0

Progress report on Trac and a few questions...
by B. Johannessen 11 Oct '05

11 Oct '05

Time for a progress report on the Trac installation. After many, *many* hours, I've finally reached an agreement with Python. The agreement basically boils down to this; Python will put up with being installed in /usr/local/python (instead of in /usr or /usr/local), and I will put up with having to hack every Python "extension" in the known universe to get it to work. In practice this means everything will take about 10 times as long, at least in the beginning. The only reason I haven't taken both Trac and Python out back and shot then both in the neck, is that certain people whose opinion i respect claims Python is actually an excellent idea. But, at the end of the day (or more precisely at the end of two days), I've succeeded. Trac and Python, and their combined cluster of dependencies finally fell into place. We now have a working Trac installation! This means it's time for me to start asking some questions. The ticket tracking system has a few settings we need to agree upon before we start using it. I'll present the issues in question, along with my suggested answers, and let you all battle it out for a few days before we make a final decision. I'll give Thomas final say, and assume he speaks on behalf of the current active developers. * Type: When you create a ticket, you also select a ticket type. The default list of available types include the following: 'defect', 'enhancement' and 'task'. My suggestion is that we substitute these 3 with the following 2: 'Bug' and 'Feature Request'. My motivation for both reducing and renaming is simplicity. When a first-time Trac user submits her first ticket, lets make sure it's as simple and self explanatory as can be. * Priority: A ticket is assigned a priority. The default Trac installation is set up with a total of 5 priorities; 'blocker', 'critical', 'major', 'minor' and 'trivial'. I suggest we reduce and rename to: 'High', 'Medium' and 'Low', for the reasons listed above. * Component: As far as I can tell, the RoundCube project only has one component so far. I suggest we name this 'RoundCube Core'. * Milestone: At what milestone is this bug fix or feature supposed to be available. To keep things simple in the beginning I suggest we define the following milestones: '0.1-beta', '0.1-final', '0.2-alpha' and '0.2-beta'. More milestones will of course be added later. If we agree to start with this list, I'll need a guesstimate from Thomas on when they'll be released. * Version: The version of RoundCube that this ticket pertains to. I see no point in adding any older versions to the system, so I think this list should initially include only 'v0.1-20051007'. The important thing to remember about the above lists is that non of this will be carved in stone. We'll surely make additions and alterations as we go. The goal here is just to make sure we start with some sane defaults. Then there's the question of the design. The current design looks fantastic, but doesn't lend itself easily to some of the thinks we'll be publishing. My suggestion is to just go live with the default design of Trac, a slightly modified design on the mailing list archive, and the main RoundCube site just like it looks today. Then, once everything is up and running I'll ask for some design help on the mailing list. Last, but not least; the question of CVS to SVN migration. It's a lot easier for me just to fetch the latest source from SourceForge CVS and import this into Subversion. If we want to import all the history as well, someone with a bit more CVS-foo then me will have to help me get my hands on a repository tar-ball. This is once again a decision for the developers. Is it acceptable to leave all the old history in SourceForge CVS? At the end of the day, I'll leave this decision to Thomas. I think that's about it for tonight. Bob

3 2

Re: Progress report on Trac and a few questions...
by Praneet Kandula 11 Oct '05

11 Oct '05

Awesome work, Bob! I agree with all of your Trac settings except one. I suggest that you have more than one setting for the components, that would initially include: - Webmail - Address Book - Skins - Other (settings, etc.) We can expand to include more as we need (plugins, notes, etc.). What do you think? On 10/11/05, B. Johannessen <bob(a)db.org> wrote: > Time for a progress report on the Trac installation. After many, *many* > hours, I've finally reached an agreement with Python. The agreement > basically boils down to this; Python will put up with being installed in > /usr/local/python (instead of in /usr or /usr/local), and I will put up > with having to hack every Python "extension" in the known universe to > get it to work. In practice this means everything will take about 10 > times as long, at least in the beginning. The only reason I haven't > taken both Trac and Python out back and shot then both in the neck, is > that certain people whose opinion i respect claims Python is actually an > excellent idea. > > But, at the end of the day (or more precisely at the end of two days), > I've succeeded. Trac and Python, and their combined cluster of > dependencies finally fell into place. We now have a working Trac > installation! > > This means it's time for me to start asking some questions. The ticket > tracking system has a few settings we need to agree upon before we start > using it. I'll present the issues in question, along with my suggested > answers, and let you all battle it out for a few days before we make a > final decision. I'll give Thomas final say, and assume he speaks on > behalf of the current active developers. > > * Type: > When you create a ticket, you also select a ticket type. The default > list of available types include the following: 'defect', 'enhancement' > and 'task'. My suggestion is that we substitute these 3 with the > following 2: 'Bug' and 'Feature Request'. My motivation for both > reducing and renaming is simplicity. When a first-time Trac user submits > her first ticket, lets make sure it's as simple and self explanatory as > can be. > > * Priority: > A ticket is assigned a priority. The default Trac installation is set up > with a total of 5 priorities; 'blocker', 'critical', 'major', 'minor' > and 'trivial'. I suggest we reduce and rename to: 'High', 'Medium' and > 'Low', for the reasons listed above. > > * Component: > As far as I can tell, the RoundCube project only has one component so > far. I suggest we name this 'RoundCube Core'. > > * Milestone: > At what milestone is this bug fix or feature supposed to be available. > To keep things simple in the beginning I suggest we define the following > milestones: '0.1-beta', '0.1-final', '0.2-alpha' and '0.2-beta'. More > milestones will of course be added later. If we agree to start with this > list, I'll need a guesstimate from Thomas on when they'll be released. > > * Version: > The version of RoundCube that this ticket pertains to. I see no point in > adding any older versions to the system, so I think this list should > initially include only 'v0.1-20051007'. > > The important thing to remember about the above lists is that non of > this will be carved in stone. We'll surely make additions and > alterations as we go. The goal here is just to make sure we start with > some sane defaults. > > Then there's the question of the design. The current design looks > fantastic, but doesn't lend itself easily to some of the thinks we'll be > publishing. My suggestion is to just go live with the default design of > Trac, a slightly modified design on the mailing list archive, and the > main RoundCube site just like it looks today. Then, once everything is > up and running I'll ask for some design help on the mailing list. > > Last, but not least; the question of CVS to SVN migration. It's a lot > easier for me just to fetch the latest source from SourceForge CVS and > import this into Subversion. If we want to import all the history as > well, someone with a bit more CVS-foo then me will have to help me get > my hands on a repository tar-ball. This is once again a decision for the > developers. Is it acceptable to leave all the old history in SourceForge > CVS? At the end of the day, I'll leave this decision to Thomas. > > I think that's about it for tonight. > > > Bob > > >

2 1

← Newer
1
...
27
28
29
30
31
32
33
...
36
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Dev October 2005