Skip Navigation

[Résolu] Content Template not appearing above Archive Loop

This support ticket is created Il y a 3 années et 10 mois. 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.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

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/Karachi (GMT+05:00)

This topic contains 3 réponses, has 2 voix.

Last updated by alexG-4 Il y a 3 années et 10 mois.

Assisted by: Waqar.


I'm trying to display a content template above the Archive Loop using the block editor. The content appears in the preview within the editor, but it does not appear on the page itself.

Please see this video:
hidden link

I've deactivated all plugins (including the remaining two shown in the video). And the same behaviour happens with the 2020 Theme.




Languages: Anglais (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi Alex,

Thanks for asking! I'd be happy to help.

This issue is already highlighted and when a content template is used outside the loop of a WordPress Archive, no current post/page scope is available due to which content template fails to render.
( ref: )

A fix for this is planned to be released in Views version 3.3 and for now, a workaround can be to include any post/page ID through the "item" attribute.


[wpv-post-body view_template="slug-of-content-template" item="2"]

I hope this helps and please let me know if you need any further assistance around this.



Thanks, Waqar

My searches didn't find that reference to the problem. But on the other hand, the "workaround" proposed there didn't mention your suggestion - which works perfectly.




My issue is resolved now. Thank you!

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.