Forum Activity for @brian

jrElastic 2.0.8 profile_index.tpl

Using Jamroom

This is fixed - the marketplace uploader should have caught that, so I am checking that out.

Thanks!

Profile Tweaks Module Connection

Jamroom Developers

It should be automatic - just check your profile_index.tpl file and make sure you're not doing something in there that overrides it.

Creating Open Graph tags with Meta Tag Manager in JR

Using Jamroom

We've not removed any functionality from the meta tag manager that I am aware of. I'll need more clarification on what the "tip" is before I can comment - I really don't know what you mean.

Note that $variables in meta tags are only available on profile pages - that's how it has always been (not sure if that is what you are talking about or not).

MySQL error after updating Jamroom

Jamroom Developers


I have no idea without spending time debugging it on your system. There is no other report from any site of this happening, so unfortunately I cannot tell you what it is.

Creating Open Graph tags with Meta Tag Manager in JR

Using Jamroom

A variable can only be replaced with a value if the core knows what it is - if you add $var to a meta tag, how are you getting the data into the tag so it can be replaced?

Something off with pagination

Jamroom Developers

I believe we have a fix for this in Core 6.1.8 thanks to Michael

Oauth2 request from listener

Jamroom Developers

You can do anything you want in a listener - you can request the token via a request, then turn around and make another request. There's no restrictions on what you can do in a listener.

User Privacy Controls - More important now than ever

Suggestions


This is content related - not really Jamroom. It's up to you to police the site content on your site.

Creating Open Graph tags with Meta Tag Manager in JR

Using Jamroom


I am not sure what you mean here - all JR templates can use $variables.

Something off with pagination

Jamroom Developers

This is actually expected behavior when using "simplepagebreak".

Mountaintop has posted exactly 50 topics. With simplepagebreak being used (instead of the normal pagebreak due to the size of the datastore and the "Use Optimized Pager" setting enabled in the Core), there is no "total" SQL query that is run to determine the total number of posts. The counting SQL query used with the regular pagebreak is the slowest part of the function, so we exclude that when using simplepagebreak and just assume that if we can fill an entire page to it's simplepagebreak number, then we always show the "next page" link. In this case if Mountaintop had 49 or 51 posts this would not be an issue, but since he is right at 50 we show the "next page" link even though there is no next page.

This is an acceptable side effect for % of time you run into it versus the every-request drastic performance improvement you get from not running the counting query.
updated by @brian: 05/28/18 08:37:19AM