sadhaka

Hi, sorry for my delay in replying, but that doesn’t work. Now I remember that I tried that before, but it still doesn’t work.

Thanks. (That should be an option IMHO)

Yes the gallery plugin must be reloading after page load as you say. I can’t see any available configuration in that plugin to alter that, but I’ll ask the developer. Thanks for clarifying.

Hm OK. Well I’m not getting anywhere!

The short code is always like:

[justified_image_grid gallery=1361]

..and rendered HTML (for each gallery element) is always like:

<div class="jig-caption-title">My Caption</div>

… but no filter seems to work! Never mind!

Hm OK. Well as far as I can see the caption is nested divs until it gets to:

<div class="jig-caption-title">My Caption</div>

Ah sorry I thought you might have had experience of this one.

When you say “give it a go”, do you mean the free or the paid-for version?

I did try the free version, and it didn’t do it out of the box (as I didn’t expect), but I don’t really understand what might be the extra implementation or configuration involved.

As far as I can tell, the expanded short code content is just regular HTML (a div with a class, etc)—though maybe that’s not what you meant.

“May require filtering” — I’m guessing this means some extra function for the child theme to extend the plugin’s scope?

Thanks – but as far as I can see, there is no longer a way to detect just iPads anymore. I think I’ve tried every which way.

I even tried at https://demo.mobiledetect.net and even there it always fails to detect just iPads.

If you know of another way, do let me know!

• This reply was modified 2 years, 7 months ago by sadhaka.

It’s working very well, thanks.

But is there a way to target “mobile phones” generally (i.e., phones, not tablets)? Unless, with the plugin, wp_is_mobile covers that ?

Edit: I’m answering my own question here, but I guess this does it (tell me if I’m wrong):

function custom_is_phone() {
$IsPhone = false;
$detectPlatform = new TinyWP_Mobile_Detect;
if ($detectPlatform->isMobile()) {
$IsPhone = true;
} else {
$IsPhone = false;
}
}

Then using like:

if ($IsPhone) {
//whatever..
}

• This reply was modified 2 years, 7 months ago by sadhaka.

Many thanks @yordansoares for your helpful suggestion.

The plugin documentation seems somewhat lacking if such extras are commonly required. My hosting is a very large and well-known company.

But I’ll try out your suggested “fix”.

I was on the point of using this when I read this review. But I don’t understand this. The free version is touted as having “invisible spam protection“. So how come you’re getting so much spam anyway?

And if there really is no way with the free version to select multiple entries to delete them (trivial coding), then that really does sound like a deliberate bait to purchase a “pro” version that has that simple function.

Unfortunately the widgets placed in the sidebar (replacing the blog sidebar) are not responsive, as they displace the width on portrait mobile, so I have to restrict them to desktops only.

I found the problem. It was my template – I had inadvertently called wp_head() twice.

It had nothing to do with your excellent plugin – sorry to have troubled you.

If this gives you any clue, in the source of the “offending” template (when it has been the result of a search, and the query string has been duly appended, such as ?hilite=zebra), the content of the script is basically repeated, so it looks like:

<script id='hlst-extend-js-after'>
    /* Highlight Search Terms 1.6.1 ( RavanH - https://status301.net/wordpress-plugins/highlight-search-terms/ ) */
    const hlst = function() {
        window.hilite(["zebra"], ["#groups-dir-list", "#members-dir-list", "div.bbp-topic-content,div.bbp-reply-content,li.bbp-forum-info,.bbp-topic-title,.bbp-reply-title", "article", "div.hentry", "div.post", "div.wp-block-query", "#content", "#main", "div.content", "#middle", "#container", "div.container", "div.page", "#wrapper", "body"], true, true)
    };
    window.addEventListener('DOMContentLoaded', hlst);
    window.addEventListener('post-load', hlst);
    /* Highlight Search Terms 1.6.1 ( RavanH - https://status301.net/wordpress-plugins/highlight-search-terms/ ) */
    const hlst = function() {
        window.hilite(["zebra"], ["#groups-dir-list", "#members-dir-list", "div.bbp-topic-content,div.bbp-reply-content,li.bbp-forum-info,.bbp-topic-title,.bbp-reply-title", "article", "div.hentry", "div.post", "div.wp-block-query", "#content", "#main", "div.content", "#middle", "#container", "div.container", "div.page", "#wrapper", "body"], true, true)
    };
    window.addEventListener('DOMContentLoaded', hlst);
    window.addEventListener('post-load', hlst);
    </script>

So the function gets called twice and the same variable gets declared twice.

But maybe you realised all that.

I can’t think why the function should be repeated like that.

I don’t think so. There’s only one instance of <footer [etc]> in the source.

Ah excellent. I should have taken a look at your plugin before asking the question!

I take it that you’ve simply included Mobile_Detect.php and then added the conditional in your plugin script for wp_is_mobile to return true if isMobile() && !isTablet(), otherwise to return false.

So this means that, simply by having your plugin installed, I have all the other methods available to me in Mobile_Detect.php ? I was a bit confused about that because I wasn’t sure how WordPress derives its wp_is_mobile in the first place.