Forum Activity for @michael

A - Z Artist / Profiles page - Audio Pro

Design and Skin Customization

Sorry, thought you were on our hosting. Its all-access to all the modules/skins we make so looking at it wouldn't involve purchasing anything. Just keep going with your existing structure, its working.

Video and audio uploads not converting

Using Jamroom

The underlying linux system does not matter so much, as long as it meets the server requirements:

Docs: "Server Requirements"
https://www.jamroom.net/the-jamroom-network/documentation/getting-started/774/server-requirements

so it could run on a correctly set up Cent OS7

--edit--
Whats going to be of more of a concern for you is will they help you setup the VPS. Because a lot of the time the cheaper VPS servers are 'unmanaged' which means as long as the server is online then their job is done, its up to you to take care of running the server. The more expensive version is a 'managed VPS' where if something goes wrong you can ask them to fix it.

Jamroom hosting is managed hosting: https://www.jamroom.net/hosting
updated by @michael: 05/10/20 06:17:45PM

Image watermarks

Using Jamroom

Its a setting that is not turned on by default.
ACP -> MODULES -> IMAGE SUPPORT -> QUOTA CONFIG -> WATERMARK

Uncheck the "Watermark Images" checkbox.

Video Upload Form Gone

Using Jamroom

The message reads "This video file is currently being processed and will appear here once complete".

So it could still be processing. Check the queues to see if there is anything there:
ACP -> DASHBOARD -> QUEUE VIEWER

if thats clear, then check the error log and activity logs for any more info.
ACP -> DASHBOARD -> ACTIVITY LOG
ACP -> DASHBOARD -> ERROR LOG

A - Z Artist / Profiles page - Audio Pro

Design and Skin Customization


instead of 'profile_name' if you search on 'profile_url' that will not contain any weird characters.


'profile_url' is the profiles name converted to characters that are valid in a url, so "Crosby, Stills & Nash" would be converted to "crosby-stills-nash"

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