[rt-devel] a couple of minor 2.0.1 issues

[Vivek Khera]

I'm finally playing with setting up RT myself, after lurking here for
a couple of weeks.

Anyhow, I wanted to do the install as non-root user.  This fails
because rt2/etc directory is chmod'd to 555, which makes little
sense.  The directory should at least be 755.  If the install is owned
by root, then 755 doesn't let anyone else write to it anyhow, but if
the install is non-root, 555 prevents the install from completing,
since the owner can't write to the directory.  The change is just to
the Makefile:

--- #Makefile~	Wed Jul 18 13:55:27 2001
+++ Makefile	Wed Jul 18 13:55:27 2001
@@ -206,7 +206,7 @@
 	chmod $(RT_READABLE_DIR_MODE) $(RT_BIN_PATH)
 	chmod $(RT_READABLE_DIR_MODE) $(RT_BIN_PATH)	
 
-	chmod 0555 $(RT_ETC_PATH)
+	chmod 0755 $(RT_ETC_PATH)
 	chmod 0500 $(RT_ETC_PATH)/*
 
 	#TODO: the config file should probably be able to have its


So now I've got it running, and am testing out some Scrips.  I notice
that sometimes the mail messages contain extra CTRL-M characters at
the end of the lines.  This comes from the TEXTAREA form fields.

Browsers send these form elements with CR/NL end of line.  This needs
to be normalized to just NL end of line for use inside unix.  I've not
looked into where exactly this needs fixing, but the fix is more or
less something like this:

  $data =~ s/\r\n/\n/g;

in Perl.

Also, the comment in config.pm about leaving hostname blank for
fastest connection to the database is false for Postgres.  It causes
an error on connect if you do that.

Finally, a qustion: how do I make the "resolve" scrip template include
the content of the resolution response?  That is, I click "resolve"
and enter a message.  How does that get sent to the requestor also?
Right now I just get the stock template text.  I tried adding
{$Transaction->Content()} to the template, but that came up empty.  I
also tried switching the response type from comment to normal response
and that ended up sending two replies, one the normal message with the
response content, and one the resolved message.