Re: [otrs] Upgrading from 3.1.21 to 3.3.10

[Jan.Dreyer]

Hello.

>Hi,
>
>>> We wanted to upgrade our 3.1.21 to 3.3.10.
>>> Any intermediate upgrades required first?
>> 
>> Yes, you have to upgrade to 3.2.latest first (where latest is 16 at the
>> moment).
>
>It is actually suffucient to apply the database upgrades in order.
>
>I upgrade from an old largely unmaintained Debian wheezy package to
>Debain jessie recently. I upgraded the package using apt, then grabbed
>the upgrade *.sql from the 3.2 package, applied that, and then applied
>the upgrade SQL from 3.3.
>
>You do not need to double-upgrade the whole installation.

I¹m quite sure this is not correct. Probably it¹s not necessary to update
all the files. But beside the SQL there are other pre- and post-DB scripts
you should run. They are responsible for doing conversions (like the one
from FreeText to DynamicFields with upgrade 3.0->3.1), as well as other
important tasks (installing scheduler, Š). In short: to be sure, just do
the complete upgrade path.

Jan Dreyer
IT Administrator ‹ Operations ‹ A-SCM-IT NMD Expert

-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Re: [otrs] Upgrading from 3.1.21 to 3.3.10

[Frank Thommen]

On 24.11.14 14:03, jan.dre...@bertelsmann.de wrote:

Hello.


Hi,


We wanted to upgrade our 3.1.21 to 3.3.10.
Any intermediate upgrades required first?


Yes, you have to upgrade to 3.2.latest first (where latest is 16 at the
moment).


It is actually suffucient to apply the database upgrades in order.

I upgrade from an old largely unmaintained Debian wheezy package to
Debain jessie recently. I upgraded the package using apt, then grabbed
the upgrade *.sql from the 3.2 package, applied that, and then applied
the upgrade SQL from 3.3.

You do not need to double-upgrade the whole installation.


I¹m quite sure this is not correct. Probably it¹s not necessary to update
all the files. But beside the SQL there are other pre- and post-DB scripts
you should run. They are responsible for doing conversions (like the one
from FreeText to DynamicFields with upgrade 3.0->3.1), as well as other
important tasks (installing scheduler, Š). In short: to be sure, just do
the complete upgrade path.


AFAIK this process /is/ correct.  E.g. a "clean migration" to an other 
system would consist of


  * Do a clean install of the newest OTRS version
  * Transfer your settings files
  * Replace DB of fresh installation by the one from the old install
  * Run through all (!) required DB upgrade steps (3.1->3.2->3.3-> etc.)

This also makes sure you don't drag along lots of outdated files with 
your installation.


If that works, the update procedure described by Dominik George should 
work, too. The crucial point is that no matter how big the (file) 
upgrade step is, the database upgrade procedure /always/ has to be 
followed to the point.  AFAIK there are no pre- or post-DB scripts to 
consider.  Everything is done by the main database upgrade script.  E.g. 
in the OTRS 3.1 manual it says "A database update script will transform 
historic FreeText fields and related configuration settings into the new 
structure".


HTH
Frank

--
Frank Thommen - Structures IT Management and Support - EMBL Heidelberg
frank.thom...@embl-heidelberg.de - +49 6221 387 8353
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Re: [otrs] Upgrading from 3.1.21 to 3.3.10

[Martin Gruner]

I agree. And the DBUpdate-to-x.pl scripts, that are definitely needed,
should always run on their corresponding code base.

Best regards, Martin

Am 24.11.14 um 14:03 schrieb jan.dre...@bertelsmann.de:
> Hello.
> 
>> Hi,
>>
 We wanted to upgrade our 3.1.21 to 3.3.10.
 Any intermediate upgrades required first?
