Ticketview HTML not displayed properly

[MAKUT]

Good morning,

i already asked this in the German Area but im still clueless hope you guys can help me.

I have the great "pleasure" to move an old OTRS Version (3.016) from a physical server to a virtual machine.
Updating is no option (they say they need a special custom module that only exists for the 3.0.x versions.)

Here Some infos about the environment:

Both Servers (old-new) are running Server 2008 R2
DB is MySQL
Webserver is Appache 2.2.
Tickets and attachments are stored in the filesystem.

-------------------------
I already had the pleasure to relocate an OTRS Installation a while ago and i did it this way:

Export of the DB (sqldump) and filesystem ( OTRS Homefolder, all config files and tickets/attachments with Windows Server Backup)

Fresh OTRS installation on the new server (Same installer so exactly the same Versions of all components)
Restore of the filesystem in the new installation and DB import

Installation path on both systems are identical ( On both systems it's like D:\programms\OTRS)
----------------------------------------------

All tickets and attachments are accessible and searchable, tickets, agents and queues are there as expected.
But this time i have some problems with the ticketview

All tickets are shown in raw text. styletags are scattered all over the text and links are numbered and listed at the end.

Here is an example of how such a ticket looks like in the view field:
(all personal information have been removed or replaced)

Code: Select all

      td.product-details-block{word-break:break-all}.threeColumns{width:140px
!important}.threeColumnsTd{padding:10px 20px
!important}.fourColumns{width:158px !important}.fourColumnsPad{padding: 0 18px
0 0 !important}.fourColumnsTd{padding:10px 0px
!important}.twoColumnSixty{width:360px !important}table{mso-table-lspace:0pt;
mso-table-rspace:0pt;} 

Neue Nachricht: Ich habe jetzt noch 2 Artikel geka...

[1] 

  Neue Nachricht von: [2]XYZ [3](24) 

Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.

[4]Antworten 

[5]Angebot aufrufen 

 Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem ipsum dolor sit amet.


[6]Prdukt XYZ
[7] 



[8]Angebot aufrufen 

  Machen Sie sich ein Bild vom Käufer [9]


[10]   

Nur Käufe bei eBay sind über die eBay-Käuferschutzprogramme abgesichert. Beim
Handelspartner nachzufragen, ob eine Transaktion außerhalb von eBay
abgeschlossen werden kann, ist nicht erlaubt.

E-Mail-Referenznummer:
[#XYZ]

Nachrichten an dieses Postfach werden nicht gelesen. Bitte antworten Sie
nicht auf diese Nachricht. Wenn Sie eine Frage haben, gehen Sie zu [11]Hilfe &
Kontakt.



Diese E-Mail haben Sie von der eBay Europe S.à r.l. erhalten, die den
eBay-Service über ihre Tochtergesellschaften bereitstellt. Wenn sich Ihr
Wohnsitz außerhalb der Europäischen Union befindet, lesen Sie die
Informationen zu Ihrem Vertragspartner bitte in den Allgemeinen
Geschäftsbedingungen nach. 

©2016 eBay Inc., eBay Europe S.à r.l. 22–24 Boulevard Royal, 2449, Luxemburg

 

[1] http:/ /rover.ebay.com/rover/0/e11050.m1831.l3127/7?euid=7b39acbc4c074afda53[..]
[2] http:/ /rover.ebay.com/rover/0/e11050.m44.l1181/7?euid=7b39acbc4c074afda53a2[..]
[3] http:/ /rover.ebay.com/rover/0/e11050.m44.l1183/7?euid=7b39acbc4c074afda53a2[..]
[4] http:/ /rover.ebay.com/rover/0/e11050.m44.l1139/7?euid=7b39acbc4c074afda53a2[..]
[5] http:/ /rover.ebay.com/rover/0/e11050.m44.l1123/7?euid=7b39acbc4c074afda53a2[..]
[6] http:/ /rover.ebay.com/rover/0/e11050.m43.l1123/7?euid=7b39acbc4c074afda53a2[..]
[7] http:/ /rover.ebay.com/rover/0/e11050.m43.l1123/7?euid=7b39acbc4c074afda53a2[..]
[8] http:/ /rover.ebay.com/rover/0/e11050.m43.l1465/7?euid=7b39acbc4c074afda53a2[..]
[9] http:/ /rover.ebay.com/rover/0/e11050.m3965.l1181/7?euid=7b39acbc4c074afda53[..]
[10] http:/ /rover.ebay.com/rover/0/e11050.m3944.l7013/7?euid=7b39acbc4c074afda53[..]
[11] http:/ /rover.ebay.com/rover/0/e11050.m1852.l6369/7?euid=7b39acbc4c074afda53[..]
[12] http:/ /rover.ebay.com/rover/0/e11050.m1852.l3167/7?euid=7b39acbc4c074afda53[..]
[13] http:/ /rover.ebay.com/rover/0/e11050.m1852.l3168/7?euid=7b39acbc4c074afda53[..]
[14] http:/ /rover.ebay.com/rover/0/e11050.m1852.l3165/7?euid=7b39acbc4c074afda53[..]

Can someone tell me what is the problem?
It's the same procedure as last time but this problem is new to me and i can't find any difference to the old installation.


Thanks in advance for your help.
It's really appreciated.


Greetings

Alex

[MAKUT]

Anybody?

It seems to me i just missed something but can't figure it out.

In the end we want to migrate and upgrade to linux + latest OTRS version but first we have to accomplish this transfer.

[wurzel]

Hi,

move to linux first. then migrate.
You also can ask for commercial help. See viewtopic.php?f=34&t=33332&p=135498&hil ... er#p135498 for details (german thread)

Florian

[MAKUT]

Yes, that's the plan, but before we can do this we need a working copy outside our production environment of our actual install to reduce the downtime to a minimum and for testing purposes.

We asked for professional help and they told us it would be be much saver if we/they can do some testing before we start the process.
This OTRS install is so screwed up...

I really don't undestand why this did not work. I does before and nothing changed as far as i know.

but thanks anyway for the reply and your tips Wurzel

[wurzel]

Hi,

if you managed to get it running on Windows - the linux is much more easyier.

My tipp:

set up a linux with a OTRS Version 5 and get it running.

Then move the /opt/otrs to /opt/otrs5

unpack the otrs.tar for version 4, (and all the other versions down to yours (3.x))

move /opt/otrs4 to /opt/otrs/ and try to get it running on the same machine without errors

move /opt/otrs to /opt/otrs4

and continue with all other 3.x. versions, too...

If all of your versions are running without errors.


Dump the database from production, import it, take the configuration files... restore them on the new machine...

You'll see the OTRS in your version is runing fine. Then migrate.


I would not start with Windows. Really!

regards
Florian

[MAKUT]

Hi Wurzel,

ähhmmm i don't get it.

You're telling me i should install OTRS 5 on a Linux VM and then do something like a downgrade until i reached my 3.0.16 version and then pull it up to 5 again with the given scripts?

If this is what you mean i am sure i will run into Appache problems.
As far as i know the newer versions need Appache 2.4. But 3.0.16 is based on Appache 2.2

If i don't get it maybe you can post your guide in my german post for better understanding?

viewtopic.php?f=35&t=33569

This would be so awesome. Never heard of such a procedure before to reach my goal.
If it works as easy as you let it sound we won't even need professional support i suppose.

Thanks again for your patience and guidance sir

Greetings from Bielefeld


EDIT: Link to german post added

[wurzel]

Hi,

putted the info in the german thread

Flo