[rt-users] Plugin install in RT4 / Debian Squeeze

Hello there, I have a RT4 system running on Debian Squueze, installed via Backports according to the install howto. So far, everything works fine, but when it comes to plugins, the hassle begins. I tried to get several plugins to work without success. As an example, I will focus on the

Re: [rt-users] Plugin install in RT4 / Debian Squeeze

Hallo again, it seems I've written to early. The rights of the plugins html files were set to 0700 so that the Apache could not read them. I'll now test the whole thing. Sorry for any inconviniences, Patrick Am 14.12.2012 17:01, schrieb Patrick G. Stoesser: [...] An internal RT error has

[rt-users] RT4 and Reportspam plugin

Hello again, has anybody managed to get the reportspam plugin runnung under RT4? Installation went fine, but in the frontend nothing is shown... Unfortunately, there is no documentation at all for this plugin - I searched google for almost an hour... Thanks for any ideas. Kind regards,

[rt-users] Problemwith rt-crontool: can't get it running

Hello there, even after googleing and trying several hours I'm still stuck with rt-crontool. I'm running RT 4.0.7 via Backports on a Debian Squeeze system. RT istelfs works ok so far, but rt-crontool not. According to the manual, I have added a non-privileged system user (rtcron).This

[rt-users] [SOLVED] Re: Problemwith rt-crontool: can't get it running

I replaced --search-arg general with --search-arg Level1 (Level1 is the Name of one of my queues). And what can I say: It works. At least for a Debian system, the wiki documentation is wrong. Regards, Patrick Am 18.01.2013 15:35, schrieb Patrick G. Stoesser: Hello there, even after

Re: [rt-users] [SOLVED] Re: Problemwith rt-crontool: can't get it running

Aaall right! I understood general as apply to all queues... Regards,pgs Am 18.01.2013 16:01, schrieb Kevin Falcone: On Fri, Jan 18, 2013 at 03:53:25PM +0100, Patrick G. Stoesser wrote: As often, just after I wrote to the list, I got a solution. I just opened the line specified

Re: [rt-users] Rt4 MailgateInstallation: Stubborn 403 Forbidden Error

Hello, I'm also running RT4 ob Debian Squueze, indeed with Exim4. Just a few thoughts after reading your post: # 1 ## My /etc/aliases configuration looks like this: --- test: |/usr/bin/rt-mailgate --queue test --action correspond --url http://centcomm.engeneon.net/rt;

[rt-users] Moving Tickets between queues: best practise?

Hello, I'm running a RT with two queues, Level 1 Support (L1) and Level 2 Support (L2). Ticktes are normally created in Level 1. The Users in Level 1 (L1 Users) have access to both queues and reassign incoming ticktes to the Users in Level 2 (L2 Users). The L2 Users do not see L1, they

[rt-users] Custom status and page action menu?

Hello there, I'm running RT4 on Debian Squeeze, everything fine so far. I have set up a custom status, according to http://requesttracker.wikia.com/wiki/CustomStatusesInRt4. Works fine also. I run two queues, Level1 and Level2. My Level2 users now have a custom status returned. When chosing

Re: [rt-users] Custom status and page action menu?

forgotten to do an update-rt-siteconfig-4, but this is only an idea. After all, one can say that custom statuses work as described in the wiki including menu. Kind regards, Patrick Am 22.03.2013 15:55, schrieb Patrick G. Stoesser: Hello there, I'm running RT4 on Debian Squeeze, everything fine

[rt-users] Odd number of elements...

Hello, when restarting Apache I get the mistakes Restarting web server: apache2 Odd number of elements in anonymous hash at /usr/share/request-tracker4/lib/RT/Config.pm line 1072. Odd number of elements in hash assignment at /usr/share/request-tracker4/lib/RT/Config.pm line 1073. ...

[rt-users] Redirect when no access / no rights?

Hello, as described in 514c70f2.1040...@pgs-info.de, I run two queues, Level1 and Level2. My Level2 users now have a custom status returned. When chosing this status for a ticket, the ticket will change the queue to Level1, will be set to unowned and escalations will be reset to the beginning.

Re: [rt-users] Odd number of elements...

oh! you're right - so i'm gonna check that out and give feedback here. in a few days, actually. regards, patrick Am 12.04.2013 16:28, schrieb Kevin Falcone: On Fri, Apr 12, 2013 at 02:43:31PM +0200, Patrick G. Stoesser wrote: Restarting web server: apache2 Odd number of elements in anonymous

[rt-users] [SOLVED] Customizing via local dir does not work

Hello again, dumb mistake: the rights were not set correct (why?). After setting the rights in my local dir accordingly to the original dir, it worked. Regards, Patrick Am 19.04.2013 17:20, schrieb Patrick G. Stoesser: Hello, I'm running a RT4 (Debian package) on Debian squeeze, everything

[rt-users] [SOLVED] Redirect when no access / no rights?

regards,Patrick Am 12.04.2013 15:05, schrieb Patrick G. Stoesser: Hello, as described in 514c70f2.1040...@pgs-info.de, I run two queues, Level1 and Level2. My Level2 users now have a custom status returned. When chosing this status for a ticket, the ticket will change the queue to Level1

