If you modify the code in place, your changes will get overwritten when
you upgrade (even a minor upgrade). In general, options for changes are:
1) Change in place. Will get squashed on upgrade, so keep a copy
somewhere and make a note to reapply after upgrades.
2) Create a local directory
Thanks, Jim, for enumerating options. I'm not sure where we'll go with this
yet. Just for the time being I think we are going to use the REST API to
generate the specific report we need and then work on making RT behave more as
we think it should.
I still think it makes no sense at all to
Hello Guys,
just a brief question.
Is it possible to include Articles into messages I want to forward?
Docu does not explicitly state "Forward", therefore I just wanted to
make sure that it is, indeed, not a feature and I am not to stupid to
configure it.
If this is not a feature, is there a
The Fast CGI modules can be picky about permissions. To troubleshoot,
you might start with adding the --with-web-user and --with-web-group
options to your ./configure command to set them to the user/group for
your version of Linux (or FreeBSD). Some systems use 'apache' some have
another
On 2 Feb 2016, at 11:22, Joseph Mays wrote:
Here’s what I get in the logs when try to pull an info.php from
the website
Why would you think that is a reasonable thing to do? I would hope
that would NOT work on any normal RT installation.
I don't know why I wrote that, it was a year
I feel dumb for missing that now. Thanks.
On Tue, Feb 2, 2016 at 2:22 AM, Christian Loos wrote:
> Hi,
>
> it's actually in the documentation:
> https://www.bestpractical.com/docs/rt/4.2/web_deployment.html#mod_perl-2.xx
>
> Best is to switch from mod_perl to mod_fastcgi.
>
Here’s what I get in the logs when try to pull an info.php from the
website
Why would you think that is a reasonable thing to do? I would hope that
would NOT work on any normal RT installation.
I don't know why I wrote that, it was a year ago, but I think I just put in
info.php as a
Thank you for this solution but i think a better solution, for now, is to
stop the error email. Is some way to do that?
În lun., 1 feb. 2016 la 18:53, Parish, Brent a scris:
> I think if you leave a few blank lines at the top of the email it should
> be ok.
>
>
>
> I ran