At 10/26/04 10:06 PM, Robert Kehl <[EMAIL PROTECTED]> wrote:
>Robert L Mathews schrieb:
>> (The same goes for bug 518: OTRS is almost unusable with PostgreSQL as
>> the backend with a large number of tickets, so I submitted a patch that
>> fixes the schema to speed up OTRS dramatically and make
Robert L Mathews schrieb:
(The same goes for bug 518: OTRS is almost unusable with PostgreSQL as
the backend with a large number of tickets, so I submitted a patch that
fixes the schema to speed up OTRS dramatically and make OTRS work
properly. But the patch appears to be languishing and is in d
At 10/9/04 3:00 AM, Robert Kehl <[EMAIL PROTECTED]> wrote:
>Robert L Mathews schrieb:
>> It looks like only some of the patch got applied, so it didn't solve all
>> the line wrapping issues. :-(
>> I added a full description of the issue to the bug report (explaining why
>> the other part of th
Robert L Mathews schrieb:
It looks like only some of the patch got applied, so it didn't solve all
the line wrapping issues. :-(
I added a full description of the issue to the bug report (explaining why
the other part of the patch is necessary) and reopened it; hope that's
okay... Sorry to be s
At 9/27/04 4:15 PM, Martin Edenhofer <[EMAIL PROTECTED]> wrote:
>Now it's in cvs for OTRS 2.0.
It looks like only some of the patch got applied, so it didn't solve all
the line wrapping issues. :-(
I added a full description of the issue to the bug report (explaining why
the other part of the
On 23-09-2004 at 8:54, Wes Plate wrote:
>Dang. I too was hoping the next upgrade was going to fix this.
You can manually apply Robert's patch:
http://bugs.otrs.org/show_bug.cgi?id=526
Just type this:
curl 'http://bugs.otrs.org/showattachment.cgi?attach_id=56' | \
patch -p0 -d /opt/otrs
So...
On 9/23/04 3:43 AM, "Frederik Seiffert" wrote:
> I just looked into CVS and it seems like the fix didn't make it into
> 1.3.1. Any predictions about when it will be included? We'd rather like
> to have an official release instead of a patched version.
Dang. I too was hoping the next upgrade was
Wes Plate wrote:
On 9/10/04 12:24 AM, "Robert L Mathews" wrote:
Sorry for the delay in submitting it; perhaps it's trivial enough (and
fixes a large enough bug) that it can make it into OTRS 1.3.
Please! :-)
I just looked into CVS and it seems like the fix didn't make it into
1.3.1. Any predic
On 9/10/04 12:24 AM, "Robert L Mathews" wrote:
> Sorry for the delay in submitting it; perhaps it's trivial enough (and
> fixes a large enough bug) that it can make it into OTRS 1.3.
Please! :-)
--
Wes Plate
Automatic Duck, Inc.
http://www.wesplate.com
http://www.automaticduck.com
At 8/31/04 8:26 AM, Wes Plate <[EMAIL PROTECTED]> wrote:
>On 8/31/04 5:59 AM, "Frederik Seiffert" wrote:
>
>> Yes, that was me. Unfortunately, while the incoming message looks just
>> fine, the reply sent with OTRS still looks awful. Have a look at the
>> first and third external agent email.
>
>A
Robert L Mathews wrote:
Is there any reason against wrap=soft in the input field? As I see it,
this would fix the problem.
Hmmm. I was the one who suggested the new line wrap algorithm (it was
discussed on dev list), but I think I must not have made that part clear:
the algorithm can only work w
At 8/31/04 8:26 AM, Frederik Seiffert <[EMAIL PROTECTED]> wrote:
>Yes, that was me. Unfortunately, while the incoming message looks just
>fine, the reply sent with OTRS still looks awful. Have a look at the
>first and third external agent email.
>
>Is there any reason against wrap=soft in the in
On 8/31/04 7:51 AM, "Martin Edenhofer" wrote:
> How can I reproduce this like in the first third external agent email?
I replied to this ticket with a long bit of text...
http://demo.otrs.org/otrs/index.pl?TicketID=60234&QueueID=0&Action=AgentZoom
&ArticleID=148597#148597
And the wrapping of my
I just tried with Mozilla Firefox 0.9.3 on Mac OS X and couldn't
reproduce the problem there either.
But I think I might have lead: Firefox uses a fixed-width font in the
input field and displays 78 characters per line. Safari uses a
variable-width font and displays more than 100 characters per
scussions about OTRS.
> Subject: Re: [otrs] Line wrap problems
>
> On Tue, Aug 31, 2004 at 02:59:02PM +0200, Frederik Seiffert wrote:
> > Yes, that was me. Unfortunately, while the incoming message looks just
> > fine, the reply sent with OTRS still looks awful. Have a look at th
On Tue, Aug 31, 2004 at 02:59:02PM +0200, Frederik Seiffert wrote:
> Yes, that was me. Unfortunately, while the incoming message looks just
> fine, the reply sent with OTRS still looks awful. Have a look at the
> first and third external agent email.
How can I reproduce this like in the first th
On 8/31/04 5:59 AM, "Frederik Seiffert" wrote:
> Yes, that was me. Unfortunately, while the incoming message looks just
> fine, the reply sent with OTRS still looks awful. Have a look at the
> first and third external agent email.
Ah, right. Yeah, it isn't fixed yet.
Thanks for bringing up this
On 8/31/04 5:59 AM, "Frederik Seiffert" wrote:
> Yes, that was me. Unfortunately, while the incoming message looks just
> fine, the reply sent with OTRS still looks awful. Have a look at the
> first and third external agent email.
--
Wes Plate
Automatic Duck, Inc.
http://www.wesplate.com
Yes, that was me. Unfortunately, while the incoming message looks just
fine, the reply sent with OTRS still looks awful. Have a look at the
first and third external agent email.
Is there any reason against wrap=soft in the input field? As I see it,
this would fix the problem.
Thanks,
Frederik
On 8/30/04 8:40 PM, "Martin Edenhofer" wrote:
> We reworked the line wrap problem in OTRS 1.3.
>
> Can you test in on http://demo.otrs.org/? Is it now better?
Looks like someone tested some long lines in ticket number 200408311133
and it does appear better when replying.
--
Wes Plate
Auto
Hi Wes, Hi Frederik,
On Sat, Aug 28, 2004 at 01:58:12PM -0700, Wes Plate wrote:
> On 8/28/04 7:51 AM, "Frederik Seiffert" wrote:
>
> > We're using OTRS 1.2 and noticed that the emails always look pretty ugly
> > as the lines are not correctly wrapped. For example, the following
> > should be one
On 8/28/04 7:51 AM, "Frederik Seiffert" wrote:
> We're using OTRS 1.2 and noticed that the emails always look pretty ugly
> as the lines are not correctly wrapped. For example, the following
> should be one single paragraph. However, the email would look something
> like this:
I hope you get a go
Hi!
We're using OTRS 1.2 and noticed that the emails always look pretty ugly
as the lines are not correctly wrapped. For example, the following
should be one single paragraph. However, the email would look something
like this:
Text text text text text text. Text text text text text text text te
23 matches
Mail list logo
