Gantry

Hi,

Sorry for late reply. Well we won’t be able to solve it the way we should because like I mentioned it would require rewriting tons of MooTools code.

However I just removed MooTools and (not fully working) QTags (text editor mode) RokSprocket button from the post/page edit screen. This allows me to not load MooTools on that page which fixes the issue with YOAST.

MooTools still is required both by Gantry 4 and RokSprocket in the Widgets page, where YOAST loads its scripts too. So until you use the G4 Gizmo I mentioned previously, you still gonna see JS error there. I’m not sure why YOAST loads its JS on every admin page but as I stated before – it’s not a very good idea.

If you guys are interested I can send you a snapshot build of RokSprocket so you could test it. I’ve also passed it to our mods for internal testing.

Thanks

We use MooTools in our theme admin screen, widgets page (overrides dropdown, gantry divider etc.) and post/page edit screens (but only if you use the RokSprocket or RokGallery – shortcode generator). The only compromise I can see right now without rewriting whole JS is to disable the RokSprocket and RokGallery shortcodes generator in the Post/Page edit screens if YOAST gets detected. That way we wouldn’t have to load MooTools in that screen and YOAST should work fine there.

• This reply was modified 8 years, 8 months ago by Gantry.

I just pushed our dev build for internal testing. If the fix will get confirmed – we will release update shortly.

Allright, here is the code that I promised 🙂 Firstly you have to copy the wp-content/plugins/gantry5/engines/wordpress/nucleus/particles/contentarray.html.twig to the wp-content/themes/g5_helium/custom/particles/

Next step is to edit that TWIG file and replace this code :

   {# Query Posts #}
    {% set query_parameters = {
        'cat': filter.categories|replace(' ', ','),
        'posts_per_page': limit.total|default('-1'),
        'offset': limit.start|default('0'),
        'orderby': sort.orderby,
        'order': sort.ordering,
        'ignore_sticky_posts': sticky_posts
    } %}

with this :

   {# Query Posts #}
    {% set current_post = [wordpress.call('Timber::get_post').ID] %}
    {% set query_parameters = {
        'cat': filter.categories|replace(' ', ','),
        'posts_per_page': limit.total|default('-1'),
        'offset': limit.start|default('0'),
        'orderby': sort.orderby,
        'order': sort.ordering,
        'ignore_sticky_posts': sticky_posts,
        'post__not_in': current_post
    } %}

This should ignore the current post.

• This reply was modified 8 years, 11 months ago by Gantry.

What do you mean by current post? You’d need to define which one is “first” for you. The newest one in choosen category?

Well the thing that concerns me is that you wrote that it all worked fine initially but suddenly stopped. If it was working fine before, somethings must’ve happened and the question is what. Did you update anything on your VPS? Did you enabled any PHP modules? Installed new plugins? Are you using the same Gantry 5 version that when it was working fine?

If you have two separate instances of WordPress and two different set of files – all should be working fine.

• This reply was modified 8 years, 11 months ago by Gantry.