Skip Navigation

[Resolved] Update to Views – 3.2.2.1 To 3.3.4 – Broke Some Views…

This support ticket is created 3 years, 11 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/Hong_Kong (GMT+08:00)

This topic contains 18 replies, has 2 voices.

Last updated by Luo Yang 3 years, 10 months ago.

Assisted by: Luo Yang.

Author
Posts
#1878691

Tell us what you are trying to do?
Update to the latest version of the Toolset Views plugin.

...This may have happened in other places, but in one area I know for sure...
I have pretty complex views set up for product specs (Name: Universal Product Specs View). This view contains has three ways to show specs depending on if the current post is a product "Model" (CPT) or a product "Series" (CPT). The view is set to show models with any relationship to the current post. So if the current post is a series, it renders information for the models related to that series. If the post is a model, then the [wpv-no-items-found] contains fields for the single model, and since the view is embedded in the content template for models and series, it just passes those fields along to the content template which renders the info appropriately.

The first part of that (Models related to a Series) has an added layer of complexity - Mobile Spec Table in [wpv-items-found] Inside <wpv-loop> tags and Desktop Spec Table [wpv-items-found] Outside <wpv-loop> tags.

Inside <wpv-loop> is the html and Toolset fields for the table specs. This means on mobile each model gets it's own table, one after the other.

But on the desktop view, I needed all model specs in one single table. This meant that rows need to be their own nested views so I could loop all specs side by side. These nested views outside the <wpv-loop> had the same query settings as the view they are nested in. If there wasn't a model related to the series, the nested view would output [wpv-no-items-found] which is totally empty, meaning the whole row would just go un-rendered from the table.

This worked perfectly until I updated to 3.3.4 from 3.2.2.1

The issue (I think) is that the nested views within this Universal Product Specs View are outputting content when they should be blank. This leads me to believe a change in how relationship queries work in views could be involved.

If Christian, Shane or Luo could help with this, they may already have a duplicate of the site to help with issues experienced in my other open tickets.

On that duplicate, they can simply look at the M1d product specs before and after the update and reference the view:
Universal Product Specs View and the views nested within.

If this doesn't make sense and I need to provide screen shots, I can accommodate by spinning off a test instance of my dev site and running the update so I can show side by side what's going wrong. I hope that's necessary though.

Is there any documentation that you are following?
No.

Is there a similar example that we can see?
No.

What is the link to your site?
It's IP restricted. Christian, Shane and Luo have received duplicate site for open tickets, just navigate to M1d from the main menu.

#1879007

Hello,

We won't keep your website database, please check these:
1) Do normal compatibility issue check, for example, deactivate plugins/theme
2) Get the PHP debug logs,
3) if the problem still persists, please provide your website database dump file in below private message box( you can put the package files in your own google drive disk, share the link only), also point out the problem page URL and view URL, I need to test and debug it in my localhost. thanks
https://toolset.com/faq/provide-supporters-copy-site/

#1879989

Thanks for the details, I am downloading the files, will update here if find anything

#1883389
m1d.JPG

Your duplicator package is large size, after remove all other plugins/theme and upgrade all Toolset plugins to the latest version, I can install it in my localhost, but I don't see the M1D in the menu, see my screenshot.

Please point out the problem page URL and view URL, where should I check the problem, a screenshot will help, thanks

#1884097

Not sure why that would be. It's set up using WP under Main Menu. In any case...

hidden link

#1884721
m1d-2.JPG

I have tried the URL you mentioned above, but get 404 error, see my screenshot m1d-2.JPG

Is the URL a custom post or page? can you confirm the problem persists after all other plugins/theme deactivated?

I have searched in the database, and see a post in custom post type "Amplifier", which is using title: M1d, the post ID is 1106

Is this problem post?

#1885235

Okay, I know why you're not seeing it. Permalink Manager Lite (plus a little custom PHP) outputs a link that shows relationships.

m1d is a "model" custom post type, m-series is the "series" custom post type that it's related to and monoblock-amplifiers is a model type taxonomy

If you go to the backend and look under models you will see m1d and can access it that way. Sorry, I hadn't considered that would be an issue.

#1886497
empty-fields.JPG

Your website is quite complicated, it is hard to locate the problem.

I assume we are talking about the "model" post "M1d", the post ID is "48902", can you confirm it?
If it is, I have tried it in front-end, I see broken HTML codes, edit above post:
hidden link
I see lots of empty custom field groups, see my screenshot empty-fields.JPG

I suggest you fix those empty custom field groups first, for example:
Dashboard-> Toolset-> Custom fields, field and edit those custom field groups, restore those missing custom fields first.

#1888933
notmissing.PNG

Those aren't empty or missing on my site. Perhaps your database is corrupted. There is no custom HTML on the backend. The only HTML error I could find on the front end was <br /> in the debug, but it's possible there was an out of place tag that I have fixed since making that duplicator package. I would need to see your build out.

If you need admin access to the main dev site, I can arrange it, but please note that it is very much under development. I would need your IP address to whitelist.

#1890485

Please try these:
Use some MySQL tools, export your website database, and put it into your own Google drive disk, share the link in below private message box, thanks

#1893613

I have request access to the your file link, please grant it, thanks

#1894045

Sorry, I must not have changed the permissions. Please try now.

#1894645

I can download the sql file, will update here if find anything

#1902843

Just checking to see if there's any news on this?

#1903615

Sorry for the delay answer, I have tried the database dump files you provided above, they are not valid, I get these errors when import them: Incorrect format parameter

Please follow the duplicator plugin document, make the database only package file, and share it again:
hidden link