Skip Navigation

[Resolved] The "View in Use" Scan is not reflecting correctly

This support ticket is created 3 years, 9 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 4 replies, has 2 voices.

Last updated by saint 3 years, 9 months ago.

Assisted by: Waqar.

Author
Posts
#1959085

I have noticed that the "Where is this View used" button is not correct and often times, does not show where the View is used, even though it is definitely used in Oxygen. Example: hidden link

This result is not true, the View is used in: hidden link

#1962215

Hi,

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

The scan feature in the "Used on" column is designed to work for the views which are placed in the default WordPress editors.
( Gutenberg or classic/legacy editors )

The other page builders like the Oxygen builder that you have, store their content differently in their own formats. That is why the usage of the view is not detected if it is included through other page builders.

regards,
Waqar

#1962293

Ahhh, thank you Waqar!

Do you know if Views will be able to integrate with Oxygen deeper so that it can be detected? I use Oxygen almost exclusively for it's power and it pairs so well with Toolset.

#1962721

Thanks for writing back and I'll be happy to internally pass on this feedback.

For now, a workaround that you can try is to insert views in your Oxygen builder content using view's shortcode in a text widget, instead of using the Views widget.
https://toolset.com/documentation/programmer-reference/views/views-shortcodes/#wpv-view

#1963023

My issue is resolved now. Thank you Waqar!