This is a good tool for finding out which templates construct a page "Template name in source"
Docs: "Developer tools -> Template Name in Source"https://www.jamroom.net/the-jamroom-network/documentation/modules/932/developer-tools#template-name-in-source
In truth I don't use that very often though. What I do is grab a distinctive looking class from one of the elements on the page and run that through the search function in my IDE to locate the templates. If that fails then I'd use the above tool to figure out the template.
jrCore_list is the swiss army knife of getting anything from a datastore out to a template:
Jamroom has 2 types of data storage systems, a regular mysql 'table' and a 'datastore'.
A datastore is a KEY -> VALUE storage system that allows you not to have to define a table structure. Most modules use a datastore for their items.
Careful though, if you're making alterations to jrAudioPro then if it gets updates and you upgrade all your adjustments will be lost.
What happens when a skin gets upgraded is the existing skin gets moved to a version directory jrAudio-version-1.2.3 and the new update gets put in its place.
In order to avoid that clone the skin to its own name so there will be no updates to over-write your changes.
updated by @michael: 16 Jul 2020 10:30:53PM