[Gelöst] Views not working properly after update

[Author]

Artikel

[ashiA]

Hi,

I updated toolset and WordPress to the latest version today. My last update must have been 6-7 months ago, so it was after sometime.

Post the update, I am facing an issue with views.
(a) Any view which has pagination enabled, will not display the results. When I turn it to no pagination, the results are shown fine.
(b) I use front-end filters across multiple different views, with most of them set to update results via Ajax when the user changes and filter value. These filters do not appear to be working any longer. Importantly, on changing the filter the URL no longer seems to be getting updated via the search parameters.

Would appreciate any assistance on the same.

[ashiA]

Just an update - I tried changing the filtering option from Ajax to manual with a submit button. The filtering now works, but we prefer to have the Ajax implemented.

It seems to be that there is some Ajax issues causing the problem, post the updates.

[Shane]

Hi Ashi,

This is quite possibly a case of a plugin conflict if you're not able to use the AJAX search but able to use the non-ajax search.
In a case like this when the plugins are not functioning as intended we recommended that you disable the non-toolset plugins.
What this means is that you will need to go through your list of plugins and disable each of your plugins one at a time while checking to see if the issue still remains.

Thanks,
Shane

[ashiA]

Hi Shane,

Thanks for your inputs. It appears that the problem was being caused by W3 Total Cache, and more specifically the minify settings. Once the minify option has been turned of, the Ajax is now working fine.

I would like to avoid if possible losing the performance benefits of minify. Any options that you might suggest that I could consider, in terms of changes to the minify setting that can help avoid the Ajax issue while still using minify in caching.

[ashiA]

Hi Shane,

I also came up with an additional issue while testing. Please note that W3 Total Cache has been disabled (this was the plugin which was causing the Ajax error).

The issue is now with Content templates. Most of my content templates for custom post types are working fine. However, for one of the post types the custom template seems to no longer be working. I am facing the following issues:
(a) when I view a post from this custom post type, I am only seeing the body field -- none of the custom fields that have been designed to show in the custom template are showing
(b) whenever I try to add a new custom field via the fields & text block, it reverts to displaying the body field content only
(c) when adding a single field block, i no longer get the option to choose the post-type (it only displays current post or other post) and there is no option below for custom field

Has there been some new updates that have changed how this needs to be set up. Also, not sure why but i am only facing this issue with a single custom post type - all the other custom posts seem to be working fine.

[Shane]

Hi Ashi,

Thank you for the update. We do have information on how to use our plugins with optimisation plugins. Here is the info below.
https://toolset.com/faq/how-to-use-optimization-plugins-with-toolset/

Has there been some new updates that have changed how this needs to be set up. Also, not sure why but i am only facing this issue with a single custom post type - all the other custom posts seem to be working fine.

There hasn't been any new updates since January 25, 2022.

What I can do is to have a look at the page with the issue for to see what is happening.

I've enabled the private fields for your next response. Also send me the link to the exact page with the issue.

Thanks,
Shane

[Shane]

Hi Ashi,

Thank you for the credentials to the demo site, however they don't seem to work.

Can you check if they work on your end and let me know.

Thanks,
Shane

[ashiA]

Hi Shane,

My apologies, had forgotten to actually add the user. Can you check now, I have checked at my end and it is working.

[Shane]

Hi Ashi,

The other template elements should now be showing. Can you check this on your end and let me know if you're able to see them now.

It appears that elementor is causing the issue. Once I disabled elementor and checked the page the elements loaded without any issues. Are you able to disable elementor for this post type only?

Thanks,
Shane

[ashiA]

Hi Shane,

Thanks for your support on this. Even I tried this at my end, and when I disable Elementor the content type does seem to show fine.

However, there are a few issues
(a) Elementor is very important in this particular post type. Disabling this in this post type is not really an option for us.
(b) We have other custom post types (AMC for example) which also does use Elementor for the body field. However this issue in the AMC post type and the content templates are working fine.

Is it possible to try to identify what is the specific issue that Elementor is causing, and why it seems to be causing this only in this custom post type, but not the others.

Really would appreciate if you can try to identify this specific solution.

[Shane]

Hi Ashi,

What seems to be happening is that elementor is loading the post content directly without taking into consideration the fact that Toolset has overwritten the post body and is now displaying it with a content template.

However now it seems since i've disabled/reactivated elementor pro, i'm no longer able to see the template for this post type.

Can you check this for me so that I can continue debugging.

Thanks,
Shane

[ashiA]

