Forum Activity for @blindmime

jrAparna module

Using Jamroom


No, updates don't really affect my process any more than if I override the template in the skin folder. You override it either way don't you? (I update module templates via the ACP, incidentally).

I'm still trying to understand the issue with Aparna, however. Or rather the thought behind disabling it because new skins are overriding aspects of the module-based template system. Is this an indication that Jamroom will be changing its approach to modules? Seems like we reached this point in the battle between skin and profile in Jamroom history back in the day.

jrAparna module

Using Jamroom

Well I'll be. I've always just changed the template in the module folder. So doing it as outlined above makes aparna-generated modules behave badly?

Gallery Photos showing as placeholder photos

Using Jamroom

Anywhere there is a list of items in gallery, audio, etc. I'll send you a login as a follower, along with a link via a support ticket.

jrAparna module

Using Jamroom

What is a template override?

Gallery Photos showing as placeholder photos

Using Jamroom

All the images are displayed when logged in as admin. What causes placeholders to display and how can I fix this?

jrAparna module

Using Jamroom

I'm curious to understand how Aparna is not compliant with the way Jamroom now works. I'm not questioning the statement or anything. I just don't understand it. Aparna works OK with how I personally work with Jamroom. But it wouldn't be the first time I'm doing things completely the wrong way.

jrAparna module

Using Jamroom


Is there currently a simple method to create a basic barebones module starting point that is compliant with the way jamroom now works?

max_allowed_packet

Using Jamroom

I have a jr site over on arvixe. After updating to 6.1 the system check shows the attached. So I had them increase the max_allowed_packet to 32M, but it's still showing red and 16M. I notice on the left it says max_query_size -- is this actually a different setting?

updated by @blindmime: 05/21/18 09:56:17PM

Elastic 2 Footer Issue

Design and Skin Customization

Another thing to think about, of course, is that each social network forms their URL's differently. For instance, if I just entered my LinkedIn user name in the Elastic 2 form I will get an error, since the URL is https://www.linkedin.com/in/username.

Also with your solution, the title will produce something like: "Like www.youtube.com/channel/UCexere_fdfdaeeerfddfd on Youtube". Maybe {$_conf.jrCore_system_name} would work better in the title tag? Although, some people will enter a SEO value for that which might not really work here either. Might be the better solution overall, however.

Elastic 2 Footer Issue

Design and Skin Customization

I get it. In the second point, I'm just saying it could be done more clearly. What you're asking for is not really a URL. You're asking for a user or profile name. So why not put that in the form?

I realize it's not really a big deal and most of us figure it out and work around it. Just saying you might consider fine tuning things there.
updated by @blindmime: 01/20/18 07:04:02AM