Skip Navigation

[Resolved] Incorrect used on information

This support ticket is created 5 years, 6 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
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

Tagged: 

This topic contains 6 replies, has 2 voices.

Last updated by Christian Cox 5 years, 5 months ago.

Assisted by: Christian Cox.

Author
Posts
#1322109
Screenshot 2019-08-22 at 9.40.36 PM.png
Screenshot 2019-08-22 at 9.43.50 PM.png

Dear Sir/Madam,

Refer to screenshot, the deco-search-2 is inserted into the page with slug "home-2" but not the deco-search, when I click Scan button to both deco-search and deco-search-2, there is no page be used on deco-search-2, I try edit the home-2 and save again but no luck.

How can I fix this problem? I worry it wrongly report and I delete the view.

Best regards,

Kelvin.

#1322237

Hello, I can see the issue you have described. If only the filters of a View are displayed, the Scan button does not report this View instance. I will report this to my 2nd tier team for additional investigation. In the meantime, you can add the View shortcode inside an HTML comment, like this:

<!-- [wpv-view name="deco-search-2"] -->

The scan button should recognize the View now, and report it. I will let you know what I find out from 2nd tier support.

#1322293
Screenshot 2019-08-23 at 12.15.29 AM.png

Dear Christian Cox,

As per your request, I add the View shortcode inside an HTML comment and scan, there is nothing to the result.

#1322303

You're using the wpv-form-view shortcode in the comment, which is not quite right. The shortcode should be wpv-view, not wpv-form-view:

<!-- [wpv-view name="deco-search-2"] -->

The wpv-form-view shortcode only inserts the search filters. The wpv-view shortcode inserts the results and the filters. The results seem to be required for the scan to work.

#1322647

Dear Christian Cox,

Yes, thanks for your correction. I change the wpv-form-view to wpv-view and it can be scanned but I suggest the scan progress should consider the wpv-form-view also as it is a part of the Views, if it skips this, we will wrongly think the view does not attach to any page/post, once we delete it, we will get problem.

Best regards,

Kelvin.

#1323831

Yes, I agree, the scan feature should include this information without the necessary workaround. Our 2nd tier support team has escalated this usability issue to our developers. I will keep you posted here as I receive more information.

#1343199

Hello, this issue should have been resolved in the latest round of updates. Please update all Toolset plugins to their latest versions and let me know if the problem is not completely resolved.