Forum Activity for @ken-rich

Ken Rich
@ken-rich
11/26/15 11:07:14AM
926 posts

Mailgun Issue
Installation and Configuration

I just tried to send a broadcast and got cut-off at 300 recipients with a message that I need to verify my domain.

I haven't had problems like this since it's been set-up ages ago, so I am wondering if something in the latest rounds of updates wiped out something on the Jamroom side of things relating to verification?
updated by @ken-rich: 02/25/16 02:03:44PM
Ken Rich
@ken-rich
11/26/15 04:24:53AM
926 posts

Still Unable to upgrade
Using Jamroom

Hi Michael,

I just had a real quick look because I'm way behind on something else right now. I didn't see "switching" but it's still showing the wrong skin on sitebuilder pages.

It just occurred to me that this may be because my demo and real site have the site builder installed differently.

Not just different version numbers, but I think that perhaps on the real site I may not have sitebuilder installed in the Active section (Nova Clone Skin there) but I do in the Ningja clone, used in profile and admin sections.

It might be this section of code needs looking at, and it's placement in which skins, so that it is consistent between the real and demo sites.

{* Site Builder *}
            {if jrCore_module_is_active('jrPanel') && jrCore_module_is_active('jrMenu') && jrCore_module_is_active('jrWidget')}

                {jrMenu_display active=$menu_url}

            {else}


                {if jrCore_module_is_active('jrSiteBuilder')}

                    {* User menu entries *}
                    {jrSiteBuilder_menu}

I don't have time to confirm right now, but I'm thinking this may be why sitebuilder pages have different styles between the sites and it's confusing us???????
Ken Rich
@ken-rich
11/25/15 12:24:43PM
926 posts

Still Unable to upgrade
Using Jamroom

Hi Michael,

I think (not 100% sure) I am following you. I have seen that sort of skin switching behavior on the demo site.

I also saw my notes temporarily grab the wrong skin once on my "real" network, but only after the latest round of updates, which included the Ningja clone skin in the Profiles and Admin sections.

However, I have never PREVIOUSLY seen any such issues on my "real" network. So when you say there will be a problem if you "revert" to the old way, I'm not so sure.

I could be in a profile and add a page (or song, or whatever), or I can be in a profile styled "sitebuilder page" and go to add a new sitebuilder page, and the result is always another profile styled page.

So whatever way you were coding things until recently, seems to work. I don't know why, but it doesn't produce the condition you seem to think will occur if you revert ("On profile, click + to add something, skin changes.").

I can only report what I see, I'm not sure why it's not what you expect.
Ken Rich
@ken-rich
11/25/15 11:53:11AM
926 posts

Code Mirror Breaks on Mapped Profiles Domains
General

Sorry it was removed sitewide over the issue.

The mapped domains are subscribed accounts on my network, so I can't really in good conscience turn on something I know is broken for paying clients.

You are welcome to play around on my demo network though, sky is the limit there. It's in Jamroom hosting and adding modules doesn't cost me anything extra.

http://democo.jamroomhosting.com/
Ken Rich
@ken-rich
11/25/15 12:05:53AM
926 posts

Still Unable to upgrade
Using Jamroom

Hi Michael,

Yes - kind of.

If you look at this page http://democo.jamroomhosting.com/categories you can see it is taking the Nova clone style from the active skin (Terminator 2)

Here is the same page on my "real" site and it's taking the Ninja clone style (Network skin) from the Admin/Profile sections http://indiegospel.net/categories

That is the thing I am not understanding - why is that? It's the same page, different style.

I imported it into my demo while it was set to Sitebuilder version 1, then upgraded to version 2.

I don't know if it's the mods you did to the skins there, or the difference in sitebuilder versions, or perhaps some other thing, which is causing it to switch to a different style.

Until I can account for what is causing that difference in style, I don't feel safe to upgrade the real site. I don't want those pages to switch styles like that.

The front page should continue to be the only one with that Nova clone (Terminator 2) style, just as my real site currently operates right now.
Ken Rich
@ken-rich
11/24/15 05:48:27PM
926 posts

Still Unable to upgrade
Using Jamroom

Hi Brian,

What I have done is pretty simple really, and done with what Jamroom provided.

I installed the admin skin module, put a Nova clone in the active section, and a Ningja clone in the admin and profile section.

I installed Sitebuilder 1 into both those skins.

I am able to create pages with the Ningja clone's style, even though it is not the active skin.

It seems to work like Michael suggested:

(is this a profile page?) = Show the 'profile' skin.
(is this an ACP page?) = Show the 'admin' skin.
(otherwise) = Show the 'active' skin.

My problem is that the new demo site I made, which has similar skins and sitebuilder 2 doesn't seem to work that way, which makes me scared to try an upgrade on my main site.
Ken Rich
@ken-rich
11/24/15 02:45:31PM
926 posts

Code Mirror Breaks on Mapped Profiles Domains
General

Howdy,

Comment boxes on mapped profile domains lose the ability to post code at all when Code Mirror is active.

Brian confirmed it was the source of the issue, which I experienced it on my site, until I disabled Code mirror.

I really like that module and what it does, so I'm hoping you will go the extra mile and get it working cross domains.

Thanks for your innovations.
Ken Rich
@ken-rich
11/24/15 11:39:06AM
926 posts

Still Unable to upgrade
Using Jamroom

Hi Brian,

It doesn't work that way on my live, working network - http://indiegopspel.net

Style wise, the front page is a Nova clone and everything else on the network, INCLUDING all my sitebuilder pages, are Ningja clones.

If they SHOULD be otherwise, then there must be a reason why they are not. I don't understand what that reason is, I'm just saying that it literally doesn't work that way on my site.

I'm also saying that I want it to continue working the current (wrong) way, or I will be forced to get rid of my front page.

I've never been able to even come close to duplicating it's functionality or aesthetics in Ningja (after considerable effort), so that's not a good option for me.
Ken Rich
@ken-rich
11/23/15 07:24:26PM
926 posts

Still Unable to upgrade
Using Jamroom

That's the way I would expect it to work, and the way it does work on my "real" site with Sitebuilder 1.

Sitebuilder2 on the demo site seems to make active skin pages only. That's what I'm not understanding.

The only place I really need the Nova clone skin is the front page, everywhere else I prefer the Ningja clone skin, especially with pages made from sitebuilder.
Ken Rich
@ken-rich
11/23/15 02:32:20PM
926 posts

Still Unable to upgrade
Using Jamroom

Hi Michael,

Your CSS adjustment worked in the Nova clone (Terminator) skin.

I'll try the store module settings when I get a chance.

To see this behavior just go here - http://indiegospel.net/store

That site is running the same skins as the demo. Modified Nova in the active section, but modified Ningja in the profiles and admin sections.

As you can see, the style is from the profile and admin section, not the front end. That's what I am trying to achieve. If it worked that way before, why not again?

My theory is that I installed Sitebuilder manually in those skins, in the early part of development, when you posted the method (which I have since forgotten). I seem to recall that, but not how to repeat.

I don't know if that's a valid premise or not, as to why it works the opposite of the way you say it should? I just know I need to get it working that way again in version 2.

What I am saying is that I need the pages I make to take the Ningja clone style used in admin and profiles section, not the Nova clone style used on the fromt end.

Sitebuilder 1 works that way on my current working site. The demo doesn't and I don't understand why or how to change.
updated by @ken-rich: 11/23/15 02:35:30PM
  22