>>>
>>> Yes, you have to upgrade to 3.2.latest first (where latest is 16 at the
>>> moment).
>>
>> It is actually suffucient to apply the database upgrades in order.
>>
>> I upgrade from an old largely unmaintained Debian wheezy package to
>> Debain jessie recently. I upgraded the package using apt, then grabbed
>> the upgrade *.sql from the 3.2 package, applied that, and then applied
>> the upgrade SQL from 3.3.
>>
>> You do not need to double-upgrade the whole installation.
> 
> I¹m quite sure this is not correct. Probably it¹s not necessary to update
> all the files. But beside the SQL there are other pre- and post-DB scripts
> you should run. They are responsible for doing conversions (like the one
> from FreeText to DynamicFields with upgrade 3.0->3.1), as well as other
> important tasks (installing scheduler, Š). In short: to be sure, just do
> the complete upgrade path.
> 
> Jan Dreyer
> IT Administrator ‹ Operations ‹ A-SCM-IT NMD Expert
> 
> -
> OTRS mailing list: otrs - Webpage: http://otrs.org/
> Archive: http://lists.otrs.org/pipermail/otrs
> To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
> 

-- 
Martin Gruner
Senior Developer R&D

OTRS AG
Bahnhofplatz 1a
94315 Straubing

T: +49 (0)6172 681988 0
F: +49 (0)9421 56818 18
I:  www.otrs.com/

Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751,
USt-Nr.: DE256610065
Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André
Mindermann (Vorsitzender), Christopher Kuhn, Sabine Riedel

Service Desk-Professionalität auf höchstem Niveau – OTRS 3.4 wird zu
OTRS 4! – Jetzt Beta-Version testen!
http://www.otrs.com/otrs-4-beta-mit-ultra-flachem-design-und-uberarbeitetem-core/?lang=de
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Re: [otrs] OTRS DS mobile app iOS 8.1

[Scott R. Morgan]

Bumping this.  Has anyone else had a similar issue

Thank you!

Scott R. Morgan
Director of Information Systems
Mama Fu's Franchise Group
512.949.3229 Help desk (NEW!)
512-949-3236 Office/Cell (NEW!)
sc...@mamafus.com /  http://www.mamafus.com

From: otrs-boun...@otrs.org [mailto:otrs-boun...@otrs.org] On Behalf Of Scott 
R. Morgan
Sent: Sunday, November 16, 2014 8:00 AM
To: otrs@otrs.org
Subject: [otrs] OTRS DS mobile app iOS 8.1

I just switched from Android/Cyanogen mod running OTRS DS mobile to iOS 8.1 
running same company's iOS version of the app. So far the only issue 
encountered is the cursor is invisible when tying typing text on the app.

Where can the cursor color for a mobile device/app be changed on the OTRS Admin 
dashboard?


Thank you!

Scott R. Morgan
Director of Information Systems
Mama Fu's Franchise Group
http://www.mamafus.com

Sent from my iPhone
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Re: [otrs] Unicode encoding problems in the agent frontend

[Renee B]

Vielleicht liefert
http://stackoverflow.com/questions/7285215/nginx-fastcgi-utf-8-encoding-output-iso-8859-1-instead-of-utf8
die Lösung

-- 
Perl / OTRS development: http://perl-services.de
OTRS AddOn repository: http://opar.perl-services.de

-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Re: [otrs] OTRS DS mobile app iOS 8.1

[Jan.Dreyer]

Hey Scott.

I just switched from Android/Cyanogen mod running OTRS DS mobile to iOS 8.1 
running same company's iOS version of the app. So far the only issue 
encountered is the cursor is invisible when tying typing text on the app.

Where can the cursor color for a mobile device/app be changed on the OTRS Admin 
dashboard?

I don’t think this is the appropriate place to ask. Afaik "OTRS DS"  uses the 
JSON interface that OTRS offers. This way it does not rely on the editor OTRS 
provides but has it own. So you should direct this question to their support 
team.

Regards
—
Jan Dreyer
IT Administrator — Operations — A-SCM-IT NMD Expert

This email may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this email in error) please notify 
the sender immediately and destroy this email. Any unauthorized copying, 
disclosure or distribution of the information in this email is strictly 
forbidden.
-
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs