Finalise your fields ‘nice names’, your user lists and their headings.
Make sure you have any available wp and plugin translations loaded, or create your own string translations for public facing strings. The strings within the formatting of the lists can be translated & localised. see demo.
If you have headings on the userlist or directory, either:
create translations for the headings using wpml’s admin text translation feature. Choose the option ‘amr-users-custom-headings’ – it will have all the headings for all the lists. See screenshot below.
OR, copy the list and make a version with translated headings.
Last step – do one of the following:
One userlist page for all languages. All strings get translated in realtime. If you have no additional text on the page that requires translation, this may suit. This is shown here: https://lang.wpusersplugin.com/
One userlist page for each language re-using the same userlist on each of the language pages. Good with translated custom headings as per above or if the userlist is not using headings.
A page for each language with a separate user list for each language page. Copy the list you created for each language and change the headings to suit the language.
Where to get translations:
A language pack may be available from wordpress. For status of available language files, please see https://translate.wordpress.org/projects/wp-plugins/amr-users/ and consider contributing translations for the languages you are skilled in. If a language for a plugin has reached 90% complete, a language pack for it will be automatically generated and made available. These are stored in …wp-content/language/plugins.
A plugin may provide some translations and load from ‘plugin_rel_path’. Eg: …wp-content/plugins/amr-users/languages. For amr-users these have been provided by volunteers. I have no way to judge their completeness or quality. Note: If a rel_path is not provided, wordpress will load translations from the plugins top folder wp-content/plugins/the-plugin
a translation editor may offer another way to translate strings and will probably add a filter to ensure that these are uploaded. WPML stores these by default in …wp-content/languages/wpml
Own translations can also be loaded whereever you like and not have them overwritten by a language pack. Use a
amr-users-plus reuses some of the amr-users translations and the wp translations, so a scan of it’s files will show these domains too.
The amr-users-plus export to excel feature uses the phpoffice/phpspreadsheet library. The library must be accessible on the server. Here are two ways to make it available:
Option 1: the easy low tech way: use the plugin cbxphpspreadsheet
Add the plugin https://github.com/codeboxrcodehub/cbxphpspreadsheet to your wordpress installation. The plugin does not need to be active, it.only needs to exist in your wordpress plugins folder. It may be safer to activate the plugin so that you don’t accidental delete it thinking it is not in use.
It is possible to add text to the field value before or after the field value. There are not many good reasons to do this:
Repeated static text just clogs up the screen, headings are better.
Adding html for styling reasons is not suggested.
Better to style with css.
However let us assume for example that you wish to add the text ‘Born: ‘ to every Birthdate field with content. You can add it to the ‘before’ text of the Configure list> Before & After tab. See screen shots below.
This ‘before’ text is not shown if the field is empty.
Note that the text becomes part of the field value.The full text is included in the cache and the csv and excel extracts.
It is strongly suggested that you do NOT use this feature for styling. CSS is a better way to style fields. There are a lot of meaningful css selectors offered in the user lists so that one can target almost any field.
It is also possible to keep the field values clean for csv and excel and to use css to add the extra text. This can be done using the before and after pseudo elements. These pseudo elements can also be used to hide and replace content as you can see on this user list demo page where the field content can be replaced by text or an image.
In a recent amr-users-plus update, a variety of new formatting options were added. This was prompted by a request to handle buddypress uploaded files, like resumes or images that are stored with a relative url.. In responding to this, the ability to choose a variety of formats for urls, telephone numbers, emails etc was added to amr-users-plus. See the buddypress user directory demo site for some examples. The wordpress dashicons font is used, enabling the icons to take on the colours of your theme. In addition, since it is possible for you to change the icons used as they are delivered using css.
As always I am happy to entertain requests for such features. I try to deliver them in ways that offer generic consistent use. Further updates are on the way to refresh other add-ons in line with a big refresh of the main amr-users plugin.
The amr-users and amr-users-plus* suite of programs enable websites to list their user data from the wordpress user database and related tables (eg CIMY user tables). See the individual addon plugin descriptions to see the tables they access. The plugins do not add or store any other personal user data – they are aimed at simplifying the development of lists or reports of user data.
The design of the user data and the decision to display the data in a user list generated by the plugins is the website’s responsibility. The base plugin currently caches user lists to simplify querying the website user data for the designed user list. The cache content is determined by the website – it is the user list content. These caches are temporary. They are stored in the wordpress database and are subject to the same protections as other website data in that websites wordpress database. If a user record is updated or deleted, the next cache run will delete all existing user data for that list and create a new cache.
Privacy and consent to the display of any personal data in a user list is the website’s responsibility. The base plugin offers a setting to determine whether a user list is can be shown publicly or not. The website is responsible for determining what goes into any such user list and whether these lists are made publicly available or simply run in admin by an appropriately authorised person.
The plugin offers the feature of a csv extract of a user list. If a list is public, the csv extract is stored as a file on the websites server. Security and safety of this file is the website’s responsibility. If the list is not public, the csv extract can be generated real time by a user who has the appropriate security capability.
When the plugin is deleted, the cache tables and plugin options are also deleted.
Many of the add-on plugins merely format the user data or offer searching, filtering and navigation features unrelated to the capture or tracking of the data. In some cases they are merely example plugins and it is the website’s responsibility as to how these plugins are modified and what they data they might then make it possible to store.
The above applies to the following user related plugins:
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/.