Forum Activity for @michael

Treating content after a certain number of page views

Using Jamroom

are the og:tags setup on your site? if they are post the link to the site under the screenshot, get the full link card to the page there inviting them.

Why would I signup to your site? What benefit do I get that I wouldn't get if I wasn't signed up?

Need to figure out a reason people would want to signup.
* "Signup to get the latest updates"
* "Signup to help us build this site"
....?

Adding sharethis to pages.

Design and Skin Customization

That process is described in detail on the docs page:

Docs: "ShareThis"
https://www.jamroom.net/the-jamroom-network/documentation/modules/2598/sharethis

If there are questions beyond this that you would like added to the docs, let me know and we can get them added.

Adding another folder in skin directory

Design and Skin Customization

Thats not going to work. If im understanding correctly you have
/skins/jrAudioPro/

and your adding extra .tpl files to
/skins/jrAudioPro/custom/fileone.tpl
/skins/jrAudioPro/custom/filetwo.tpl
/skins/jrAudioPro/custom/filethree.tpl

and you're wanting them to show up at:
yoursite.com/fileone
yoursite.com/filetwo
yoursite.com/filethree

... wont work.

Before making changes to a skin, you should be cloining it to xxAudioPro or other name
/skins/xxAudioPro

so your changes dont get lost when updates come in.

I can understand the concept, wanting to just add in over-rides for the skin. We talked about a similar idea a while back where a skin could be a sub-skin of an existing skin.

eg:
/skins/jrAudioPro/(all the files)

then have a sub-skin of that
/skins/xxAudioProSubSkin/index.tpl

Where if the sub skin had a .tpl that matched the one in the master, and the sub skin was active, then the subskins version would be used.

The idea has been put in the backburner as it seams like a developer feature that would be used very rarely.

You may be able to use a folder in an include.
NORMAL:
TRY:

Adding sharethis to pages.

Design and Skin Customization

You're expecting that someone visiting your site is going to be impressed by the title of a video and share it before they have viewed it? Sound very hopeful. Have you ever shared a video before you have watched it? I haven't.

The audio and video list pages are found at:
ACP -> MODULES -> PROFILE -> AUDIO -> TEMPLATES -> item_list.tpl -> MODIFY
ACP -> MODULES -> PROFILE -> VIDEO -> TEMPLATES -> item_list.tpl -> MODIFY

You can put the share code in there. Remember to reset the cache.
ACP -> MODULES -> CORE -> SYSTEM CORE -> TOOLS -> RESET CACHE

Audio is not streaming

Using Jamroom

GUESS: May have been the caching system keeping it working. If it couldn't update it would just keep showing what it had.

Well done for figuring it out.

Ninja Skin Upgrades

Design and Skin Customization

If you were using the ACP templates tabs, then do it how @strumelia suggested.

Ninja Skin Upgrades

Design and Skin Customization


Yes. Once you clone a skin, any updates that come in to the original skin will need to be ported to your clone if you want to have those changes.

One point: Any changes that come in to MODULES templates that have-not been over-ridden by the skin will be automatically available to you.

So if in your skin you ARE over-riding a modules template, eg, you have a file called /skins/YOUR-SKIN/jrAudio_item_detail.tpl. then if changes come in to that module's template (/modules/jrAudio/templates/item_detail.tpl), they will need to be ported to your over-ride version if you want them.


You are using a setup similar to how I would do it, working in the file system with version control and an IDE. So I would do it like this:

* new changes come in to your system via the MARKETPLACE update system.

You want to see what has changed between this version of the original skin and the last version of the original skin, but in the file system they are in different directories, eg:
/skins/jrMediaPro
/skins/jrMediaPro-version-1.0.1
/skins/jrMediaPro-version-1.0.2

This structure doesn't work well with a revision control system because version-1.0.1 and version-1.0.2 are treated as completely different files.

If you run the REBASE MODULE tool found at:
ACP -> MODULES -> DEVELOPER -> TOOLS -> REBASE MODULES

you can stack all the revisions onto the base name directory, so version-1.0.1 and version-1.0.2 directories will disappear and you will just have:
/skins/jrMediaPro

So I would do it like this:
* use the rebase tool to remove all the versions
* sync my IDE with the server
* commit all the changes to the version control so there are no local changes present
* run the MARKETPLACE system update tool to get the new versions of the skins
* re-run the rebase tool to put the new version onto the base directory name
* sync my IDE with the server

What you should have now in your "Local Changes" panel is just the files that have changed. you can use the compare tool built in to your revision system to see exactly what has changed. Then port those to your skin if you want them.

Power User's "default" Profile

Jamroom Developers

Yes, in the jr_jruser_item_key table there is a _profile_id field. This is the 'home' (default) profile of that user.

Audio is not streaming

Using Jamroom

how did you figure out that that was the problem?

When updating my account details, as regular user, I am forced to reset my password

Using Jamroom

The setting you're seeing is this one:
http://YOUR - SITE.com/user/admin/global/section=account+settings/hl=authenticate


Admin should not be prompted, but others should be.

If you think there is a bug somewhere, outline the steps and I'll check it out.