Forum Activity for @michael

Remove link

Design and Skin Customization

nothing, the place you want to update is index_core_blog_list.tpl

which is in a /module/ directory, so dont touch it because it would be over-written with the next update.

What you want to do is OVER-RIDE that by copying it to your skin and renaming it to jrCore_index_core_blog_list.tpl

Do that and the version in your skin will over-ride the modules version, then any changes you make will be safe through any future updates.

Docs: "Altering a modules template"
https://www.jamroom.net/the-jamroom-network/documentation/module-developer-guide/1051/altering-a-modules-template

Premium Install Issue

Jamroom Hosting

type the domain name you want in here:
https://www.jamroom.net/bigrussian/hosting/server_settings/568

and it should all be setup for you.

Account Problems

Using Jamroom

I've deleted your attachment. It has your key in it.

You have a space in front of your email address so its not valid. Probably from copy+pasting it.

My site just stopped being accessible

Installation and Configuration

Contact your hosting company and ask them to enable it.

My site just stopped being accessible

Installation and Configuration

What was happening right before this?

Were you doing any upgrades? Uploading anything? Changing server settings?

Something has changed that will be related to the issue.

Related: "Fatal error: Call to undefined function ctype_digit()"
https://stackoverflow.com/questions/51167297/fatal-error-call-to-undefined-function-ctype-digit

Firefox home page issue

Using Jamroom

http://www.dubmusic.com/
and
http://dubmusic.com/

are not the same place. Your site is on the WWW version. If you access it via the non WWW version your javascript stops working because its not the same domain.

Best idea is to redirect to the WWW version.

stream pay

Installation and Configuration

In that case what you'd have to do is setup some way to get the money from the viewer to you (The site owner). Then you, as the site owner could pay that out to the owners of the music that has been played/listened to.

The stream pay module is the second part of that equation.

So if you setup a system where users of your site could view 100 videos per month if they paid $20/month then that would provide the money to pay your artists. You could then set the per stream payout to $0.20.

Then set the view limit on the quota to 100/month. And you have your system.

Only users who pay the $20 per month will be able to login and listen to music. Artists will get paid when their music is played.

Facebook API advice gives me the heebie-jeebies

Using Jamroom

You can pretty much ignore it. You needed to agree to get the key, so they send you the messages. But its the module that does the connecting, and even then its OneAll that takes care of the connection.

Years ago we tried to make native connection scripts but got so sick of having to update it just to keep it running everytime facebook or other decided to change it, this time we found OneAll who handle that part for us.

So as long as the connection between your Jamroom site and Oneall is working (which has been pretty stable for many years) then they will take care of the connection necessities to facebook at their end. Thankfully.

stream pay

Installation and Configuration

Stream Pay:
* You install the module on your site.
* You want (me/someone) to upload videos to your site, so you offer to pay (me/someone) 1cent per stream, or whatever.
* I upload the a video.
* 10 other people come to your site to watch my video, you pay me for every time they watch.

What it is not:
* you upload your video to your site
* I come and watch that video
* you get paid.

stream pay

Installation and Configuration

The docs are here:

Docs: "Stream Pay"
https://www.jamroom.net/the-jamroom-network/documentation/modules/3587/stream-pay

What part is unclear? or where did you get up to when the docs stopped being helpful? Thanks.