Search will search all fields in the current list for the search text and return users who are in the current list and have that text in a field in the list.


Search will search all fields in the current list for the search text and return users who are in the current list and have that text in a field in the list.
A range of formats are available for each type of field. The plugin will try work out what type each field is. If it doesn’t, you can set it yourself in the ‘Fields & Nice Names settings.
Then if the ‘Format’ section of each list, formats can be chosen for that field.
For example: Date Time fields and Unix time-stamp fields (and even an ‘ambiguous date in case you have inconsistent data) can be formatted as:
The actual format of the date, time and datetime options can also be customised. The options are the usual wordpress options AND the custom options from your general settings screen.
user_email field will be formatted with the ‘mailto’ linktype and then each site can tailor this with their own css. Perhaps use wordpress dashicons to show a email icon?
You should ensure that your data adheres to the field type specified. Any invalid data will generally be shown unformatted / raw.
See the screenshots below and the demo sites for more possibilities.
Changing the text in a plugin or theme without editing the plugin or theme files is surprisingly easy IF the plugin or theme has made the text translateable.
Using a plugin like https://wordpress.org/plugins/loco-translate/, ensure the language chosen matches your wordpress language, and choose a location for your files (loco translate helps) that
will be accessed by the plugin or theme (some help with this) and
will not be overwritten by updates – loco translates helps and some plugins/themes help too by offering another lookup location. The recommended custom language file location is /wp-content/languages/.
For more information see http://icalevents.com/3445-an-accent-for-your-website/
Search users text replaced using translation tools – translating english into english!
The amr-user plugin offers wordpress capability control of access to users lists. In wordpress roles have capabilities, and the capabilities determine what the users can do. User lists can also be tagged as ‘public’ so that a viewer with no role can see the list if used on the front end.
If you want to isolate the ‘manage_userlists’ capability to a non-administrator and you don’t already have a plugin to do that for you, something like Justin Tadlock’s Members plugin is useful.
There are two fields that show details of date of registration. When the plugin started I wanted to see a human based ‘days ago’ view as I found that much more helpful to assess how long a user had been a member.
Thus that is the real wordpress registration date fields default formatting. If one hovers over the field full details of the actual date will show.
It is also possible for you to write your own formatting function to format the date any way you would like. For those people who are unable to write their own functions from the example and just want to display the registration date, there is a ‘pseudo’ field created which is called ‘Registration Date’ – it is not a real field though and does not sort well.
In the future there may be the possibility for one to choose from a range of formats. For example I can imagine a number of possibilities:
[2019 Note: Please watch out for major update. First_role will be replaced by Capabilities/Roles. There will no longer be a separate first_role field ]
Do users on your websites have more than one wordpress role ?
On a basic wordpress install, a user usually has only one role. At the simplest, many sites only deal with administrators and subscribers.
The free amr users user listing plugin will extract the first role found in the wordpress usermeta capabilities value and present that as the ‘first role’. This is great for most installs, some may need more reporting possibilities.
WordPress does actually allow for users to have multiple roles. Add in the bbpress plugin and possibly a membership plugin which may create it’s own set of roles in parallel to the wordpress ones (ie not instead of), then you may find a single user may have many roles even if you actually need them to only have one.
Depending how/when a user was created in the system, (converted? created before or after the forum etc) they may/may not have a wordpress default role, they may just have a bpress role for example. Even more confusingly the ‘first role’ may no longer be useful. For example, someone may have been created as a forum participant with while someone else may be wordpress ‘editor’ and then a forum participant. The ‘first roles’ may then differ, when one might think that they should both have participant.
In such a case, other role fields may be useful too. The free amr users plugin will automatically extract all the roles it finds and present each as a field where the user either has a that value (1 or true) or does not. One can use these to exclude or include users from the user lists, or to interrogate the db looking for users with multiple roles etc.
If you need more than that, then you need the amr-users-plus plugin. It adds
The latest update (3.9) adds a admin screen that allows you to
This became essential for anyone using S2member, and handy for anyone using Advanced custom fields which seems to create additional hidden metakeys for every custom field. Thisplugin will attempt to help you out by default excluding as many unnecessary fields as possible. You can then update.
The S2member access cap times field is keyed by time, which means that as time goes by there will be more and more sub fields detected by amr-users and the fields and nicenames page will become impossible.
This is clearly unworkable. So a admin page to exclude meta keys was added. This page will also allow you to delete meta records. Be Careful! This is a confirmation step, but no undo.
The “find fields and nice names” page has been updated to help highlight what’s going on.
Do you want to add css for html generated by a plugin perhaps?
Do you have a custom theme that you are NEVER going to automatically update?
Then edit the themes css, add your custom css to the bottom of the main style.css. This should be in your themes folder under wp-content.
Does your theme have upates occasionally ? If you want to be able to auto update your theme, then it is better to add your css separately.
Some plugin have ways to add a custom css file for that plugin and/or to disable any plugin css so that you may reduce the number of stylesheets. Do NOT edit any plugin css files unless it is a site specific plugin that will not be updated automatically – you will lose your css when the update is applied.
The easiest way to add custom css if you cannot use your themes style.css is probably by using the official wordpress jetpack plugin: http://wordpress.org/support/plugin/jetpack
It has a custom css module http://jetpack.me/support/custom-css/ There are other plugins that allow you to do this.
First you need to work out what css selectors have been provided in the html that is generated. My plugins generally offer many css selectors in the html. The various ‘inspect element’ tools are invaluable here.
They help highlight what css is being applied to the html and what is being overwritten. And of course they help you to see easily what css ‘hooks’ there are to add special styling.
Your custom css needs to work with your theme, so you either need to specify the css tightly enough that no theme css will ever override it, or know that you are not going to be changing themes.
To work out what css to add, ideally you should have a reasonable understanding of css. In particular the concepts of specificity and inheritance
http://coding.smashingmagazine.com/2007/07/27/css-specificity-things-you-should-know/ .
When asking for help you should
You should also know that browsers vary in their implementation and while your hack that you worked out or have been given might look beautiful on your apple mac running safari, results can vary greatly.
If you have any pride in your work at all, you should test the result using something like http://browsershots.org/, or risk the site looking really stupid.
In this example from the amr-users plugin, one can see that:
A ‘funny’ recently presented itself. In the chrome browser, avatars were not showing up, despite they being there in the html code.
My first thought when I hear of browsers responding differently is to check html validation – browsers often cope with errors but sometimes not.
In this case, it was the css that turned out to be the problem.
An invaluable tool to debug these things is the ‘inspect element’ firebugs or chromes and the ability to deselect or add css to see what is overriding what. See http://bigemployee.com/4-simple-techniques-to-quickly-debug-and-fix-your-css-code-in-almost-any-browser/
Fairly quickly one could see that somehow the inline attributes were being overwritten.
Scrolling back up through the css to see what might be overwriting that css, I paused thoughtfully at a image max-width and unticked and reticked some css.
As soon as I unticked the max-width the images reappeared in chrome.
A quick web search showed that others had encountered this before and had some suggestions on overcoming this. It seems Chrome interprets the rule differently from Firefox. It assumes the image can freely be shrunk, and with a long string of text in the cell next door, it squeezes the images.
So some possible solutions appear to be: