It would be nice if one could customize the operation, description and entity_type text through some settings page.

For example i don't think delete is a good name for the operation on an purchase. I would like it to be something like Purchase.

But instead of make changes in the module it would be nice if these were just settings.

Comments

bmagistro’s picture

bmagistro commented

I am not sure if I will fix this, but an option I would be open to is creating an include file that you could just edit those in the file. The operations are in reference to what is going on with your points, in a purchase where you pay with points, they are "deleted" from your total points. I will have to look at something with the userpoints module because I vaguely remember this coming up in my discussion with the developer there.

jredding’s picture

jredding commented

in regards to userpoints, the operation field is a varchar32 so it may contain anything it wants. However there is a different conversation going on over here that may solve this issue
http://drupal.org/node/257515

in short the operation is a field that should be tied in with the module is doing and should be reserved for development work. for example with nodes the operation is 'insert' and then entity_type and entity_id are filled in with 'node' and the $node->nid (respectively). This way the userpoints_basic module (and others) know what happened.

However 'insert' (just like 'delete') isn't very descriptive for the user. Thus their is a discussion (and nearly a decision), linked above, that would change the userpoint reports so that they display the 'description' vs. the operation field. This way the operation can stay as a programming method (like insert, update, delete) and description is displayed to the user.
http://drupal.org/node/257515

bmagistro’s picture

bmagistro commented
Status: Active » Closed (won't fix)

Closing, won't fix due to D5 EOL notice. When D7 dev starts please feel free to add a feature request. If I remember I will check back here and see what "won't fix" items could be brought forward.