If it’s a broadly-applicable meeting type, please ask us in the discussions forum. We must maintain consistency for the mobile apps, so not all proposals are accepted.
If you have access to your theme’s functions.php, you may add additional meeting types or rename existing ones. Simply adapt the following example to your purposes:
Please note a few things about custom types:
It depends on your Permalinks setup. The easiest way to find the link is to go to the Dashboard > Meetings > Import & Export page and look for it under “Where’s My Info?”
We get our geocoding positions from Google (this true even if your maps are by Mapbox). Google is correct an amazing amount of the time, but not always. If you need to add a custom location, add this to your theme’s functions.php.
Note you can add multiple entries to the array below.
Yes, you can add, update, or remove these descriptions. Adapt this example as needed and add it to your theme’s functions.php. Using an empty string '' will unset the type.
Change Detection augments our data import utility by periodically polling your data sources and generating email notifications to Change Notification Email recipients who you registered on the Settings page.
Change Detection can only be enabled when adding a data source to your list of Data Sources. Re-registering an existing data source is necessary to get Change Detection enabled. This includes:
* To be safe, always make a backup of your existing meeting list by using the link on the Import tab to export your Meeting List.
* If you are going to have change detection on multple data sources, you may choose to add the parent organization(s) to your list of Regions first (i.e. District 1, YourCity Intergroup, etc.).
* Remove the data source (click on the X next to its Last Refresh timestamp) We suggest first noting the json feed URL (hover over the feed name to view the URL) for use when adding it back.
* Set data source options: enter a name for your feed, set the feed URL, select the parent region from the Parent Region dropdown, and lastly choose the “Change Detection Enabled” option.
* Pressing the “Add Data Source” button will register a WordPress Cron Job (tsml_scan_data_source) for the newly added and enabled data source. By default, this cron job is scheduled to run “Once Daily” starting at midnight (12:00 AM).
The frequency and time that the cron job runs is optionally configurable with the [WP Crontrol[(https://wordpress.org/plugins/wp-crontrol/)] plugin.
When editing a data source record a warning is given that the record will be over-written when the data source is refreshed.
To avoid this warning and prevent a refresh from altering an edited record it’s necessary to follow a few simple steps to reimport the data source records:
Your meeting list records will now no longer display a warning message when being edited, and will not be overwritten by a data source refresh operation!
Add this CSS to your theme:
The easiest way is to link to that view straight from your navigation. Usually that looks like /meetings/?tsml-day=any, but it can vary depending on your settings.
If you’d prefer to keep the default address, you could add this code to your theme’s functions.php instead:
Add this to your theme’s functions.php. The value should be an existing value, ie 1, 5, 10, 25 or 50.
Add this to your theme’s functions.php.
Add a URL to your theme’s functions.php.
You can add variables to the URL that can be picked up by a form plugin:
Feel free to adjust as necessary. This can also be a new email URL, such as:
Add this to your theme’s functions.php. Feel free to change the order or column names (eg ‘Region’) but keep the keys the same (eg ‘region’).
Add this to your theme’s functions.php.
By default, the plugin sorts by day, then time, then location name. To set your own sort index, add this to your functions.php:
By default this plugin uses the Streets theme, v9. To change this, add this to your functions.php:
Please note the version of the Mapbox script we use doesn’t support all the themes displayed on the Mapbox site. The themes which have been tested and are known to work are: mapbox://styles/mapbox/streets-v9, mapbox://styles/mapbox/outdoors-v9, mapbox://styles/mapbox/light-v9, mapbox://styles/mapbox/dark-v9, mapbox://styles/mapbox/satellite-v9, and mapbox://styles/mapbox/satellite-streets-v9.
If you are using the “Legacy UI” appearance, copy the files from the plugin’s templates directory into your theme’s root directory. If you’re using a theme from the Theme Directory, you may be better off creating a Child Theme. Now, you may override those pages. The archive-meetings.php file controls the meeting list page, single-meetings.php controls the meetings detail, and single-locations.php controls the location detail.
If you are using TSML UI, then adding local CSS is the best way to customize the appearance of the meeting finder.
Please note these pages will evolve over time. If you override, you will someday experience website errors after an update. If that happens, please update your theme’s copy of the plugin pages.
To see types in the meeting list, one way to do it is to add some CSS to your theme which will make a types column visible.
One drawback of this approach is that it shows all the meeting types, and you might not want all of them to be displayed over and over in the meeting list.
Another approach is to adjust which meeting types are “flagged” in the meeting names, by default for most programs this is /Men and /Women. To adjust this, find the meeting type code for each type you want to show and include it in your theme’s functions.php like this:
The code above will add “Open” and “Closed” flags to the meeting name.
If you don’t mind some PHP programming, then yes! Create a function called tsml_import_reformat, and use it to
reformat your incoming data to the standard format
You can make use of the gettext filter to override the plugin’s translation strings. For example, if you wanted to replace ‘Region’ with ‘City,’ you could add the following to your functions.php file.
Save it as a draft by editing the meeting’s Status.
Yes, you can use [tsml_meeting_count], [tsml_location_count], [tsml_group_count], and [tsml_region_count] to display human-formatted counts of your entities. For example, “Our area currently comprises [tsml_meeting_count] meetings.”
Use [tsml_types_list] and [tsml_regions_list] to output linked lists to your meeting finder.
Use [tsml_ui] to display the TSML UI meeting finder. Optionally you may pass parameters, for example: [tsml_ui weekday="sunday" type="women,closed"]
It is translated into Polish. If you would like to volunteer to help translate another language, we would be pleased to work with you.
That’s right, we don’t display that information by default for the sake of anonymity. To display it in your theme, go to Meetings > Settings and set the Meeting/Group Contacts dropdown to “public.”
Sure. Try adding this code to your theme’s functions.php:
Also check out our One Page Meeting List theme.
Yes, but you will need to enter an approximate location. To do this simply enter the city and state or province of the general geographic location of the meeting into the address field.
Yes, try setting the $tsml_slug variable in your functions.php.
You may set it to false to hide the public meeting finder altogether.
To apply these changes, you must go to Settings > Permalinks and click “Save Changes”
Yes, you can use the following filter to change the with_front configuration from true to false
Yes, add the following to your theme’s functions.php. Make sure you’ve enabled the Geocoding API in the Google Cloud Console.
To report a security issue, please use the Security Tab on our GitHub repo,
located under the repository name. If you cannot see the “Security” tab, select the … dropdown menu, and then click Security.
Please include as much information as possible, including steps to help our team recreate the issue.
Yes, you will need to know the key name of the field. Then include an array in your theme’s function.php file:
