Docs

[Mark M]

Hi,

I have come across an issue. Our site uses a bunch of plugins with X (Integrity) v3.2.2. While verifying for conflicts for a planned upgrade to X v4.6.4, I noticed the index page of all our forums was being displayed like a portfolio with a single entry.

I tested with a localhost install of the latest version of WP, and the latest version of X. Installing only the latest versions of WPML, BBPress and Cornerstone I could replicate the issue after creating 2 forums. My test URL would be something like http://localhost:8080/forums/. I realise you can’t access my localhost, but if you try this bare-bones setup, do you get similar results? I attached the same image with the latest X vs the 2016 theme.

Any idea what’s causing this? It worked great before, but i can’t proceed with the upgrade if my forums aren’t accessible.

Thanks, as always for your excellent support.

Mark

[Rad]

Hi there,

Thanks for posting in.

This is my first time seeing this, I have a latest copy too and not getting this issue. Have you tried deleting the old X theme and install new one? Sometimes, the update will leave some files that are meant to be deprecated.

And I couldn’t really tell since it all works on my all my setup, perhaps, if I could check your site in a staging then I may able to gather information.

Thanks!

[Mark M]

Hi – thanks for the suggestion.

I tried that, but the same issue remains, with just these:

New WP install – 4.6.1
New X install – 4.6.4
New WPML CMS install – 3.5.3.1
Create 2 forums & switch to view the forum index to see the odd behaviour.

Deactivating WPML seems to make it display correctly.

I can’t really deploy this on our server, since it breaks functionality. Can you confirm these versions should work together?

Thanks!
Mark

[Christian]

Please setup or copy your local test site to a staging server so we could check your setup.

Thanks.

[Mark M]

This reply has been marked as private.

[Rad]

Hi there,

Please try adding this code to your child theme’s functions.php

add_action('init','remove_template_redirect', 9999999999);

function remove_template_redirect () {
remove_filter( 'template_include', 'x_force_template_override', 99 );
}

That should remove the WPML integration that alters template redirect.

Hope this helps.

[Mark M]

Hi Rad,

Thanks a lot! That worked!

Is that something will be corrected in future versions? Or was it something I was doing wrong?

Thanks again – great support!

Mark

[Rad]

Hi Mark,

WPML has an issue with archive templates so we added some fix. But that fix is also affecting some setup like yours, hence, let’s just remove the fix through the provided code. We’ll look into this to see what else alternative we can implement. But for now, it could be turned on and off through custom code.

Cheers!

[Mark M]

Thanks Rad!

[Rahul]

You’re most welcome!

Let us know if we can help with anything else.

Thanks!

[Author]

Posts