CCS [related] tag doesn't work anymore.

Update:

After reading the updated plugin guides, I realized that [related] shortcode does not exist anymore so I updated my code and this one worked well:

<div class="post-related section-container clearfix">
<h2 class="section-title">????? ??????</h2>
<div class="row">

[loop type=post count=3 tag=this exclude=this orderby=rand]
<div class="post-box-wrapper col-sm-6 col-md-4 "><article class="post-972 post-box post-box-headline">
<h3 class="title title-small">[field title-link]</h3>
<div class="post-thumbnail-wrapper vw-imgliquid imgLiquid_bgSize imgLiquid_ready">[field image-link size="vw_small"]</div>
</article></div>
[/loop]

</div>
</div>

However, I didn’t find a replacement for this part:
[if not tag=”exclude”]
[/if]

Which intends to remove all posts from that loop that has the “exclude” tag/flag.

Please advise,
Many thanks!

Hello, sorry it took me a few days to reply.

The [related] shortcode still exists – it’s in the documentation under Main Features -> Taxonomy. Also, [if not tag=exclude] should work inside [loop]. Have you tried it? If it doesn’t work correctly, could you describe what it’s doing? I’ll set up a test to see what I can find.

Hi Eliot,

Thank you for your reply!

The [related] shortcode might be valid as you say, but I ended up using the [loop] code instead to which can do the same as [related], which is OK.

However, when I incorporate [if not tag=exclude] which I used previously in [related] and now in [loop] what happens is that the plugin seems to crash and doesn’t allow the rest of the WordPress post to load.

For example, this piece of code work:

<div class="post-related section-container clearfix">
<h2 class="section-title">????? ??????</h2>
<div class="row">

[loop type=post count=3 tag=this exclude=this orderby=rand]
<div class="post-box-wrapper col-sm-6 col-md-4 "><article class="post-972 post-box post-box-headline">
<h3 class="title title-small">[field title-link]</h3>
<div class="post-thumbnail-wrapper vw-imgliquid imgLiquid_bgSize imgLiquid_ready">[field image-link size="vw_small"]</div>
</article></div>
[/loop]

</div>
</div>

While this piece of code does not work:

<div class="post-related section-container clearfix">
<h2 class="section-title">????? ??????</h2>
<div class="row">

[loop type=post count=3 tag=this exclude=this orderby=rand][if not tag="exclude"]
<div class="post-box-wrapper col-sm-6 col-md-4 "><article class="post-972 post-box post-box-headline">
<h3 class="title title-small">[field title-link]</h3>
<div class="post-thumbnail-wrapper vw-imgliquid imgLiquid_bgSize imgLiquid_ready">[field image-link size="vw_small"]</div>
</article></div>
[/if][/loop]

</div>
</div>

And if you look at the code of the initial post, it didn’t work either with [related] tag instead of [loop].

Please advise, thanks!

I tested this, and [if not tag=exclude] is working correctly on my side – inside both [related] and [loop].

what happens is that the plugin seems to crash and doesn’t allow the rest of the WordPress post to load

How strange.. I’m looking at your code, but I don’t see anything that could cause an issue.

One thing I can suggest is to start with the simplest version of the code, to see where it stops working. For example, I tested with:

[loop type=post]
[if not tag="exclude"][field title][/if]
[/loop]

..and..

[related taxonomy=tag]
[if not tag="exclude"][field title][/if]
[/related]

Also, I just made a plugin update, so please try that too.

Hi Eliot,

I updated the plugin to the latest version.

Unfortunately, I confirm that even simple codes like:

[related taxonomy=tag]
[if not tag="exclude"][field title][/if]
[/related]

Still don’t work once I’m using [if not tag=”exclude”][/if]

Same with [loop] is crashing the page.

– Please note that I am using Visual Composer, probably the most popular page builder for WordPress.
– I would love to volunteer more information and I’ve been trying to reach out to you via Slack as well.

Please advise,
thank you for your time!

It could be a conflict with Visual Composer. Here are some ideas to try to find the cause of the issue:

1) Does the code work when Visual Composer is disabled?
2) ..when loaded from somewhere other than current post content, for example, a field or another post?
3) ..without using quotes? [if not tag=exclude]
4) ..with other conditions? For example, [if name=something]..[/if]

Also, is the code just inside the post content or loaded from somewhere else via shortcode or PHP? Or..inside some widget of Visual Composer..?

1) Does the code work when Visual Composer is disabled?
No, I used the classic editor and it’s still not working when I’m using the [if not tag=exclude] condition.

I also disabled the Visual Composer plugin, getting the same result.

2) ..when loaded from somewhere other than current post content, for example, a field or another post?
In order to test this I created a new post, with the following code:

[if not category=recommend]
  Must watch!
[/if]

And it generated the same result.

3) ..without using quotes? [if not tag=exclude]
Still the same result.

4) ..with other conditions? For example, [if name=something]..[/if]
Every condition I’m using holding the page from load and results in the same issue.

In summary, every time I’m using conditions the page load is crashing.

Back to you,
Thanks!

..every time I’m using conditions the page load is crashing.

How strange.. I’m not able to reproduce the issue on my end, so it’s hard to determine what’s happening there.

If you don’t have debugging mode enabled, please try putting the following line in wp-config.php (around line 70).

define('WP_DEBUG', true);

Do you see any warnings or errors?

—

#2 is especially odd – a new post with only a basic condition. So it displays nothing and the rest of the page doesn’t load? Hmm..

A couple things you could try (if you have the time):

1) Deactivate all other plugins one by one to see if any of them are related to the issue.

2) Disable all modules one by one in the plugin settings.

Interestingly, it seems like 2 weeks later the problem fixed itself.

I wonder what could have caused that!

I’ll report back within a few more weeks, thank you for your assistance thus far ??

Thanks for the update, I’m glad to hear that it’s been resolved. I’ve continued to improve various parts of the plugin (including the [related] shortcode) so somewhere along the way the issue must have been fixed. That’s good to know.