• Hi,

    We have a problem with the blog post archive at our site.

    If you for example see and want to look at the blog category: Amningsrum (2) nothing shows up.. It is like this when doing this as a visitor. When we are logged in as admin it works as it should and we can see the two blogs post from the blog category: Amningsrum (2).

    We have been in contact with several persons, among others the support of our theme – X PRO from Themeco – trying to figure out what is wrong. We have made and changed several settings in Breeze trying to find a solution and at the same time maintaining the good speed, but unfortunately without success.

    Now the support from Themeco wrote the below and I am now asking for your help with this issue, if possible. Hope! Kind regards, Johanna
    ——
    I see that it’s working when you’re logged in and not when logged out. That happens maybe because your caching / performance plugin does not cache and minify resources when you’re logged in.

    The blog masonry script which is in VIEWS/GLOBAL/_SCRIPT-ISOTOPE-INDEX.PHP (not in the JS files listed previously) requires jQuery to be loaded in the head because it is loaded in the body part. Because of your optimization (grouping and minification), jQuery (combined and minified along with other JS) now is loaded at the very bottom of the page.

    Please load the jQuery in the head and see if the issue persists. You might need to contact the caching / performance developer for this.

    Also note that this is not an issue with X, though there is a performance benefit loading all JS in the footer, generally, it is not feasible because some jQuery functionality is needed to be used in the body. That is true not only for X but for many other plugins as well.

    • This topic was modified 6 years, 6 months ago by Wilja.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Wilja

    (@wilja)

    Hi again,

    We found the blog masonry script in the file: VIEWS/GLOBAL/_SCRIPT-ISOTOPE-INDEX.PHP?. See below. Could this help in anyway, according to what we have written – that we got from our team developer – earlier, i.e.

    The blog masonry script which is in VIEWS/GLOBAL/_SCRIPT-ISOTOPE-INDEX.PHP (not in the JS files listed previously) requires jQuery to be loaded in the head because it is loaded in the body part. Because of your optimization (grouping and minification), jQuery (combined and minified along with other JS) now is loaded at the very bottom of the page.

    Please load the jQuery in the head and see if the issue persists. You might need to contact the caching / performance developer for this.

    Kind regards,
    Johanna

    <?php

    // =============================================================================
    // VIEWS/GLOBAL/_SCRIPT-ISOTOPE-INDEX.PHP
    // —————————————————————————–
    // Isotope script call for index output.
    // =============================================================================

    $is_rtl = is_rtl();

    ?>

    <script>

    jQuery(document).ready(function($) {

    <?php if ( $is_rtl ) : ?>

    $.xIsotope.prototype._positionAbs = function( x, y ) {
    return { right: x, top: y };
    };

    <?php endif; ?>

    var $container = $(‘#x-iso-container’);

    $container.before(‘<span id=”x-isotope-loading”><span>’);

    $(window).on(‘load’, function() {
    $container.xIsotope({
    itemSelector : ‘.x-iso-container > .hentry’,
    resizable : true,
    filter : ‘*’,
    <?php if ( $is_rtl ) : ?>
    transformsEnabled : false,
    <?php endif; ?>
    containerStyle : {
    overflow : ‘hidden’,
    position : ‘relative’
    }
    });
    $(‘#x-isotope-loading’).stop(true,true).fadeOut(300);
    $(‘#x-iso-container > .hentry’).each(function(i) {
    $(this).delay(i * 150).animate({‘opacity’ : 1}, 500, ‘xEaseOutQuad’);
    });
    });

    $(window).xsmartresize(function() {
    $container.xIsotope({ });
    });

    });

    </script>

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    @adeelkhan Your account is on moderation watch, you’ve been doing something very bad here for a while.

    I’ve deleted your offer to login to your user’s site. I’m am 100% sure you mean well but please never ask for credentials on these forums.

    https://www.ads-software.com/support/guidelines/#the-bad-stuff

    Now for the why: The internet is a wonderful place full of very nice people and a few very bad ones. I’m sure everyone here is very nice however, by giving some ones keys to your house you are trusting they wont steal anything. Likewise the person who takes the keys is now responsible for the house FOREVER.

    If something was to go wrong, then you the author may well legally become liable for damages, which they would not normally have been as their software is provided without warranty.

    Please be aware that repeatedly asking for credentials will result in us asking you to repeatedly stop before escalating up to the plugins team.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    @wilja I’m closing this topic. The author made a mistake and posting your login, letting the author log into your site is AMAZING unsafe. The author is now on watch for that, that’s going too far.

    Please do not repeat that with anyone.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Problem with blog post archive’ is closed to new replies.