Dear developers!
In the course of trying to render multipart/related e-mails (those that are created by
OE),
I found a (perl) tool that is used to archive e-mails and newsgroups to standard
html format: MHonArc.
Now I am wondering if anyone could give me a hint what would be the best strategy
to integrate this into OTRS.
My first idea was to write a module "ArticelStorageMHonArc.pm". Altough this would
be straight forward, I could not yet find a way of how to utilize the data from inside
OTRS.
I considered using the "ArticleContentPath" that is stored in the article data base
table.
I can create it from the storage module, but I am somewhat unsure about its correct
semantics, since I am tempted to store a file together with path instead a path alone.
And more seriously ,my problem now is, that I cannot access this field from
"TicketView.dtl". I tried:
$Data{"ArticleContentPath"}, but had no success.
The idea is to use an inline frame to render the content of the path (filename).
Even if this could be made to work, I still fell a little unlucky with this approach
since it is kind of a (dirty?) hack.
But going this way would not interfere much with the core code of OTRS, and I hope
that I will
still be able to do smooth upgrades.
What I would rather like to see is having a "ArticleStorageMbox.pm" for easy archiving
of old
articles and an "orthogonal" method of choosing my renderer i.e. using MHonArc.
But this would need to change much of the (very well written!) source code of OTRS I
am afraid,
and all the mess of track-keeping on upgrades.
In the hope anyone can give me some hints,
Roland
_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev
