I am trying to: Update to latest Elegant Themes Extra theme
Link to a page where the issue can be seen: hidden link
I expected to see: The first pepper in the list, without the query page's entry first
Instead, I got: The result you see now.
This issue is over 3 years old, but my WordPress is getting 'creaky' and it is overdue for updating the theme. This issue has prevented us from upgrading. You can see from the attached images how it looked before updating which we are happy with.
The options haven't changed, but I included a screenshot of the "Don't include..." option as it is checked. I have gone over the scripts/macros in hopes of finding something that might have changed in Toolset that may address this, but I could not find anything.
I've checked the view result and the view returns the correct results and the view results does not contain the current post or page where the view is inserted.
The only workaround I found is I've added the following custom JS code to the view's JS box:
jQuery( document ).ready(function($){
jQuery(".et-boc:first").hide();
});
jQuery( document ).on( 'js_event_wpv_parametric_search_results_updated', function( event, data ) {
/**
* data.view_unique_id (string) The View unique ID hash
* data.layout (object) The jQuery object for the View layout wrapper
*/
jQuery(".et-boc:first").hide();
});
That works pretty well, but there's still three issues:
One is that it draws all the content before hiding this. I'm sure that's due to some JS deferring, and I can likely tweak theme settings and the caching plugin to solve this.
The second issue (and I'm sorry I forgot to mention this before) is that if you look at the Peppers CPT, I have tried to compensate for the issue by adding another pepper named "Test Pepper Ignore" that has a higher scoville rating so the correct first pepper is displayed. If I remove this pepper, we still will not see the proper first pepper entry.
Third, selecting the Pepper Classification filter displays a bad entry for the first in the View's list.
I know in the past certain compatibility workarounds for Divi/Extra have needed to be implemented. I am hoping this can be solved, as we have waited a long time.
Thank you for your help!
The above code holds some divi shortcode that used to be the culprit of this issue. There was no issue from the Toolset as Toolset view returned the correct result.
To solve all the issues, I've removed the above code from the content template and replicate it with the related HTML that above shortcode generates and I've then replaced the dynamic Toolset shortcodes. So the content template code now holds the value as given under instead of above that holds the divi shortcodes:
