I realize that this may not be the right forum to ask such a question with
all the perl “gurus” hanging out, and I sincerely appologize for this, BUT:
Do any of you know if there’s a PHP port of rt available? Or something
that’s neerly as good as rt but in PHP?
I really like the features that rt has, but I don’t speak perl… PHP on the
other hand is no problem at all for me, and since I’d need to hack up rt
quite a bit to be usable for me, I’d need it to be in a language I’m good at
and that’s not perl.
Well, please no PHP vs. perl flamewar, I’d just want to know if there’s
something like rt available in PHP.
There are a couple of PHP ticketing systems on freshmeat, though, personally,
I don’t think any of them are as nice as RT But no, there’s no PHP port
of RT.
-jOn Tue, Feb 27, 2001 at 07:28:09PM +0100, Alexander Skwar wrote:
Hi, all!
I realize that this may not be the right forum to ask such a question with
all the perl “gurus” hanging out, and I sincerely appologize for this, BUT:
Do any of you know if there’s a PHP port of rt available? Or something
that’s neerly as good as rt but in PHP?
jesse reed vincent – root@eruditorum.org – jesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90
Not that I am aware of… but I have often wondered the same thing. PHP does
seem like it would be an easier method to use since nearly everything is web &
MySQL. The things that would have to be perl or some sort of scripted language
would be the mailgate functions (email into the database & etc), plus the CLI
(command line interface) functions.
More rhetorical, but I wonder how many people use the CLI…
Anyhow, the main thing would be handling the email IN… Current iterations of
RT (1.x) save the actual email messages in text files, which almost require
PERL interaction (PHP file manipulation is painful at best… that’s not what
PHP was intended for, either). If the transaction data were saved in MySQL,
that would be another story…
Oh, and if you know PHP well, Perl won’t be that hard to handle. A lot of the
PHP commands originated in Perl … well, maybe that’s not accurate… I am just
trying to say that a lot of the functions of php translate well to Perl (with
some slight syntactical differences).
There are a couple of PHP ticketing systems on freshmeat, though, personally,
I don’t think any of them are as nice as RT But no, there’s no PHP port
of RT.
So sprach Rich West am Tue, Feb 27, 2001 at 01:56:22PM -0500:
Not that I am aware of… but I have often wondered the same thing. PHP does
seem like it would be an easier method to use since nearly everything is web &
MySQL. The things that would have to be perl or some sort of scripted language
Right - that’s a thing I like so much about PHP. Web and database and …
is so nicely integrated into PHP.
would be the mailgate functions (email into the database & etc), plus the CLI
(command line interface) functions.
Hmm, yeah, suppose so. I could live with a non existing CLI, since it
wouldn’t be used anyway.
Anyhow, the main thing would be handling the email IN… Current iterations of
RT (1.x) save the actual email messages in text files, which almost require
Uh? Not in a database? Hmm, that would be one of the things I’d have to
change.
Oh, and if you know PHP well, Perl won’t be that hard to handle. A lot of the
PHP commands originated in Perl … well, maybe that’s not accurate… I am just
trying to say that a lot of the functions of php translate well to Perl (with
some slight syntactical differences).
Yes, I had a look at the rt src. I understood pretty well how things are
done, but there are too many things that I don’t know about perl to make a
perl rt a viable solution FOR ME. It would require me to learn perl very
well and also to understand the complete source of rt. That’s too much
right now (no, I’m not whining, but if I am, I’m just whining about my
“incompetence”).
Rich West wrote:
-> More rhetorical, but I wonder how many people use the CLI…
Speaking from personal experience with other ticketing systems, you use
it so rarely that you forget it’s there.
Then a time comes when you need it - you need to do something “script-ey”,
making the same change to 1,000 tickets, or whatever - and suddenly
you’re praying with all your heart that there is in fact a CLI. With a
CLI, you just bang out a script that calls the CLI programs and you’re
done in a few minutes. Without the CLI, you either spend days pointing
and clicking via the web interface, or you spend days chewing through
the internals so you can write something to do what you need with SQL.
In short, it’s worth keeping. It’s a hell of a lot easier to develop it
alongside the web interface than on a production system, in a time crunch,
when you haven’t looked at the internals in a year.
-Robert Tarrall.-
Unix System/Network Admin
E.Central/Neighborhood Link
But no, there’s no PHP port
PHP does
PHP does