Custom Field sort order

[Alan Murrell]

Our production system is RT3.0.8 and rt-assettracker from github.  The sort order for the custom fields are displaying in alphabetical order and not the custom order I specified from "Tools > Configuration > Asset Types > (Asset Type) > Asset Custom Fields".

I used the [Move Up] and [Move Down] to move the CFs into the order I want them to display, but no matter what order I choose they always display alphabetically.

Any idea why the custom ordering is not being honoured?  I am not getting any errors.  I was going to turn on verbose debugging, but wanted to check here as well while I did that.

Thanks! :-)

[Alan Murrell]

OK, so I have enabled debug logging and watching when I try to make a change to the "Asset Custom Field".  The only error I can see is the following:

[error]: Couldn't set auth token: AuthToken could not be set to e14d395af86ac0ad. (/opt/rt/sbin/../lib/RT/User.pm:994)

Is this perhaps a permissions error either on one of the RT directories (maybe Apache needs write access to a particular directory?) or possibly a permissions issue with the database?

[Michael Ellis]

I also have trouble with sort order. Recently, I just started naming fields with a, b, c, ... etc. in front of them.

Are you really on 3.0.8?

Mike

--
You received this message because you are subscribed to the Google Groups "at-users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/at-users/-/XVY6KuDww_wJ.
To post to this group, send email to at-u...@googlegroups.com.
To unsubscribe from this group, send email to at-users+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/at-users?hl=en.

[Alan Murrell]

OK, so I fixed the AuhToken error (for some reason that column was missing from the Users table), but I am still unable to get the custom sort order.  I dropped all the AT_* tables and then re-rean 'make initdb" from the 'rt-extension-assetmanager' directory.  It ran the 'schema' and 'acl' parts OK, but had a problem creating the initial asset.  The error that shows up is:

[error]: Couldn't create a Type group of type 'Admin' for asset 1: Could not create group (/opt/rt4/local/plugins/RTx-AssetTracker/lib/RTx/AssetTracker/Type_Overlay.pm:816)

 

[Alan Murrell]

On Friday, 2 November 2012 16:20:32 UTC-7, Mike Ellis wrote:

Are you really on 3.0.8?

Sorry, that should have been 3.8.8 :-)  I will see if I can fix it in my original post :-)   We are actually looking at upgrading to RT4, so at the same time I am working with a dataset in testing an upgrade :-)

I thought about preceding the CFs with numbers and or lower-case letters also, but it makes it look ugly.  Also, many of the CFs are going to be shared amongst different asset types and I may want them to appear in a different order on different asset types (I don't know for sure as we are still planning out the fields we want for each type but there is definitely going to be common/shared CFs amongst the asset types)

[Alan Murrell]

The above should note that we are on RT3.8.8 and *not* 3.0.8 :-)

[Alan Murrell]

On Friday, 2 November 2012 16:20:32 UTC-7, Mike Ellis wrote:

I also have trouble with sort order. Recently, I just started naming fields with a, b, c, ... etc. in front of them.

I think I may put up a totally complete fresh system (not upgraded from any previous version, etc.) and then install AssetTracker and manually create an asset and CFs and see if the sort order problem is still there.

I will report back on my findings.

[Alan Murrell]

OK, so I went onto my test system, blew away the database and ran the 'make initialize-database' for RT and 'make initdb' for AssetTracker', creating fresh installations of each.  Still having the sort order problem :-(

Unless an proper solution is found, I guess we will have to either prefix the custom fields with something that will order them correctly (and decide on a standard ordering), or just live with the alphabetical ordering :-(

Let me know if there is any further information you might require to look into this further.

[gfranzini]

Hello,

I tried to add instructions  in [...]\html\AssetTracker\Asset\Elements\EditCustomFields in the INIT section :

 
 $CustomFields->ApplySortOrder;

and it seems to work well. A similar change should be made in the ShowCustomFields element as well.

HTH,
Gabriele