Still Unable to upgrade
Using Jamroom
I've had a chance to try this code in Ningja and got absolutely nowhere with it. All that showed up is some plain text words.
Forum Activity for @ken-rich
Still Unable to upgrade
Using Jamroom
Hi Douglas,
I'm still using the old Nova skin but I can't use Nova at all now (either version) - this functionality has to be transferred to my Ningja skin in order to upgrade to Sitebuilder 2.
So how do I make that work in Ningja? Pretend for a minute that basic HTML is challenging for me and Javascript is like absolute Greek.
All I know is my current working code looks like:
{* FEATURED TABS *}
<br><div class="row">
<div class="col12 last">
{if jrCore_is_mobile_device()}<div class="menu_tab">
<div id="default" class="p_choice fartist" onclick="jrLoad('#sm','{$jamroom_url}/index_artists');jrSetActive('#default');">{jrCore_lang skin=$_conf.jrCore_active_skin id="21" default="featured"} {jrCore_lang skin=$_conf.jrCore_active_skin id="12" default="artists"}</div>
<div id="s_song" class="p_choice fsong" onclick="jrLoad('#sm','{$jamroom_url}/index_songs');jrSetActive('#s_song');">Songs</div>
<div id="s_video" class="p_choice fvideo" onclick="jrLoad('#sm','{$jamroom_url}/index_videos');jrSetActive('#s_video');">Videos</div>
<div class="clear"></div>
</div>{else}
<div class="menu_tab">
<div id="default" class="p_choice fartist" onclick="jrLoad('#sm','{$jamroom_url}/index_artists');jrSetActive('#default');">{jrCore_lang skin=$_conf.jrCore_active_skin id="21" default="featured"} {jrCore_lang skin=$_conf.jrCore_active_skin id="12" default="artists"}</div>
<div id="s_song" class="p_choice fsong" onclick="jrLoad('#sm','{$jamroom_url}/index_songs');jrSetActive('#s_song');">{jrCore_lang skin=$_conf.jrCore_active_skin id="21" default="featured"} {jrCore_lang skin=$_conf.jrCore_active_skin id="13" default="songs"}</div>
<div id="s_soundcloud" class="p_choice fsoundcloud" onclick="jrLoad('#sm','{$jamroom_url}/index_soundclouds');jrSetActive('#s_soundcloud');">{jrCore_lang skin=$_conf.jrCore_active_skin id="21" default="featured"} {jrCore_lang skin=$_conf.jrCore_active_skin id="61" default="Soundcloud"}</div>
<div id="s_video" class="p_choice fvideo" onclick="jrLoad('#sm','{$jamroom_url}/index_videos');jrSetActive('#s_video');">{jrCore_lang skin=$_conf.jrCore_active_skin id="21" default="featured"} {jrCore_lang skin=$_conf.jrCore_active_skin id="14" default="videos"}</div>
<div id="s_youtube" class="p_choice fyoutube" onclick="jrLoad('#sm','{$jamroom_url}/index_youtubes');jrSetActive('#s_youtube');">{jrCore_lang skin=$_conf.jrCore_active_skin id="21" default="featured"} {jrCore_lang skin=$_conf.jrCore_active_skin id="62" default="youtube"}</div>
<div id="s_vimeo" class="p_choice fvimeo" onclick="jrLoad('#sm','{$jamroom_url}/index_vimeos');jrSetActive('#s_vimeo');">{jrCore_lang skin=$_conf.jrCore_active_skin id="21" default="featured"} {jrCore_lang skin=$_conf.jrCore_active_skin id="63" default="vimeo"}</div>
<div class="clear"></div>
</div>{/if}
<div class="inner mb8">
<div id="sm"></div>
</div>
</div>
</div>
What exactly must that look like in Ningja? Keep in mind I have already got each form of content being featured in Ningja, by a two step process.
I copied the Nova index_XXXXX_row.tpl files into Ningja like this (video example).
{if isset($_items)}
<div class="container">
<div class="row">
{foreach from=$_items item="item"}
<div class="col3{if $row@last} last{/if}">
<div class="p5" style="text-align:center;">
<a href="{$jamroom_url}/{$item.profile_url}/{$_params.module_url}/{$item._item_id}/{$item.video_title_url}">{jrCore_module_function function="jrImage_display" module="jrVideo" type="video_image" item_id=$item._item_id size="medium" crop="auto" alt=$item.video_title title=$item.video_title class="iloutline img_shadow"}</a><br>
<div style="width:196px;margin:0 auto;">
<table>
<tr>
<td class="media_title capital" style="text-align:center;">
<a href="{$jamroom_url}/{$item.profile_url}/{$_params.module_url}/{$item._item_id}/{$item.video_title_url}" title="{$item.video_title}">{$item.video_title|truncate:25:"...":false}</a><br>
<span class="normal"><a href="{$jamroom_url}/{$item.profile_url}" title="{$item.profile_name}">{$item.profile_name|truncate:20:"...":false}</a></span>
</td>
</tr>
</table>
</div>
</div>
</div>
{/foreach}
</div>
</div>
{/if} On content index pages, I then added this code to get my paid quotas only to feature, thus creating paid advertising. A very handy innovation useful in selling subscriptions and funding the network. Again video example:
<h1>Featured</h1>
<br><br>
{jrCore_list module="jrVideo" order_by="video_title random" quota_id="6,7" limit="4" template="index_videos_row.tpl" require_image="video_image"}
<br><br> So the building blocks already exist in my Ningja clone, I just don't have a clue (even with what you have written) how to write the code for the multi-tab version in Ningja.
Are you telling me just that little code snippet you gave above will do the trick? Or is that calling on some heavier code in the Java library that exists in Nova, but does not currently exist in Ningja?
With what you see I have done in my code examples, what EXACTLY do I paste into Ningja to get it's front page to show the multitab widget and is that the only thing i have to do? Are div references and so on for CSS a problem here as well?
updated by @ken-rich: 11/30/15 10:23:18AM
Still Unable to upgrade
Using Jamroom
Hi Gary,
Found it - https://www.jamroom.net/the-jamroom-network/forum/ning-to-jamroom/16613/featuring-can-be-better-than-ning#last
That thread explains the issue and how to resolve it but it turned out to be too advanced for me to understand or implement.
It's what Douglas wrote toward the bottom that is relevant.
updated by @ken-rich: 11/30/15 06:30:19AM
Still Unable to upgrade
Using Jamroom
Hi Gary,
That is the section I am talking about. I can get those tabs to show but I can't get them to "load" properly because of some type of reset issue which I believe is in Ajax or Java.
So if I show the featured members and then click another tab like featured songs it doesn't re initialize properly. It is only taking the page load (not tab clicks) as initialize - if you get where I am coming from. It's been a while since I attempted, but that is the issue if I recall.
Now over on this page it works perfectly http://indiegospel.net but it has the Nova clone as active.
I've also got all the individual elements working in a Ningja clone there, for example on top of the songs page at http://indiegospel.net/uploaded_audio there are 4 featured songs from the paid quotas - so automatic paid advertising.
To do this I had to put a piece of code into all the content categories of Ningja from Nova.
I just couldn't solve the multi-tab issue on the front page.
If you want to experiment, I can give you admin status on my demo site - it costs me nothing extra for modules and skins, since I am in Jamroom hosting. Besides which I paid for both of those skins before Jamroom hosting became available.
In fact Douglas (Jamroom) tried to tell me how to do it before (in a forum post if I can find it) but I had no clue how to implement - too advanced for me.
updated by @ken-rich: 11/30/15 05:56:32AM
Still Unable to upgrade
Using Jamroom
Hi Michael,
http://democo.jamroomhosting.com/categories now has the right style. It's not from the active skin, it's from the Ningja clone in the profiles and admin sections.
Admin skin 1.2.7 is installed and Sitebuilder 1 with Menus 1.0.11 Widgets 1.0.14 Panels 1.0.15
Skins are the xxTerminator 2 and xxNetwork 2 that incorporate your mods, with the addition of my CSS via table entries.
From here, if I upgrade to Sitebuilder 2 (changing nothing else), I see the issue where sitebuilder pages start taking the active skin, rather than the one I prefer. If I revert the problem disappears.
This indicates to me that the issue has something to do with the difference between Sitebuilder 1 and 2, rather than the skins or the Admin Skin module. Although the CSS I put in through the tables might be part of the issue too.
updated by @ken-rich: 11/30/15 05:44:21AM
Still Unable to upgrade
Using Jamroom
I'm on the right track now. I reverted a bunch of stuff to earlier versions and got the desired outcome. I have to bring them back to current one at a time to isolate what causes the issue.
Code Mirror Breaks on Mapped Profiles Domains
General
Hi Steve,
The mail system isn't set up there. I just approved you.
Yes I had that install done properly on my "real site" and the code mirror worked everywhere except for the comment boxes in mapped domains.
I haven't tried it in the demo site but I just gave you master admin status there. I'm running experiments on the skins, sitebuilder, and admin skin module - so things may get a bit "screwy" at times.
Let me know if that interferes and I'll let you play around by yourself in there.
Still Unable to upgrade
Using Jamroom
Hi Gary,
Sorry but I do not have the java and CSS skills for that. I spent many days at it before and couldn't even find a way to float my radio and logo on top of the page.
I have a featuring system as well in the Nova that shows 4 members, 4 songs, 4 videos, etc. all from the paid subscriber quota only, but I can't get it to work in Ningja. Something about how it resets with ajax or java. I have members who pay to be in that.
The rest I could handle but not those two issues.
Still Unable to upgrade
Using Jamroom
If it looks a little off on the demo site now it's because I'm running more experiments reverting to earlier versions and such.
I've noticed if I take the sitebuilder code out of the header menu template in version one - the buttons are gone, in version 2 they still show which tells me you are putting them their by a different method.
Maybe java slider or something I don't understand.
updated by @ken-rich: 11/28/15 08:51:44AM
Still Unable to upgrade
Using Jamroom
I just ran another experiment. On the demo site I overwrote the admin skin module's include file with an earlier version but it made no difference. Original is now put back.
So neither the admin skin version, skin versions, or sitebuilder version seem to be causing the difference in skin styles between the demo and real site.
