CBJUICE2 is a complete rewrite of the original concept. The new version includes delete by CSV and other useful features. This new version makes substantial use of the excellent CB API. CBJUICE2 supports only Joomla 1.5 and 1.6 and 1.7-3+. It’s use in 1.6 REQUIRES the stable version of Joomla 1.6 and CB Version 1.4 or later. Joomla 1.7/3+ requires CB 1.7 or later. DO NOT ATTEMPT TO use earlier versions of 1.6 or CB in combination because of changes in the ACL. We have tested the component as thoroughly as possible but NO warranty is offered. The newest version supports multiple usertypes in 1.7 and also limits the fields in the save function.
Please note, the support forum and the latest version are always on joomlacode at
Please use the correct version for your respective version of Joomla.
READ THE DOCUMENTATION IN THE PDF associated with the release.
Just had to convert XLS spreadsheets into CSV files, name and set the headers order properly, upload the CSV file and that was all. Immediately my CB and core Joomla user tables had the pertinent data stored.
I can even update the user data in edit mode every time the CSV file is changed (existing entries can be kept and new ones are added).
The latest version doesn't seem to support MySQL 4, but that's not really a show stopper these days. Highly recommended for time saving developers.
TIP: After you set up your fields, download so you can see what the fields look like before uploading. Usertype will be there.
It helps when migrating, or just performing actions on a live site that might affect users' information.
What I didn't understand is when I exported the userlist (users.csv), why didn't it export the password hashes with it. The answer: The passwords are stored in the core users list that comes with joomla so it is referenced there. If you need to mess around with the joomla users list, I recommend using the original JUICE, that deals with it.
Otherwise, great utility! Does everything at a drop of a click! Hats off to the core team!
I can add the password to the save but it will be hashed. My concern has been that people will try to reload a hashed password. The challenge is that with continual changes to the hash, this could get into really messy things. It is NOT possible to export passwords in a clear format. If you have specific suggestions, use the joomla code forum because I would be interested.