Forum Activity for @michael

A - Z Artist / Profiles page - Audio Pro

Design and Skin Customization

The MediaPro skin has the feature your after in it, you can use it for a guide:
http://demo.jamroom.net/jrMediaPro/music

So look in the /skins/jrMediaPro/music.tpl template.

A - Z Artist / Profiles page - Audio Pro

Design and Skin Customization

Make a template in your cloned skin:
/skins/(YOUR-SKIN)/archives.tpl

make it by copying the header and footer structure of the index.tpl template to get the upper and lower sections.

something like:

Then put your jrCore_list call in the middle.

It will be something like I outlined above


This template is a bare minimum type structure to just get a jrCore_list call of some profiles, no searching, just anything

From there customize the jrCore_list. This jrCore_list call gets "any profile beginning with the letter 'a' "

If that is coming out correctly, then adjust it to receive the variable:

Then call the url:
yoursite.com/archives/letter=a

and see if the same thing comes out, if it does, try the other letters to
yoursite.com/archives/letter=a
yoursite.com/archives/letter=b
yoursite.com/archives/letter=c
yoursite.com/archives/letter=d
.......

If they all work, then setup some navigation

Running with development mode on will mean you dont need to reset your caches each time:
ACP -> MODULES -> DEVELOPER -> DEVELOPER TOOLS -> GLOBAL CONFIG -> Run in developer mode

A - Z Artist / Profiles page - Audio Pro

Design and Skin Customization

Ask the second question in its own thread, easier to explain one topic at a time.

The tool you're looking for is jrCore_list:

Docs: {jrCore_list}
https://www.jamroom.net/the-jamroom-network/documentation/module-developer-guide/89/jrcore-list

Its the swiss army knife of getting data from the database, so if you want something beginning with 'A' you'd have a url like:
site.com/some_template_name/a
or
site.com/some_template_name/letter=a

The difference in the two is what comes into the template in the $_post variable. on the second one you KNOW that $_post['letter'] is the variable you're looking for. for the first one, you'll need to look for 'A' using {debug} to find out what variable it comes in on, its probably {$_post['module']}.

Once you have the variable, you pass that to jrCore_list to get what you want.

Alternate use for platform

Genosis

There is no look-up functionality in Genosis script. You can import GEDCOM files, but it does not connect to any external database to pull in data. Unless you want it to, and then you'd need to build that module.

Audio Pro - Form Builder

Design and Skin Customization

First off, if your site is only ever going to be in english, you dont need to use the language feature, that will make it simpler.

so instead of:
you can just use:

It really depends on how you like to work. The language strings are there for users who want to be able to customize the site without the need to look at code. If you're comfortable looking at code the best workflow (the one I like) is to keep out of the ACP for all skin customizations. There is an over-ride system for working with templates that allows you to adjust at the coding level.

From the question im making the assumption you're using the TEMPLATES tab to make your changes. The other way to do it is to clone your skin, then make adjustments via SFTP. Which you prefer depends on you comfort level with code.

For web developers the preferred workflow (the one I like) is:
* clone the skin from jrAudioPro to xxAudioProCustom (or any name you choose)
* download xxAudioProCustom into your development environment (I use phpstorm)
* adjust the xxAudioProCustom/profile_sidebar.tpl and upload it back to the site
* (either) run the site in "Developer Mode" so the caches are off, (OR) reset the caches to see your changes.
(repeat)

back to the question:
1. you will need to find out what the correct variable is that holds the quota id, for that adding {debug} to the templates will get you a list of what variables are available in each template, see these docs for more info:
Docs: {debug}
https://www.jamroom.net/the-jamroom-network/documentation/module-developer-guide/1477/debug

it will probably be something like:

2. add your new form field to the "Additional search fields" section of the ACP then rebuild the search index:
https://www.jamroom.net/the-jamroom-network/documentation/modules/950/search#rebuild-the-search-index

3. check it for string length

Alternate use for platform

Genosis

Jamroom is designed to be customizable. Genosis is a set of extra modules and a custom skin built on top of jamroom so its customizable too.

The biggest issue you will have will be learning how the platform works because there is a learning curve. In order to do it you will need to look at code.

As with anything there is a trade-off. If we try to make things easier for non-developers to do, then things get more complex for developers. Jamroom comes from being a system for developers and the non-developer stuff is added on as extras, so if you're coming from the perspective of using it as a development tool integrated in a web developers work flow then its just a question of getting things arranged how you want them.

If the question comes from a "Can I change some settings and have this work?" perspective then im not sure, maybe.

How to test as a user while in maintenance ?

Using Jamroom

not a regular user, no. Probably what you're after is the jrBeta module that will allow you to take the site off maintanence mode but block signups and also allow login from beta testers

--edit--
Docs: Beta Launch Page
https://www.jamroom.net/the-jamroom-network/documentation/modules/2953/beta-launch-page
updated by @michael: 05/04/20 05:56:54AM

Audio Pro - Form Builder

Design and Skin Customization

Are you talking about "Simple Custom Forms"
https://www.jamroom.net/the-jamroom-network/documentation/modules/2885/simple-custom-forms

or the "Form Designer"
https://www.jamroom.net/the-jamroom-network/documentation/jamroom-admin-handbook/1275/using-the-form-designer

Its my guess that you're talking about adding extra values to modules using the Form Designer, if its that, then the designer is just the first part. Its the location that the information is collected and put into the database.

From there to get the information to show you need to get it out of the database, that's the job of the skins. Skins format the information from the database in whatever structure you want.

So if you went into the audio module's custom form designer and added a text area to collect "Composer" and saved it to audio_composer then in the skin templates where you see all the other variables like {$item.audio_title} then you could use {$item.audio_composer} and the value entered would show.

Picking up some errors

Installation and Configuration

Try running the INTEGRITY CHECK to fix the play_key error, go to:
ACP -> CORE -> SYSTEM CORE -> TOOLS -> INTEGRITY CHECK
check all the checkboxes, then START.

That should make sure any tables that need creating are created.

The second one is just a warning, its saying that for some reason the process that fires every minute couldnt complete on one particular minute. But thats ok, because the process that fires the next minute will pick up any left over tasks that were queued and do them.

Unable to FTP your software to my hosting

Using Jamroom

I don't understand what you mean by "It wont launch".