Hi Shane,

Just checking to mean that when you say that you can no longer see the template for this post type, you mean an Elementor template and not the toolset custom post template. I can see the toolset custom post template at my end.

Just to let you know the page structure. Toolset custom post type is what was displaying the post. However, there are a couple of Elementor elements that also do come into the display part - (a) there was an Elementor library which was included as part of the Toolset custom template for PMS schemes - I have removed this at my end once you mentioned that Elementor may be causing the issue (b) the other area is that there is a footer template which conditionally shows for PMS schemes. This affects the footer and not the main content area which is controlled by Toolset custom templates.

At my end I have removed both the Elementor library block which was showing up on the content template for PMS schemes and I have also disabled all Elementor elements that were showing up as part of their theme builder. Have cleared all caches post doing the same, but am still not getting the PMS scheme custom template to display correctly.

[ashiA]

In addition to my previous message, I just realised that there was only one key difference between the PMS scheme (not working) custom post type & the PMS AMC (working) custom post type. Both of these post types have custom fields but use Elementor for the main body. PMS AMC is working fine (both custom fields & the body created via Elementor are showing fine), while PMS schemes are giving the issue (only the body created via Elementor is showing, not the custom fields).

The only recognisable difference between the 2, was that the PMS scheme content template had an Elementor library block as part of the content template. This was not the case with the PMS AMC content template.

I was hoping to address the issue by removing this Elementor library block, but the issue seems to continue even after having removed this. Not sure if there could be some cache issue at the content template level that is preventing this removal from addressing the issue (if this was the cause in the first place).

Just thought would let you know to help if your analysis

[Shane]

Hi Ashi,

What I know is that the elementor templates will completely overwrite the Toolset Content templates when its comes to modifying the body area of your posts.

It is usually advised to only use one template builder to do customize how your content will look. In this case it would be either elementor or Toolset Blocks.

However it seems i've ran into a snag with the Elementor Pro as it needs to be verified before I can make adjustments to the templates on custom post types.

My thinking is that if you create and elementor template for the custom post type and then add the Post Content widget then our content templates should overwrite this post content widget which should allow you to have the Toolset template being loaded in tandem with the elementor template.

Is there a way for you to activate the elementor pro license on the testing site so that I can continue with the testing of the templates?

Thanks,
Shane

[ashiA]

Hi Shane,

Thanks for your response. If you open up a new private ticket, I can give you access to the dev site which has elementor pro enabled.

I tried what you were trying to do - create an elementor template and then add the post content widget (which has a toolset content template defining the layout). This does indeed work, thanks for this. It gives an immediate solution to a problem.

However, there seems to be some deeper issue which is at play. The first point is that if you try to edit the toolset content template, you will still see some strange behaviour - when you try to add a custom field in the toolset template (using single field or text & field block), in the live preview of the content template the body is loading instead of the custom field.

Like indicated earlier, this issue is only happening on one custom post type (PMS schemes), while the other custom post types are working fine. I am wondering whether due to some reason, the content template has been corrupted and creating a new content template would help.

I had also contacted Elementor support to try to see if they could figure a solution - sharing their response below (which again seems to suggest that something specific to this one custom post type is happening).

After an investigation of your website issue, it seems that this issue is not coming from Elementor. It seems this is something server-side-related. I have tried disabling all plugins, including Elementor and Elementor Pro, leaving just your current theme active and the Toolset plugin, which you used to create templates and custom post types. Even in that case, the fields are not displaying.

I noticed there are a lot of errors in the console related to this template. Please try opening versteckter Link and investigate it in Chrome Inspector. Console tab. You will see a lot of net::ERR_HTTP2_SERVER_REFUSED_STREAM errors in there. This is not happening with other Tooltip templates that work fine and display custom fields.

I would kindly suggest double-checking this template and contacting your web hosting provider to see what can be done from their side since it seems that not all updates you performed work well with HTTP2. Your fields seem not to be displayed since the server refuses AJAX requests on this template and could not load them. Also, it may be related to your current template since other templates have shortcodes and fields added as Views, and this one has HTML widgets. It may also be one of the culprits that fields added via View template from Tooltip can access field values, but when added in the template via HTML block from Gutenberg, it simply gets sanitized and not loaded.

Please have a look at the templates difference here (one has view templates and another just HTML widgets):

ref. versteckter Link

I hope these insights will be helpful. If you need any further assistance from our side, please do not hesitate to get back to us. We will be more than happy to help.

Kind regards,
Elementors support team