If listing users with custom fields is a one-off requirement or only super users need to do that task from time to time, registered users and the contents of their custom fields can be listed by a custom query using phpMyAdmin or a similar MySQL client.

The following example creates temporary tables before generating the list. The query assumes that there are three custom fields, field4, field5 and field6, where the field ids are 4, 5 and 6. Replace 'epr28r' with your own table prefix.

CREATE TEMPORARY TABLE IF NOT EXISTS `ep28r_registered`
SELECT u.id, u.name, u.email FROM ep28r_users u
INNER JOIN ep28r_user_usergroup_map m ON u.id = m.user_id
WHERE m.group_id = 2 AND u.block = 0;

CREATE TEMPORARY TABLE IF NOT EXISTS `ep28r_work4`
SELECT u.id, v.value AS field4 FROM ep28r_registered r
LEFT JOIN ep28r_fields_values v ON r.id = v.item_id
INNER JOIN ep28r_fields f ON f.id = v.field_id
WHERE f.id = 4;

CREATE TEMPORARY TABLE IF NOT EXISTS `ep28r_work5`
SELECT u.id, v.value AS field5 FROM ep28r_registered r
LEFT JOIN ep28r_fields_values v ON r.id = v.item_id
INNER JOIN ep28r_fields f ON f.id = v.field_id
WHERE f.id = 5;

CREATE TEMPORARY TABLE IF NOT EXISTS `ep28r_work6`
SELECT u.id, v.value AS field6 FROM ep28r_registered r
LEFT JOIN ep28r_fields_values v ON r.id = v.item_id
INNER JOIN ep28r_fields f ON f.id = v.field_id
WHERE f.id = 6;

SELECT r.id, r.name, r.email, w4.field4, w5.field5, w6.field6 FROM `ep28r_registered` r
INNER JOIN `ep28r_work4` w4 ON r.id = w4.id
INNER JOIN `ep28r_work5` w5 ON r.id = w5.id
INNER JOIN `ep28r_work6` w6 ON r.id = w6.id;

Sometimes websites produce warnings or error messages without giving any clues what caused the issue. Surely this has happened to everyone and it is annoying, especially if it happens at a website you are supposed to maintain. 

Recently someone reported that they are unable to update articles because every time they try they get the message "Warning, Registration failed. Please try again."  Clearly this message does not belong anywhere near the editing process where articles are updated or created. Something must have gone wrong in a third party extension or a home grown plugin.

If you have a similar situation where a seemingly unrelated error or a warning is reported in the browser, search for the text string from the website or clone or simply download the filesystem of the site and search on your workstation. A utility like grep or Windows grep are the easiest to use.

The text of the message is most likely to be found in one of the language files.  This of course assumes that the extension that produced the message follows Joomla best practice of keeping the message texts in separate files, consisting of language constants and language strings.

Third party extensions add their own language files into the languages folder either at the front end or the back end of the site, or both.  Extensions can also install their language files in a subfolder in the same folder where the extension itself is installed. Therefore a text search utility is the best approach to find any obscure messages where the origin can be anywhere in the system.

Once you find a match in a language file, copy the language constant from the start of the line and then search for that constant from the website filesystem or its copy exactly the same way, using a utility like grep or Windows grep. This way you can identify the file or all the files where the language constant has been used and you will be able to identify the extention.

If the message is not defined in one of the language files, it would have had to be hard coded in a third party extension, for example a plugin, which you may then be able to unpublish.

If your Joomla! site has issues in connecting to your SMTP mail server, it is possible to get a detailed log of all the messages exchanged between your Joomla site and the SMTP server.  Inspecting this low level transaction log allows you to see what is going wrong between the two servers and then get your IT department or hosting provider to resolve any connectivity issues. 

Go to Extensions - Plugins and configure the system plugin 'System - Debug' with the following settings:

• Allowed Groups: Super Users
• Log Priorities:  All
• Log Categories: mail
• Log Almost Everything

 

Go to Global Configuration and turn on the debug option in the System tab - Debug Settings - Debug System.  

Go to the Server tab - Mail Settings and click the button Send Test Mail. 

The test result, success or failure, will then get displayed as a system message, but you can download the detailed log file 'everything.php' from the Joomla log folder, usually administrator/logs, or, if your site was installed much earlier, from the /logs folder in the main Joomla folder.

 And this is the email we would like to receive from the website:

More about logging from the Joomla! Documentation at https://docs.joomla.org/Using_JLog