Skip Navigation

[Resolved] Issue when using Toolset with WpRock

This support ticket is created 4 years, 3 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/Karachi (GMT+05:00)

This topic contains 2 replies, has 2 voices.

Last updated by davidP-30 4 years, 3 months ago.

Assisted by: Waqar.

Author
Posts
#2045041
2021-05-05 10_09_04-Clipboard.jpg

I am trying to view a page that contains toolset views.

Link to a page where the issue can be seen:
hidden link

I expected to see the page without any error code or extra text.

Instead, I got:
on top of the screen I see CA"> (which I suppose is part of the language code that should appear in the html).


<!--[if IE 7]><style>.wpv-pagination { *zoom: 1; }</style><![endif]-->CA">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="profile" href="<em><u>hidden link</u></em>">

It doesn't seem to appear when I view the page while I'm logged in :


<!DOCTYPE html>
<html lang="fr-CA">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="profile" href="<em><u>hidden link</u></em>">

#2045729

Hi,

Thank you for contacting us and I'd be happy to assist.

This seems to be the cache issue and the non-logged-in guest visitors are seeing the older cached version of the page.

Without logging in, I see the issue when I visit the page, but if I append some URL parameter '?no-cache=true' to force a non-cached version, it is fixed:
{yourwebsite.com}evenements/mojo/?no-cache=true

I'll recommend clearing all involved caches at plugins, server, and CDN level and then check the page again, as a guest.

regards,
Waqar

#2049379

My issue is resolved now. Thank you!