Forum Activity for @brian

brian
@brian
04/04/19 01:17:31PM
10,148 posts

GEDCOM Will Not Import


Genosis

Thanks for posting the GEDCOM file - I will check it out and see if I can spot what's up. I see it's only 1.4mb - I have no idea why it shows "5 Gigs" - that's not right.

Thanks!
brian
@brian
04/04/19 07:43:22AM
10,148 posts

NVME Bump



We use Linode for all our VM servers and I believe they have been on NVMe for some time now - definitely fast!
brian
@brian
04/04/19 07:42:39AM
10,148 posts

Deleted server



gary.moncrieff:
Hey guys I deleted my server as I have no plans to redo my site anytime soon or if at all. Lost all interest in web development currently.

Hey Gary - sorry to hear that! I go through periods of up and down when my interests move on to something else. As a long time developer I always end up coming back to development, but fresh air and a change of scenery can be awesome :)

Good luck with whatever you are up to :)
brian
@brian
03/25/19 11:49:34AM
10,148 posts

Two Questions About Documentation Module


Using Jamroom

Ceri:
Did anyone get a chance to look in to this yet?

I tested this and don't see any issue - make sure and place:

{jrProfile_disable_module_tabs}

At the top of the doc_section_header.tpl file.

Let me know if that helps.
brian
@brian
03/17/19 01:39:51PM
10,148 posts

Mobile post editor problem


Using Jamroom

lornawebber:
Is it possible to default to the normal comment editor, instead of the small-screen editor, when on mobile devices? Is there an option for that?

No - the "normal" editor has never been enabled on mobile devices. Previous to Jamroom 6.1.6 (when the mobile editor was first introduced) mobile devices would see just a simple textarea - no editor. The problem with that is that if you created a post on a desktop (for example) and then came back later to edit it on a mobile device, then you would just see the raw HTML in the texraea. This of course caused issues. With Jamroom Core 6.1.6 the TinyMCE editor (which Jamroom uses) included a new beta mobile editor, and that is what has been enabled since then.

I'm not sure if it will function on the mobile device but if you want to FORCE all devices to use the standard editor (which again is NOT made for mobile devices and is not likely to look right) you can edit the "form_editor.tpl" file in the System Core module (templates tab) and remove these lines (13 - 15):

    {if jrCore_is_mobile_device() && !jrCore_is_tablet_device()}
    mobile: { theme: 'mobile' },
    {/if}

Save, click the enabled checkbox and reset caches.

I'm not 100% sure that will force the "normal" editor on mobile phones, but that is how it is controlled. I would be prepared for the regular editor to have significant size issues on mobile phones, however, so I would make sure and test that thoroughly.
brian
@brian
03/17/19 01:04:17PM
10,148 posts

BUG - Profile Avatar Looks Terrible


Using Jamroom

Re-reading my follow up here, and I didn't really post any possible "solutions" - sorry about that.

1) The easiest would be to simply upload a larger version of the profile image for that profile
2) You could customize your profile page and add a template conditional where if the image width (or height) is UNDER a certain size, then simply show it smaller (maybe center it, etc). The only issue with this approach is that your profiles may not have a uniform appearance.

I also will add that Google+ is going "out of business" and I would not be surprised at all that they are no longer offering hi-res versions of images for social signup - they probably turned those off as a way to save bandwidth and money.
brian
@brian
03/17/19 12:22:09PM
10,148 posts

site no longer sending important emails (beta issue?)


Using Jamroom

Those are not emails being sent - that's a remote site trying to connect to your SMTP server for "relaying" and being denied. I am not familiar with how your email is setup, so that's something you will need to contact your hosting provider to assist with - it's not really something we're going to assist with here in the forum.

Thanks!
brian
@brian
03/17/19 12:20:40PM
10,148 posts

BUG - Profile Avatar Looks Terrible


Using Jamroom

SoftDesigns:
@Strumelia - Thanks, but the user did not upload the image, it was pulled from their Google SignIn (OneAll), and incorrectly enlarged automatically by JR platform.

This is really frustrating to read. Jamroom did not "incorrectly enlarge" the image. The fact that you say that indicates you don't understand what is happening here. Jamroom cannot enlarge a 50x50 pixel image to 512x512 - it WILL be pixelated.

Quote:
--
@brian - You said above:
Quote: The ORIGINAL image is horrible:
--
Please do not blame the end user for JR code issues that do not occur in other platforms that also use Google SignIn.

Please look at the image again. that image is what Google+ gave to Jamroom - we don't have control over it. When a user signs up using OneAll, OneAll will give us different size URLs to download the user's avatar -we always try to use the highest resolution one FIRST and work our way down if the higher res ones are unavailable. We have users sign up here on Jamroom.net all the time and the image that gets associated with their account is whatever the remote network gives us.

So there is no bug here and nothing for us to do or change.

Quote:
The JamRoom OneAll module integration code should be "tighter" , and check the size of the avatar image, and if it is too small, do not try to enlarge a tiny image.

Again, this just shows you're not understanding how Jamroom images work. Jamroom doesn't "enlarge" anything. If it only has a 50x50 pixel image to work with, then any "size" requested over 50x50 will look pixelated - Jamroom cannot create more pixels than there are.

So the image URL YOU are using in your template is:

https://softart.club/cv/image/profile_image/181/xxlarge/_v=1cdc61552754398

Do you see the "xxlarge" part? You are telling Jamroom to create a NEW image 512x512 in size, and to use the 50x50 as the SOURCE image (since that is all we have). No wonder it is pixelated!

I'm going to mark this post "solved" since this is not a Jamroom issue. I know you won't like that but I'm not sure how else to explain it. If you continue to find this to be a problem, then Jamroom may not be the right platform for you to use since there really is no other way to handle low-res images.

Thanks!
brian
@brian
03/17/19 09:01:10AM
10,148 posts

Mobile post editor problem


Using Jamroom

lornawebber:
@brian thanks for the explanation - that's what I thought.
The problem I have is that embedded images don't seem to be re-sizable by dragging in the corners, when commenting on a mobile device. It may be a caching issue - the image appears to be reduced in size when a corner is dragged in, but it still shows in the large size when the comment is posted. I'll test a bit further including clearing caches, and let you know if it works or not.

I'm not seeing any ability to "drag by corners". Note that the image insert functionality is part of the editor - that's not something Jamroom inserts or controls, so we don't have control over the size. Would it be better to simply remove the ability to attach an image?
brian
@brian
03/17/19 08:59:44AM
10,148 posts

site no longer sending important emails (beta issue?)


Using Jamroom

You should see "sent" messages in your mail.log - i.e. here's an example from jamroom.net:

Mar 17 15:57:39 jamroom postfix/smtp[6701]: B99B4111F5: to=(removed), relay=smtp.mailgun.org:25, delay=0.83, delays=0/0/0.39/0.44, dsn=2.0.0, status=sent (250 Great success)
  35