Hi there,
Have been playing around with the Asset Tracker extension in an RT 4.2.2
environment, using the rt-extension-assets master branch from 20140228.
All seems to work very nicely so far, however, in looking to populate
a large set of common assets, I came to use the Bulk Update facility
and found that, of the Custom Fields I had defined for the catalog(ue)
in question, I wasn’t presented with either a “Wikitext area” or a “Select
date” widget on the Bulk Update page,
(See attached PNG)
although those widgets do appear within the page for a single asset.
Is this just a “ToDo”, something broken that should be there, or something
I’ve missed in the setup so far?
For completeness, the browser is a Firefox 26.0 within an Ubuntu 1204 OS,
and I am currently testing using the standalone rt-server interfacing to a
MySQL database.
Kevin M. Buckley
eScience Consultant
School of Engineering and Computer Science
Victoria University of Wellington
New Zealand
Have been playing around with the Asset Tracker extension in an RT 4.2.2
environment, using the rt-extension-assets master branch from 20140228.
All seems to work very nicely so far, however, in looking to populate
a large set of common assets, I came to use the Bulk Update facility
and found that, of the Custom Fields I had defined for the catalog(ue)
in question, I wasn’t presented with either a “Wikitext area” or a “Select
date” widget on the Bulk Update page,
Both of these are limitations derived from RT, not Assets itself. RT
4.2.3 contains bulk updating of Date and Datetime fields; I’ve pushed a
4.2/bulk-update-wikitext branch that should cause Wikitext fields to
appear; you should be able to apply
https://github.com/bestpractical/rt/commit/1e05e76.patch atop 4.2.3.
Bingo!
Will give that a go: thanks.
Please keep all replies on-list.
Can I also assume that the 4.2.3 plus patch additions would cure what I’ve
seen in the log, since trying to add in in the
RT::Extension::Assets::Import::CSV
module, namely the three criticals
[3757] [Thu Apr 10 00:14:11 2014] [info]: Successful login for root
from 127.0.0.1 (/opt/rt4/sbin/…/lib/RT/Interface/Web.pm:819)
[3755] [Thu Apr 10 00:14:38 2014] [critical]: Unknown CustomField
type: Wikitext (/opt/rt4/share/html/Elements/BulkCustomFields:81)
[3755] [Thu Apr 10 00:14:38 2014] [critical]: Unknown CustomField
type: Date (/opt/rt4/share/html/Elements/BulkCustomFields:81)
[3755] [Thu Apr 10 00:14:38 2014] [critical]: Unknown CustomField
type: Date (/opt/rt4/share/html/Elements/BulkCustomFields:81)
which I don’t get without the CSV import model in ?
The CSV import module is totally unrelated to those warnings. Those
warnings show up on the bulk page of any search (of tickets or assets)
which contains Wikitext or Date CFs.
But yes, running 4.2.3 plus the patch I linked will quiet those
warnings.
Please keep all replies on-list.
Apologies, I tend to just hit reply, expecting things to go to the lists.
What can I tell you - old habits die hard.
The CSV import module is totally unrelated to those warnings. Those
warnings show up on the bulk page of any search (of tickets or assets)
which contains Wikitext or Date CFs.
Yes, can see that now.
I was overwriting a log file and only noticed them after adding in the
CSV import module.
But yes, running 4.2.3 plus the patch I linked will quiet those warnings.
Because I’d copied the old RT installation dir as a base for the 4.2.2 → 4.2.3
upgrade, I found I had to clear the leftover mason_data/obj cache before
everything worked as expected.
Everything now works as expected though - thanks again for the patch.
Kevin M. Buckley
eScience Consultant
School of Engineering and Computer Science
Victoria University of Wellington
New Zealand