userpoints 5.x-3.1

Stable release of Userpoints API 3.x.

Major features:

New API 3.x of Userpoints

• Simpler arguments, with sensible defaults.
• Arguments as an associative array, hence less work in future modules.
• Categorization of points (pools of points).
• Informative return info, as an array too.

Thanks to jredding for coding it, and to dami for the ongoing testing, and greggles for suggestions and feedback.

Views integration

Thanks to corsix and GHOP.

Basic Workflow NG integration

Thanks to fago.

Detailed change log below.

• #202167 suggested by greggles, code by jredding: Provide a reason for failure. Return is now an array instead of a true/false response. Please update your code accordingly. README and function comments updated to reflect new return code for userpoints_userpointsapi.
• #206101 by fago, and modularization by kbahey, add basic workflow-ng integration
• #205250 by jredding, implemented get_max_points
• #202168 cleaning up the README file
• #120318 by corsix, Views integration (GHOP task #62)
• Changes to the install file to add columns for point expiration. added to v6 upgrade; Work beginning on v3 upgrade #153626
• #153626 API modified to use an array of parameters, point expiration implemented
• completing work on the v3 API, parameters as array, also fixed a bug in userpoints_admin_txn that prevented points from being edited and also from being assigned to user 0
• Modified point list location to be under admin/user/userpoints instead of defaulting to moderation #170971
• minor string changes
• fixed an issue with t() in the expiry_point_description
• minor adjustments and initiated removal of and implementation of the use of as a boolean
• implemented single variable API call so that if the api is called with a numeric number points are awarded to current user according to site defaults
• #153626 implemented with an added bonus of being able to flip the points award message on and off.
• Updated userpoints_basic to use the new API
• merged transaction_tools with core. Fixed issues #172214, #125880, #156912, #176989
• Categorization implemented in the transactions and API call, reporting and caching table needs to be updated
• Major changes in this version, so many I lost count and didn't keep a good record; sorry. I'll view the Diff then recommit with a better message. Categorization is complete and v3 is ready for BETA testing! DATABASE SCHEMA CHANGE; .install file needs some serious looking-over
• -Completed Categorization changes. A DB record with 0 or NULL is considered in the Uncategorized(CONSTANT) category.
  -misc. code cleanup issues.
  -Added several new functions to support categorization.
  -Modified userpoints table to include new Primary Key so that 1 user can have multiple records.
  -userpointsapi() nows accept a txn_id, if present an UPDATE will be done thus eliminating the need for an external UPDATE and creates a cleaner interface
  -userpointsapi() will accept a status parameter directly (override )
  -Various bug fixes with the _transaction function due to API change and a bug in point expiration
  -Created a separate function for updating the userpoints (cache) table
  -Removed UPDATE statements from admin_approve, admin_txn
  -changes to admin_manage, list_users, user_exists, admin_approve, admin_txn_submit,
  -Fixed my_userpoints to display proper status msg from txn_status
  -userpoints table schema modified to DROP the PK on uid, ADD a new PK named pid (points ID) and ADD a new column tid. Allows for caching of category specific points.
• Minor changes for translation
• updated userpoints_ecommerce to new v3 API
• Updated README.txt with update API changes
• Update point expiration to use the API for Updates for consistency sake. Also fixed a minor bug with cron
• Passes coder module now.
• turned may_cache back to true and removed some errant debug code. Now its ready for a release, fingers crossed
• fixed a minor bug in the .install file. OK fingers crossed again.
• Fixed max points issue
• fixed version issue
• squashing bugs #158552
• Minor change to allow the Uncategorized category name to be translated in the branding
• minor changes to .install file to properly create the schema
• type in .install file
• Squish Squash #184502 #184472 as well as fixed some translation issues with categories and cleaned up some constant names
• Fixed a minor bug with messages not being displayed
• Trying to squash #183520
• resolved an issue where an anonymous user could potentially receive points
• Fixed userpoints block so that there is one block for every category #185580
• brought back /userpoints so that its useful again; blocks are complete
• whoops typo in a single line
• Made the Highest Points blocks configurable for record count
• Commented the code that is currently in question, hopefully someone can help squash this bug #183520
• Updated .install file to add in the new fields #184896
• #184896 implemented while wearing a 'make me sexy' facial mask! he he 呵呵��
• Fully implemented #184896 into userpoints_basic.module
• fixed a minor bug where the cache would be updated even if the txn SQL query failed
• Updated the reports to links to the comments or nodes that caused the pointsw
• updated .install file as the initial creation of the table didn't contain the changes in update 7. This was an oversight
• fixing .install file
• #183520 has been fixed.. backward compatibility is next. This bug is fully squashed yet
• Testing commmit to a 5--3 branch.
• #198533 ezyang is right the tid should have been null to begin with, I made the change in .install need to modify throughout code of .module
• #202093 Thanks greggles
• #200592 minor issue.. patched up Thanks
• #198638 cleaned up minor things but works as stated.. nice addition
• #194286 fixed
• #158490 permission removed. erroneous
• #172271 fixed
• whoops fixing the highest user block.. slight mistake earlier
• whoops fixing the highest user block.. slight mistake earlier
• #199507 fixed... up to the themers now
• #183520 squashed. honestly I think this is a hack and I do not like it but it does work and there is a clean version available
• #183520 squashed. Removed some debug code and added a disclaimer to the on/off switch for the bug fix. Honestly I think the original code is a hack and people are better off without it as i think more problems are going to crop up from it. Hopefully some will have the time to update userpoints_retroactive to do a dull recalculation so that people can start anew without the old version2 point issues (i.e not having entity_ids)