Front page activity feed broken after update
Design and Skin Customization
paul:We do our best
That is such an understatement!
Forum Activity for @ultrajam
Design and Skin Customization
That is such an understatement!
Tag Creation @ item create/update form
Suggestions
iLoveHouseMusic:
I think it would be more intuitive to allow tagging from the item owner and admins. It just seems more "normal".
I think it would be more intuitive to allow tagging from the item owner and admins. It just seems more "normal".
Tags are user generated navigation. The idea is generally that you crowdsource your navigation and allow the crowd to make prominent the items/profiles/pages that are important to them. Take a look at how tagging works on the major services.
If you just need the owner and admins to do that, use multiple category fields.
Quote: What's "funky" to me might not be "funky" to someone else.
That's the idea of tags. You don't get to define what is funky, the crowd does, and the crowd may have a different opinion to you.
updated by @ultrajam: 03/17/14 10:48:47AM
Player on custom skin broken after update
Design and Skin Customization
It is something to do with the embed.
The problem occurs when using this for the embed (loaded via ajax, embed and main player work on initial load)
{$proj_summary|jrCore_format_string:$profile_quota_id:"embed"}{$proj_summary|jrCore_format_string:$profile_quota_id:null:"embed"}listening/notification question
Using Jamroom
Example:
This makes the form:
function view_jrBlog_update($_post, $_user, $_conf)This does the save:
function view_jrBlog_update_save($_post, &$_user, &$_conf)You'd probably want to do the checks after validation:
$_sv = jrCore_form_get_save_data('jrBlog', 'update', $_post);And send the notification at the same time as adding to actions:
// Add to Actions...
jrCore_run_module_function('jrAction_save', 'update', 'jrBlog', $_post['id']);Player on custom skin broken after update
Design and Skin Customization
I have a site with a customised Nova skin where the audio player shows on all profile pages.
{assign var="ap" value="`$_conf.jrCore_active_skin`_auto_play"}
{jrCore_media_player type="jrAudio_blue_monday" module="jrAudio" field="audio_file" search="_profile_id = `$_profile_id`" autoplay=$_conf.$ap assign="profile_player"}I've just updated core and modules, and the player now no longer works on some pages, it shows a text list as in the screenshot.
Surprisingly, the player breaks when I load another div with ajax, although the player is not part of the load. No console errors.
It appears to be related to having jrEmbed audio in the loaded div.
{$proj_summary|jrCore_format_string:$profile_quota_id:"embed"}It works when that loaded content is loaded, then breaks when other content is loaded, then fixes itself again when relaoding the content with the embed. It was fully working on versions from about 2 weeks ago.
If there is no embed in the loaded content, everything works fine.
Has anyone else encountered this? Any idea where to look to fix it?
Thanks
updated by @ultrajam: 05/04/14 11:34:26PM
listening/notification question
Using Jamroom
If the module has a form save function, check the box field in that, and send notification if the field value is "on"
Setup
LifeStreams
Glad that its working for you!
Thanks for letting me know about youtube.
It looks like you are using a facebook user account in your lifestream settings rather than a Facebook Page, which is why no entries are showing from fb on your profile. Only Pages (or Fan Pages) return the feed data, so try with a Facebook Page such as "jamroomdotnet"
Setup
LifeStreams
If there is nothing after the copyright notice in footer.tpl, where are your /body and /html closing tags? They appear in footer.tpl for all of the jamroom skins I have seen.
Compare your footer to jrElastic and check that you have all the necessary code. You should have at least this after the copyright notice:
{if isset($css_footer_href)}
{foreach from=$css_footer_href item="_css"}
<link rel="stylesheet" href="{$_css.source}" media="{$_css.media|default:"screen"}" />
{/foreach}
{/if}
{if isset($javascript_footer_href)}
{foreach from=$javascript_footer_href item="_js"}
<script type="{$_js.type|default:"text/javascript"}" src="{$_js.source}"></script>
{/foreach}
{/if}
{if isset($javascript_footer_function)}
<script type="text/javascript">
{$javascript_footer_function}
</script>
{/if}
{* do not remove this hidden div *}
<div id="jr_temp_work_div" style="display:none"></div>
</body>
</html>
updated by @ultrajam: 03/16/14 07:14:52AM
Tag search doc result labelled as "documentation"
Suggestions
I noticed that when clicking through the tag cloud to results documentation isn't labelled as such. It's clear when using search as it appears under the Documentation heading, but on tag search it is easy to miss:
updated by @ultrajam: 04/20/14 12:27:03PM
Setup
LifeStreams
That code won't be causing a problem - its used in all skins.
Look in your footer.tpl as that's the most likely place to find your error
