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 18 replies, has 2 voices.
Last updated by Luo Yang 3 years, 3 months ago.
Assisted by: Luo Yang.
I can install the new full backup duplicator package, after deactivate all other plugins, I can see the Toolset Dashboard in admin side,
According to the description you provided in post:
https://toolset.com/forums/topic/update-to-views-3-2-2-1-to-3-3-4-broke-some-views/#post-1879615
I have searched the view name "Table Spec Driver Size Inches", but can't find the exact one with the same name, see my screenshot: table.JPG
Which one is the "Table Spec Driver Size Inches" view? can you provide this view's ID?
And I have tested it in front-end:
hidden link
Where can I see the problem you mentioned above:
After the update, the view "Table Spec Driver Size Inches" correctly showed a result for [wpv-items-found] when looking at the M1d post.
Please provide a screenshot for it, thanks
Ah, sorry, like I said the site is under development. Since submitting this ticket, the Driver Size Inches Spec was broken into those two specs shown in your screenshot.
But I guess it doesn't matter. I did the update again to take more 'before and after' screenshots, and this time there was no change to the spec tables after updating views.
I double checked the version number on Views and see that this version I updated to is in fact newer. Previously I updated to version 3.3.4, and this is version 3.3.5.
So something must have changed in this new version to correct this entire issue. I went to the changelog but the content was not rendering correctly - screenshot attached.
I'm glad it's fixed, but I'd like to know more. From your post it sounds like you did see the issue, so perhaps you updated to 3.3.4? Please confirm.