[rt-users] Modifying Update.html?

Hello there, I'm stuck trying to customize RT. Normally, when updating a ticket with a response (Update.html?Action=Respond), the test input field is red. This is a warning for the user that the response will be sent out to the customer (unlike when just commenting). Now what I want to do

[rt-users] Problem with Callback / NewTicketsAlert

Hello everybody, I have a problem with callbacks, especially NewTicketsAlert. I put the callback code as described in http://requesttracker.wikia.com/wiki/NewTicketsAlert in my local directory (Debian), which is /usr/local/share/request-tracker4/html/Callbacks/NewTicketsAlert/Elements/MyRT

Re: [rt-users] Problem with Callback / NewTicketsAlert

Am 25.04.2014 19:56, schrieb Kevin Falcone: On Fri, Apr 25, 2014 at 05:08:58PM +0200, Patrick G. Stoesser wrote: I have a problem with callbacks, especially NewTicketsAlert. It appears your problem is with the code in NewTicketsAlert, not with callbacks in general. [...] My assumption

Re: [rt-users] Suddenly, replys to existing tickets open new tickets

ged into the ticket. When the subjet mark was set after that, it worked also. So: The subject tag removal fixed the error, but re-adding the subject tag did not re-add the error. Regards, pgs Am 16.12.2015 um 18:57 schrieb Patrick G. Stoesser: Hello everybody, suddenly, when someone reply

Re: [rt-users] Suddenly, replys to existing tickets open new tickets

And: My thread here was not intended as a reply to Daniel Schwagers message. Unfortunately, I did not compose a new message from scratch... Sorry for that. mfg, pgs Am 16.12.2015 um 21:16 schrieb Patrick G. Stoesser: Hello, partly resolved. The issue "Impossible to assign the t

[rt-users] Suddenly, replys to existing tickets open new tickets

Hello everybody, suddenly, when someone replys to an existing ticket, the reply opens a new ticket instead of merging the reply. A few days ago, this worked perfectly. I already googled, and checked differernt things, but as I did not had changed anything, I don't know what I could do. In

[rt-users] Plugin JSGantt causes CSRF on automatically reload

Hello there, on my working Debian Jessie RT I'm using the JSGantt Plugin which also workes fine except causing a Possible cross-site request forgery on automatic reload. Generally, CSRF occuring were eliminated at the beginning of the installation several months ago by setting # Webdomain

[rt-users] Plugin JSGantt causes CSRF on automatically reload

Hello there, on my working Debian Jessie RT I'm using the JSGantt Plugin which also workes fine except causing a Possible cross-site request forgery on automatic reload. Generally, CSRF occuring were eliminated at the beginning of the installation several months ago by setting # Webdomain

Re: [rt-users] Plugin JSGantt causes CSRF on automatically reload

Pardon me, accidentially threadnapping! Am 23.11.2016 um 10:56 schrieb Patrick G. Stoesser: Hello there, on my working Debian Jessie RT I'm using the JSGantt Plugin which also > [...] - RT 4.4 and RTIR training sessions, and a new workshop day! https://bestpractical.com/train

Re: [rt-users] Plugin(s) stopped working (long)

209) Any hints welcome. Regards, Patrick Am 21.11.2016 um 17:17 schrieb Patrick G. Stoesser: Hello everybody, strange things happen on my RT. I'm running RT 4.2.8 on an Debian Jessie installed via the Debian packages. I started adding plugins long time ago: # Plugins Set(@Plugins,(qw( RT:

Re: [rt-users] Plugin(s) stopped working (long)

schrieb Patrick G. Stoesser: Update: I remembered that I installed JSGantt and Calendar via aptitude and the other plugins via Makefile.PL, make, make install. So I now decided to deinstall everything and reinstall all plugins by one method via Makefile.PL, make, make install. My "double dire

Re: [rt-users] Plugin(s) stopped working (long)

Update: I now made research from bottom to top and found out that all files under /usr/local/share/request-tracker4/plugins were root:staff and 0775 - except RTx-Calendar, which was 0444. I chmoded to 0775 and heureka! Calendar is displayed. What a... What still does not work: The inline

[rt-users] RESOLVED: Plugins stopped working [was: Plugin(s) stopped working (long)]

to your existing @Plugins line. If you're using 4.0, add Set(@Plugins, qw(RTx::Calendar)); or add RTx::Calendar to your existing @Plugins line. Regards, Patrick Am 22.11.2016 um 16:42 schrieb Patrick G. Stoesser: Update: I now made research from bottom to top and found out that all files under

[rt-users] Plugin(s) stopped working (long)

Hello everybody, strange things happen on my RT. I'm running RT 4.2.8 on an Debian Jessie installed via the Debian packages. I started adding plugins long time ago: # Plugins Set(@Plugins,(qw( RT::Extension::EscalationDates RT::Extension::TimeWorkedReport RT::Extension::TicketLocking

[rt-users] All of a sudden: Odd number of elements

Hello there, I'm running RT 4.2.8 (deb-pakets) on a Jessie Debian. RT runs without problems since long time. Now, all of a sudden, the cronjob which calls rt-crontool causes Odd number of elements, for every queue in RT. The exact error message is Odd number of elements in anonymous hash at