Skip Navigation

[Resolved] taxonomy archive page running second loop above theme header

This support ticket is created 7 years, 2 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 27 replies, has 3 voices.

Last updated by Luo Yang 6 years, 2 months ago.

Assisted by: Luo Yang.

Author
Posts
#568394

It might be a bug of Views plugin, since I can duplicate same problem without the "storied" theme, so I have escalated this thread to our 2nd tier supporters, I will update this thread if there is anything found

#568496

Thanks. Whatever they find, please let me know so that I can proceed accordingly.

#569186

Our 2nd tier supporters are still working on it, I will update this thread if there is anything news.

#575861

Hi Luo,

Has there been any progress on this?

Customizing archives is the last major item of my build, but I can’t complete the site until this issue is resolved.

Customizing archives was one of the primary reasons I purchased the Toolset plugin in the first place, per this page: https://toolset.com/documentation/user-guides/what-archives-are-and-why-they-are-so-important/

Custom archives are ESSENTIAL to the unique SEO and user experience requirements of this particular site.

Is there someone at Toolset whom you could put me in contact with that could help me resolve this issue, or at least figure out a workaround until the issue can be resolved?

Let me know, please.

Thank you.

#578826

Hi, Just wanted to chime in here and second this issue, happening exactly the same for me (second View loop above theme header, essentially View outputting in the meta area; I'd conjecture a conflict with a shortcode, or enqueueing fonts per Luo, in meta) , and using Squared theme from ThriveThemes. Based on OP's (Eric's) detailed responses, it appears this is symptomatic of many/all of Thrive's themes.

Thanks, and hoping for an update overall.

#578839

Hi, Further to my previous, I can confirm that:

1) Luo's previous note about commenting out 'thrive_enqueue_head_fonts()' function in the header template of the theme fixes the immediate issue. Haven't tested more to see the implications to the fonts and other elements affected by the function.

2) This appears to be affecting all themes of Thrive, particularly seeing as they're reusing the same font enqueue function across different themes.

Of course, this fix will be overwritten in the next update, so a permanent update/fix in Thrive or Toolset will have to be made.

#580090

@eric, There isn't more news from our 2nd tier supporters, and I added your comment in our to-do list, hope it will be able to raise the attentions. Currently the only workaround is what I mentioned in post:
https://toolset.com/forums/topic/taxonomy-archive-page-running-second-loop-above-theme-header/#post-566309

#580408

Luo & NeekD1926,

Yes, I commented out this function in Thrive’s header.php file: <?php thrive_enqueue_head_fonts();?>

This allows the archives pages to render correctly.

As NeekD1926 mentioned, now whenever Thrive updates its header.php file, it will overwrite this hack. Which means I’ll have to manually inspect header.php on every update.

It would be preferable if either Thrive or Toolset would simply correct the code that’s causing the conflict.

Thanks.

#584714

For those PHP errors, you mentioned in the debug logs:
PHP Fatal error: Uncaught Error: Call to undefined function WP_Installer() in /nas/content/live/primaltonic/wp-content/plugins/types/vendor/toolset/toolset-common/inc/controller/admin/notices.php:94\nStack trace:\n#0 /nas/content/live/primaltonic/wp-content/plugins/types/vendor/toolset/toolset-common/inc/controller/admin/notices.php(72): Toolset_Controller_Admin_Notices->screen_any()\n#1 [internal function]:

We have got some similar reports with other performing background synchronizations plugins, which are fixed in the latest version of Type plugin, please update to Types plugin version 2.2.17 and test again, you can download it here:
https://toolset.com/account/downloads/

And feedback if it is fixed or not. thanks

#584906

I updated Types to 2.2.17 and uncommented 'thrive_enqueue_head_fonts()' in header.php, but it's still breaking the archives pages by inserting a second set of archives ABOVE the header.

I'm not sure about the PHP errors from my debug log as they relate to "background synchronizations plugins." This is the first I've heard of "background synchronizations plugins."

The problem I'm having is that 'thrive_enqueue_head_fonts()' in header.php of Thrive Themes is conflicting with Toolset, causing a second loop of archives to insert themselves ABOVE the header.

My best guess is that either Thrive or Toolset has a scoping bug in their use of get_posts().

#585085

Yes, you are right, the main problem of this thread:
thrive_enqueue_head_fonts()
is still in our to-do list, our developers are working on it, here is the feedback from our 2nd tier supporter:
We can understand why it happens but cannot guarantee we can solve this right now

#1102326

Hi, after several attempts to contact this theme authors we have been unable to receive any communication or collaboration to resolve this issue. Our team needs to discuss some technical details of this theme with the authors, and without that discussion we cannot resolve the problem. At this point, we encourage you to reach out to the theme authors, since as a paying customer they will probably be more responsive to your requests. Please let them know we are trying to contact them and you are waiting to have a problem resolved.

#1102338

As the request of 2nd tier supporters, I have changed the ticket status to "Need more details from client".