Adds a dynamic list of entries to each record. Log work hours, attendance records, list your collection, places you've been...adds a whole new dimension to your Participants Database record.
Product Setup
- Setting Up the Log
- Configuring Log Entry Fields
- The Admin Record Log Display
- Adding Entries
- Exporting/Importing Entries
- The Frontend Log Entry Display
- Showing an Interactive Log
- Showing a Global List of Log Entries
Global Log Configuration
In the Participants Database admin menu will be an item named “Participant Log.” On that page you will find the global settings for all logs under the “General Settings” tab. This is where you set things like the template (which controls the layout) and other general settings for all the logs. These settings can be individually overridden in the log field definition if needed.
Setting up the Log
The first thing to do to set up a log is to add a new “Participant Log” field to the Participants Database on the Manage Database Fields page. This new field is the “container” for the log, and in most ways is simply another field in the database. The General Settings tab of the plugin settings menu provides a way to add a new log. When this field is created, a new table is added to your WordPress database which will hold the data for the log.
It is important that the name of your log should be the name of what is stored in it. If, for example, the log is meant to record a person’s time spent volunteering, you might call it “Volunteer Hours.” If it is storing a record of class attendance, you could call it “Class Attendance” or “Attendance Record.” You can change the title that is displayed once it is set up, but the name of the log field can’t be changed, so it’s worth taking a minute to think about what you call it before committing the name. Once you set up the log field, you can configure what is recorded in each entry of the log you created.
Configuring the Log
On the Participant Log admin page, you will see a tab for the log you created. Under that tab you can configure the log: you can set the name for an entry or entries which will help the user interface make more sense. There are more settings that determine what the frontend user can do and also how the log will be displayed in various contexts. This will be explained in more detail later.
Configuring Log Entry Fields
Each log can have as many fields as needed to hold whatever information you need to store in each entry. The user interface for that is the same used for managing the fields in the main database. You can add fields, and then configure each field as needed. They work the same as fields in the main database. Each entry field you create for the log adds a column to the log’s database table.
Field Visibility
Entry fields have a “Visibility” setting that determines the context in which the entry field will be shown. “Public” means the field will be shown in all contexts. “Private” means the field will only be shown to the owner of the record and administrators. “Admin” means the field will be visible to administrators only.
Searchable Fields
When list searching is enabled, only fields that are both visible and marked as searchable will be used to get search results. This is helpful to making searches more efficient and avoids spurious results.
Searchable log entry fields are also available in regular Participants Database list displays so that records with log entries that match the search can be found.
Sortable Fields
Fields that have this setting enabled will be shown in the header of log entry list displays so the log can be sorted by the value of that field.
Field Validation
Entry fields can be made required in the entry field’s configuration. The entry fields use “client side validation” which means the user’s browser will perform the validation and provide the feedback. This is going to look slightly different on every platform, there is little you can do about that, but it has the upside of working on all platforms and devices. To make a field required, you set the validation setting to “required.” You can add to the field validation configuration by using validation attributes.
The Admin Record Log Display
The log display on the record edit page in the admin shows a list of all the entries. The list is paginated, and the number of entries shown on each page of entries is determined in the general settings for the log, in the “Entries Per Page” setting.
The display for the log on the frontend is similar, but what controls are shown depends on the configuration.
Entry List Filtering or Searching
There is a search input at the top, any text typed into the search input will be used to filter the list of entries. On the admin side, all the visible entry fields are included in the search. On the frontend, only fields marked as “searchable” will be included in the search.
Entry List Sorting
The entries can be sorted by clicking on the blue arrow icons seen in the top bar. The fields that can be used for sorting are configured in the log entry fields configurations: check the “Sortable” checkbox to configure the field to appear in the sorting bar.
Adding Entries
Once you have the entry fields set up, you can begin adding entries to the log. Entries can be added in the admin by going to the admin edit record page for the record you want to add log entries to. Find your log field on the edit record page and in the display for the log field, you will see a button with a plus sign for adding a new entry. Clicking that will bring up a form for entering the data for your log entry. Each entry may also be edited by clicking the pencil icon next to the entry. Clicking the pencil will open a form where the contents of the entry can be changed. Entries can be deleted individually by clicking the red on the entry line. When the “X” is clicked, you will be asked to confirm deleting the entry. There is no undo, deleted entries are gone forever unless you restore it from a backup.
Exporting/Importing Entries
In the admin record edit display (Edit Participant), the entry data for the record’s log can be exported as a CSV file. This works pretty much the same as exporting records from Participants Database: if you have used a filter, the export will only include the entries shown after the filter is applied. Records can also be imported with a CSV file. It’s also possible to import and export data for all records on the Participant Log admin page under the tab for the log.
The Frontend Log Entry Display
In single record and editable record displays on the frontend, the log is displayed as a list of entries. It is very similar to the display in the admin, only the ways that the user can interact with the list are controlled by settings. This is so you can choose whether the log can be added to by users, entries edited, deleted, etc. When the record is displayed using the [pdb_single] shortcode, a list of entries is shown using the template style chosen in the Participant Log settings under the general tab. The entry list in this display can be sorted and filtered. Only log entry fields that have “public” visibility will be shown in this display.
Display Templates
For the frontend displays of the log entry list, 3 basic templates can be chosen. Which one you choose is going to be determined by what you need to show, and what is going to work best for your users.
The Table template will put the log entries into a fixed-width grid so all the values will line up below a header row. This can be the clearest way to show the log entries, but you can only control the width of the table by controlling how many log entry fields you’re showing. Also, it isn’t great on small screens because the width is not determined by the device’s screen width, and so horizontal scrolling is usually required to see all the information.
The Responsive template takes the approach that every log entry field is a separate element with its own width determined by the title and data display. These elements can flow into whatever configuration will fit on the screen. With this template, all the data will be visible on any device, but it can be cluttered.
The Grid template is kindof a bend between the two. It is responsive in that the width of the log display is determined by the width of the device display, but instead of each entry field having its own width, the widths of the entry fields are controlled into columns. This can result in a more organized and easier to see display of the log entry data.
For any kind of responsive display, some adjustments of the CSS that controls the layout are often needed. These additional CSS rules can be placed in the Participants Database Custom CSS setting.
The Summary Display
Each log entry list display may optionally show a “summary” which is configurable to show an important value, such as the number of entries. By choosing a different sum type, the summary can also display other values. If the sum type is a numeric field, the summary will be a sum of the entry values for that field, such as for a work log that shows the number of hours worked. If the field is not a numeric field, the summary will show the number of records that contain a value for that field or if the field has a default value, the sum will show all the fields that have a value different from the default value.
When searches are performed on the list or when a date range is selected, the sum value is immediately updated to show the correct value. This also happens when entries are added, deleted or edited.
This sum value is also saved in the main database so that in Participants Database list displays, the list can be sorted by the summary value: for example you could rank volunteers according to the number of hours logged, or place the collector’s club member with the largest collection at the top.
Showing an Interactive Log Entry List
When the editable record is displayed using the [pdb_record] shortcode, the log entry display is sortable and filterable, but it is also possible to enable adding new entries, editing and deleting entries, and also import and/or export entries using a CSV file. The settings that control access to these features are in the Participant Log settings, under the General Settings tab. The user interactions in this display are very similar to what is possible in the admin. Log entry fields that have a visibility setting of “public” or “private” will be seen in this display.
Frontend Imports and Exports
The interactive log list display can also be configured to allow the user to import and/or export data to a record’s log. This is enabled under the global settings for the [pdb_record] log display.
Global Log Displays
It’s possible to display a list of log entries that are taken from all the log entries in all records. There is a special shortcode [pdb_log_list] that will show all the entries in the same way that the Participants Database list shortcode shows a list of Participants Database records. You can use shortcode filters, custom templates, search, sort, etc. to customize the display.
An example of the use of this shortcode would be a car club, where each member keeps a list of the cars in their collection. The global log display could be used to show all the cars in the club.
If you’ve got more than one Participant Log defined, you can tell the shortcode which one to use with the log_name attribute. Just give that attribute the name of your log, and it will show entries from that log. For example:
[pdb_log_list log_name=cars]
Log List shortcodes can be filtered just like the Participants Database List shortcode, you can filter by fields in the main database and by fields in the log. Check out the linked article for details.
Product Settings
General Settings
These settings will affect all logs, but it is possible to override them for a specific log in the participant log field definition attributes setting.
Enable Log Search: when checked, a search input will be shown above the display of log entries. This search input will search on visible fields only.
Enable Log Sorting: when checked, fields that are configured as “sortable” will show as sorting links in the header of the log entry list.
Enable Date Created Sorting: the “Date Created” field is an automatically set timestamp for every entry. This switch allows the user to sort the entries by this timestamp field.
Entries Per Page: sets the default number of entries to show in the list. If there are more entries in the log than this number, a pagination control will be shown.
Record Shortcode Settings
These are settings that pertain to showing the log list when using the [pdb_record] shortcode. The log list in this context is editable.
Record Shortcode Log Template: select the display template to use when showing the log entry list.
Enable Creating New Entries: when checked, allow the user to add entries.
Enable Editing Entries: allows the user to edit entries.
Enable Deleting Entries: allows the user to delete entries.
Allow Log Export: allows the user to export a CSV with the log entry data.
Allow Log Import: allows the user to import log entries in a CSV file.
“Slide In” Entry Controls: when checked, the log edit controls will be hidden until the user hovers over an entry. This is good for compact displays.
Highlight Color: lets you select the color to use when highlighting an entry while it is added or edited.
Single Shortcode Settings
These setting are used when showing the list of log entries when using the [pdb_single] shortcode.
Single Shortcode Log Template: selects the display template to use when showing the log entry list.
Individual Log Settings
For each log you have defined, there is a tab and under that tab are settings that are specific to that log.
Log Fields
In this section, the fields that are used for each entry of a log are defined. The interface is very similar to the one used on the Manage Database Fields page. There are a few differences, for example, there are no field groups (instead there is a “visibility” selector). And, like the Manage Database Fields interface, which options you can set depend on the type of field you have created. You can edit, delete and add log entry fields in this interface.
It is highly recommended that you define all the fields you need to use before adding entries to the log.
Log Options
For each log, a set of options is available:
Log Entry Name: name for a single entry.
Log Entry Name Plural: name for several entries.
No Entries Message: message to show when a log has no entries.
Search Field Placeholder: when the search input is shown, this placeholder string will serve as a prompt for the user.
Entry Image Height: the nominal image height for images uploaded to a log entry. The aspect ratio will be preserved in most cases.
Entry Dates
These settings are for configuring how entries are dated.
Primary Date Field: this allows you to select a log entry field to use as the date for the entry. It defaults to the timestamp that is set when the entry is created. You would use this in the case of something like a list of events where the date of the event is more important than the date the entry was created. This date field will be used to sort the entries chronologically.
Show Log Entry Timestamp: every entry has a timestamp, this preference lets you make that timestamp visible.
Timestamp Title: if you are showing the timestamp, this is how it will be labeled.
Date Range Filter
It is possible to filter entries by date range, these settings configure the date range interface.
Enable the Date Range Filter: check this to turn on the date range control for the log.
Date Range Filter Heading Text: title for the date range control. Leave blank for no title.
Date Range Filter Button Text: text for the button that performs the date range filtering.
Entry Sum Display
The “entry sum” is a feature of the log where a configurable sum is shown. The default is to show the number of entries, but if there is a numeric field in the log entries, the entry sum can show a sum of those values. For example, in a work log, it can show the number of hours worked.
Show Entry Sum in Record Displays: this is to enable a summary display just above the list of entries.
Sum Type: this is where you would configure what is summed.
Sum Display Template: this gives you a way to control how the sum is displayed. There are a number of “value tags” you can use to show dynamic values from the log in the summary display.
F.A.Q.
Is it possible to override the global setting in individual logs?
Yes, this happens in the log field definition on the Manage Database Fields page in the main plugin. You add your override to the “attributes” for example to override the global setting and allow adding entries on the frontend:
allow_frontend_add::true
Here is a list of the global settings with the proper name to use in the attribute:
| Setting | attribute name |
|---|---|
| Enable Log Search | enable_log_search |
| Enable Log Sorting | enable_log_sorting |
| Entries Per Page | entry_list_limit |
| Record Shortcode Log Template | record_module_log_template |
| Enable Creating New Entries | allow_frontend_add |
| Enable Editing Entries | allow_frontend_edit |
| Enable Deleting Entries | allow_frontend_delete |
| Allow Log Export | allow_export |
| Allow Log Import | allow_import |
| “Slide In” Entry Controls | hide_entry_controls |
| Highlight Color | highlight_color |
| Single Shortcode Log Template | single_module_log_template |
How can I show a customized sum of values for the log list?
Each log has a “summary display” that can be used to show a simple sum from the log data. If you want to show a sum that is specific to your application, such as a sum that is conditional, or a sum that involves multiple entry fields, you need some custom code for that.
In technical terms, the code you need is a filter handler that takes the normal value that would be displayed and changes it ro a custom calculated value. This is best added as a custom plugin or you can put it into your theme functions.php file.
The filter hook is pdblog-{$logname}_sum where {$logname} is the slug name of the log field. You’ll see that on the manage database fields page where the log field is defined.
The filter gets two arguments: the configured sum value (in other words, what the sum would show if you didn’t change it) and the second argument is an array of the record’s log values. You can calculate your sum from the values in that array, and then the filter handler should return your new sum, which will be displayed with the log as configured in the log’s settings for the summary display.
There is a simple example here: https://gist.github.com/xnau/fb961393fc675cf802a509a2a1c888d1
Is it possible to provide a link to the editable record in the Global Log List?
The Global Log List shortcode will show a filtered list of entries from all records for a particular log. Each line in the list is an individual entry from a record’s log. It is possible to place a link to the editable record in this list so that the log entry can be edited. This requires the use of a custom template.
Be sure to control access to this list display, you will be giving edit access to your records when you use it.
To use this custom template, you must first create a “placeholder” field in the main Participants Database plugin. You can also re-use an existing placeholder field if you want. Below is a link to the custom template. You must modify it to use the placeholder field you set up.
Is it possible to delete log entries that are no longer connected to a PDB record?
As of version 1.5.9, when a Participants Database record is deleted, the entries belonging to that record are deleted also.
If records were deleted prior to that version, or if records were deleted not using the “with selected” delete method on the List Participants admin page, you can end up with entries that no longer have a parent record.
There is a utility function you can use to clear these out. To do that go to the Participant Log admin page. Add &pdblog-delete-orphan-entries=log_name to the URL and hit return. This will clear out all the entries that are not connected to a PDB record. For example, if your log is named “automobiles” you can clear out the orphan entries from that log with a URL like this:
When creating a field for a new log, I get this error message: “Failed to create table for this log. You need to use a different name for your log.”
The message you’re seeing means that the table needed to create the log could not be created for some reason. The part about trying a different name is just the most likely reason for the failure.
What I suggest you do is start over: on the Manage Database Fields page, delete the log field. It will be a field of type “Participant Log” Once the log field has been deleted, go to the Participant Database settings under the Advanced tab and turn plugin debugging on to “all errors”. Once that’s enabled, open the Debugging Log page and clear the log.
Now, recreate the log: go back to the Participant Log settings page and create a new log. Try using a very simple name for the log at first…you can always change the display name of the log later, but when you’re first creating it it’s a good idea to use something simple. Once you’ve created the new log field, go back to the Participant Log settings and under the tab for the new log, create your first field for the log. If you get the error message again, check the debugging log.
If you can’t create the log field because of the error, post a question to tech support on this page.
Be sure to turn plugin debugging off again once you get things set up and working.
Is it possible to select a custom template for the single/record shortcode logs?
Thanks
There are no custom templates for the log displays. The “responsive” and “grid” templates provide a huge amount of flexibility…given the knowledge of how to use CSS to format it.
Is there something specific you needed in that template?
I am wanting to move the field title but if it’s designed to be all done in css that’s fine.
Thanks
You can drag the field to re-order them in the log’s field configuration.
The order’s fine, it’s the location of the elements, ie moving the log name above the log to save space while still maintaining a table style log. I’ll play with the css.
Thanks
Has the text-line field type disappeared from logs? There only appears to be text-area when making a new field.
Thanks
thanks for letting me know about that, I just posted an update to Participant Log that fixes this.
Hi Roland,
I currently have 8 Logs in the PDB. I have just tried to add another one, but won’t work. Is there a limit to the number of Logs?
In the Participants Log page I type the name of the log, click “+Create Log”, it goes to the Manage Database Fields page as usual, but then the New Field Form Element type is Text-line, not Participant Log (and this is not in the list). If I click Add Field, it just adds a text field and no log is created. I don’t see any errors in the PDB debugging log.
I am using the latest versions of PDB and Log.
Updated to 1.6.3 today and when adding a new log entry it opens an existing log from a different record. Presumably a bug.
Thanks
Try reloading the page…this could be page caching providing a record from a previously loaded page.
I don’t think it’s that, happening on several different computers, and is pulling up logs that are years old.
Yes, I’m not talking about a browser cache, this is some kind of cache on your server or website, so you’d see it on any computer or browser. I just don’t see how this could happen otherwise unless the database was altered.
Hmm, there are no cache plugins on the site (I have just installed one in order to do a purge, but no change) and I have 2 sites running pdb logs on the same server. One is 1.6.2 and works fine, the other updated to 1.6.3 today and had the problem. No other changes to the sites or the server, as far as I am aware.
Is there any way to roll back to 1.6.2 to test?
Thanks
OK, well, I will need to check on how that release may have introduced a problem. I’m sorry about the inconvenience.
Email me at support@xnau.com and I’ll send you the previous version.
Thanks for letting me know about that, I made a mistake in the last update to Participant Log, I’ll issue a fix today.
Hi Roland,
I am creating a customized sum summary for the one of my logs and I successfully adapted/modified your pdb-custom_summary.php example. However, this replaces the original sum tag with my custom sum class/function leading to the loss of the original simple sum, which I still need. From the prior posts, you mention to add you own tags using filter “pdblog-summary_tags”. I studied the PD Log source code but I am stuck in creating a new tag that I would like to call in Sum Display Template form and apply both tags, [sum] and my own version. Do I use add_filter(‘pdblog-summary_tags’… or apply_filters(pdblog-summary_tags’…, how do I complete these statements? My intent is to add one of these to the constructor for my custom sum summary class. Any pointers would be much appreciated! Thank you.
You would use apply_filters on the pdblog-summary_tags filter to modify (or add to) the list of tags that are available to the summary template. You can retain your original value (which will be in the [sum] tag) by adding a new tag with your custom sum. You actually don’t need the pdblog-{$log_name}_sum filter in that case, you’re just using the pdblog-summary_tags filter to add your new value to the list of tags, and then using that new tag in the summary template.
Thank you Roland! This makes sense, however I have attempted the following and I am not able to register (new) or modify any tags. My custom sum summary class/php file has the following constructor:
public function __construct()
{
apply_filters( ‘pdblog-summary_tags’, array(‘[sum]’ => 1.1, ‘[sum2]’ => 2.2,));
}
I modified the [sum] tag and created a new tag [sum2] and assigned fixed values to both for testing. The summary sums are unaffected or just display the tag [sum2] in the log’s summary output. Any pointers are very appreciated, thank you again! Martin
Martin, you need to read up on how to use WordPress filters, the way you’re doing it won’t work.
Martin, I’m looking at the pdblog-summary_tags filter and I see I didn’t make it very easy to use if you have multiple logs since the same filter will run for all logs. If you have multiple logs, you can detect which one it is by looking at the value of the [name_singular] tag, but that is not great. I do plan to issue an update to the Participant Log add-on that adds a log name argument to the filter to make this easier to use.
Hi Roland,
When I upload an image to my ‘files’ Log, it gets saved in wp-content/uploads/participants-database/files but the link provided in the list output is missing the ‘files’ directory, so I get a ‘page not found’ error. How can I resolve this?
Many thanks
Can you be more specific about where you see this issue? I’m not seeing the problem yet, so I want to make sure I’m looking in the right place. Are you using the Image Expansion Kit add-on?
Using your code template (modified)
add_action( ‘pdb-form_element_build_dropdown’, ‘set_APnames_dropdown_options’);
/**
* sets the options for the new name dropdown
*
* @param PDb_FormElement object $field the current field
*/
function set_APnames_dropdown_options ( $field )
I dump $options just before $field->options = $options;
And echo from the function gives the correct $options
/Users/Craig/www/devspk/wp-content/plugins/ap_names_dropdown/pdb-names-dropdown.php:100:
array (size=448)
0 => string ‘ID:972, isset:true, type: string’ (length=32)
1 => string ‘(1-1) [no name]’ (length=15)
2 => string ‘(4-2) [no name]’ (length=15)
3 => string ‘(5-3) [no name]’ (length=15)
4 => string ‘(6-429) [no name]’ (length=17)
the drop down in the log form is correct except for the first one
‘ID:972, isset:true, type: string’
which becomes
‘ID:, isset:true, type: string’
Why is the ID not showing?
Further to my post today:
i can get the id within the function with
$thisid = Participants_Db::get_record_id();
echo $thisid gives me the correct id but when i include this in the $newoptions array it resolves as 0 in the drop down.
So the id does not display in the drop down – i think this is the source of my problem
Hard to tell from your description, if it echoes the correct it, but then it doesn’t appear in the options, have you checked that you are successfully setting the options? Your previous question suggests that is not working. Hard to say with custom code, it could be anything because I am not looking at it and I don’t know your skill level.
Thanks for the quick reply.
The code (partial) is below. (in 2 posts as i am getting too long message
When you echo $id_value after $id_value = Participants_Db::get_record_id();
id is correct
But in the popup form for the log record the drop id = 0.
code snippet 1
add_action( ‘pdb-form_element_build_dropdown’, ‘set_APnames_dropdown_options’); function set_APnames_dropdown_options ( $field ) { if ( $field->name === ‘adverse_event_link_to_affected_person’) { global $wpdb; // grab the db helper object if ( $field->is_multi( $field->form_element ) && isset( $field->value[‘other’] ) ) { $field->value = array_merge( (array) $field->value, explode(‘,’, $field->value[‘other’] ) ); } // Get record id – doesn’t work… as $this not in object context //$ap_record_id = $this->list_anchor $query = ‘ SELECT record_id, id, persons_affected_name, persons_affected_relationship FROM’ . $wpdb->prefix . ‘participants_database_persons_affected
OK, I wasn’t actually offering to debug your code, that can’t really be done in a comment thread anyway.
I am just now realizing that your dropdown element is in a participant log entry, so things will be different, but since I haven’t attempted this, I can’t go into detail. It may require a different method altogether. Bear in mind that in that context there is both the entry ID and the record ID. If it is a new entry, the entry ID will be 0 because it hasn’t been saved yet, and so there is no entry ID yet.
“Get record id – doesn’t work… as $this not in object context” You cannot use “$this” in your function, you’re not in a class context.
Have used your pdb-form_element_build_dropdown to build a drop down.
When i get to the end of the form i have populated the $newoptions array.
1. I var_dump it and it is correct.
2. i update – $field->options = $newoptions;
3. i var dump $field->options – it is correct.
ie. public ‘options’ =>
array (size=3)
0 => string ‘(972-test’ (length=9)
1 => string ‘(972-410) Grant Jenkins (Husband)’ (length=33)
2 => string ‘(972-448) Craig Blackxxxx (Distant contact)’ (length=43)
public ‘attributes’ =>
But then the associated drop down list only displays ‘(972-test.
Appreciate your help?
I don’t see anything wrong there, have you looked at the HTML that was generated? Could be some kind of syntax error in the HTML.
Also, what is the “options” value for the field before you attempt to alter it?
Hi Roland,
Is it possible to get a count of records in the log list for each distinct field value.
The following SQL displays what I need:
SELECT
, COUNT(*)
FROM
GROUP BY
, COUNT(*)
FROM
, COUNT(*)
FROM
GROUP BY
GROUP BY
, COUNT(*)
FROM
GROUP BY
To give:
------------------------
| broken arm | 4 |
| headache | 10 |
| fatigue | 2 |
------------------------
The plugin doesn’t have a built-in way to do this for multiple values. You will need to use some custom code for that, there are several ways to do it. One way is to modify the “sum” display with something that displays multiple values, like you have there. There is a filter “pdblog-summary_tags” that you can use to define your own tags, which you would then use in the summary template for the log.