Hi,
I’m working on upgrading an RT3.4 instance to RT3.8. One of the
extensions already in use is the above mentioned patch/extension.
The most recent version of this appears to be
http://page.mi.fu-berlin.de/pape/rt3/patches/rt/deactivate_scrip-3.6.patch
and I had a quick go applying the patch to 3.8, but unsurprisingly this
doesn’t work straight off. Before I dive into porting this, has anyone
already done it?
Alternatively, is there a better way to do the same thing nowadays (the
patch allows you to select which global scrips to use on a per-queue
basis, which means that we don’t have to duplicate scrips per queue so
much – I had a quick look for the functionality existing in other areas
of RT but didn’t find anything)?
Judging by http://www.google.com/search?q=rt+global+scrip+per+queue
quite a few people have mentioned this over the years, so I would be
interested to know whether there are any plans to have this merged into
core too.
Cheers,
Dominic.
Dominic Hargreaves, Systems Development and Support Team
Computing Services, University of Oxford
Alternatively, is there a better way to do the same thing nowadays (the
patch allows you to select which global scrips to use on a per-queue
basis, which means that we don’t have to duplicate scrips per queue so
much – I had a quick look for the functionality existing in other areas
of RT but didn’t find anything)?
Yeah, this is exactly the feature we’re looking for, also. Given that
there’s already a model for this – Custom Fields, which are created
globally and then associated with specific queues (or all queues) –
it seems handling scrips the same way would make a lot of sense. With
the current system, if we want to create a single queue that is
excluded from a global scrip, we have to delete the global scrip and
then implement a per-queue scrip for every other queue. Crazy!
It occurs to me that one might be able to mitigate this somewhat
through the use of custom fields (e.g., “only apply this scrip for
queues that have the UseSpecialScript custom field set to ‘enable’”),
but that’s just a workaround.
Lars Kellogg-Stedman lars@oddbit.com
I’m working on upgrading an RT3.4 instance to RT3.8. One of the
extensions already in use is the above mentioned patch/extension.
The most recent version of this appears to be
http://page.mi.fu-berlin.de/pape/rt3/patches/rt/deactivate_scrip-3.6.patch
and I had a quick go applying the patch to 3.8, but unsurprisingly this
doesn’t work straight off. Before I dive into porting this, has anyone
already done it?
I’ve completed this port without too much hassle. Patch against RT
3.8.1, and schema files, here:
http://users.ox.ac.uk/~dom/patches/rt/3.8/deactivate_scrip/
It could probably be cleaned up to be more consistent with modern RT
standards (especially share/html/Admin/Elements/EditScrips) but is
functional.
Cheers,
Dominic.
Dominic Hargreaves, Systems Development and Support Team
Computing Services, University of Oxford
2 (19.7 KB)
I am having serious trouble in getting anything to run.
Could someone please point me in the right direction for a install package
or a howto that actually worked.
Kind regards
Erna Jacobs