[otrs-cvs] doc-admin/de/content/installation upgrading.xml, 1.2, 1.3 upgrading-windows.xml, 1.2, 1.3 applications.xml, 1.2, 1.3 source.xml, 1.2, 1.3 packages.xml, 1.2, 1.3
"CVS commits notifications of OTRS.org" <[email protected]>
| Newsgroups | gmane.comp.otrs.cvs |
|---|---|
| Message-ID | <[email protected]> |
Comments:
Update of /home/cvs/doc-admin/de/content/installation
In directory lancelot:/tmp/cvs-serv24849/de/content/installation
Modified Files:
upgrading.xml upgrading-windows.xml applications.xml
source.xml packages.xml
Log Message:
Synchronized translation files.
Author: mg
Index: upgrading.xml
===================================================================
RCS file: /home/cvs/doc-admin/de/content/installation/upgrading.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -2 -u -d -r1.2 -r1.3
--- upgrading.xml 7 Nov 2012 08:52:41 -0000 1.2
+++ upgrading.xml 26 Nov 2012 09:18:36 -0000 1.3
@@ -23,8 +23,12 @@
</para>
<para>
+ Please note that for upgrades from 3.2.0.beta1, an additional step 9 is
+needed!
+</para>
+<para>
Within a single minor version you can skip patch level releases if you want
to upgrade. For instance you can upgrade directly from OTRS 3.2.1 to version
3.2.4. If you need to do such a "patch level upgrade", you should skip steps
-8, 11, 13 and 14.
+8, 12, 14 and 15.
</para>
@@ -164,4 +168,24 @@
<listitem>
<para>
+ Database Upgrade During Beta Phase
+ </para>
+ <para>
+ This step is ONLY needed if you upgrade from 3.2.0.beta1!
+ </para>
+ <para>
+ Please apply the required database changes as follows: <screen>
+MySQL:
+ shell> cat scripts/DBUpdate-3.2.beta.mysql.sql | mysql -p -f -u root otrs
+
+PostgreSQL 8.2+:
+ shell> cat scripts/DBUpdate-3.2.beta.postgresql.sql | psql otrs
+
+PostgreSQL, older versions:
+ shell> cat scripts/DBUpdate-3.2.beta.postgresql_before_8_2.sql | psql otrs
+ </screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
Systemkonfiguration aktualisieren und Caches löschen. Bitte führen Sie aus:
</para>
@@ -294,4 +318,34 @@
</listitem>
<listitem>
+ <para>
+ Adapt custom event handler modules
+ </para>
+ <para>
+ Note: this only applies if you have any custom developed event handler
+modules.
+ </para>
+ <para>
+ Since OTRS 3.2, the data payload for even handler modules is no longer
+copied into the %Param hash. You need to explicitly access it through
+$Param{Data}. <screen>
+Old:
+
+# get ticket
+my %Ticket = $Self->{TicketObject}->TicketGet(
+ TicketID => $Param{TicketID},
+ UserID => 1,
+);
+
+New:
+
+# get ticket
+my %Ticket = $Self->{TicketObject}->TicketGet(
+ TicketID => $Param{Data}->{TicketID},
+ UserID => 1,
+);
+ </screen>
+ </para>
+ </listitem>
+ <listitem>
<para>Gut gemacht!</para>
</listitem>
Author: mg
Author: mg
Author: mg
Author: mg
---------------------------------------------------------------------
OTRS mailing list: cvs-log - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/cvs-log
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/cvs-log