View only showing 1 item after updating to Views 2.9 and Types 3.3.3

This thread is resolved. Here is a description of the problem and solution.

Problem: After updating Views, the results seem to be inaccurate in a View using post relationships and custom field filters.

Solution: Update to the latest version of Views to get the fix here.

This support ticket is created 5 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
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: Post-relationship, Views plugin

This topic contains 8 replies, has 2 voices.

Last updated by matthewC-9 5 years, 3 months ago.

Assisted by: Christian Cox.

Author

Posts

July 25, 2019 at 8:54 pm #1301035

matthewC-9

I have a content type template (type = location) that loads a view of items of a different content type (type = arbitrary feature). The view is set for no limit of items and to skip no items. It accepts a parameter for area. The template has three different areas where the view shows up, like this:
[wpv-view name="location-page-feature-areas" area=1]
[wpv-view name="location-page-feature-areas" area=2]
[wpv-view name="location-page-feature-areas" area=3]

I had it working so that I could create a relationship between the feature and the location, assign it to an area, and have it show up there. All three areas would show up on the page, and I could assign multiple features per area and they would all show up as expected.

I updated Types and Views today, and since then, only one feature will show up anywhere on the page, regardless of how many I try to assign or whether I assign them to the same or different areas. I haven't edited the view, so I'm guessing something changed with this latest plugin update.

July 25, 2019 at 9:26 pm #1301085

Christian Cox

Okay let me know when you have this set up somewhere I can take a look. I'll open private reply fields here.

July 26, 2019 at 2:19 pm #1301619

matthewC-9

An update on this: rolling localhost back to Toolset Views 2.8.2 has this working again (with no other changes to the view, template, content, etc). Here's a screenshot of what I'm seeing on that same page now (toolset-view-2) vs. what was showing with 2.9 (toolset-view-2.9). So it's definitely something about the update that made the difference.

July 28, 2019 at 3:15 pm #1302311

Christian Cox

Thanks, I see the problem you described here in the staging site, and based on your setup here I was able to recreate the problem in my localhost. I am escalating this to my 2nd tier support team now and I will let you know what I find out.

July 29, 2019 at 1:22 pm #1302893

matthewC-9

Sounds good - thanks, Christian!

July 30, 2019 at 4:29 pm #1304173

Christian Cox

Hi, our developers let me know that a hotfix for Views is due later this week, and the fix for this issue is planned to be included in that release. I'll keep you posted here when it's ready to install.

July 30, 2019 at 5:30 pm #1304191

matthewC-9

Awesome - thank you, Christian!

August 1, 2019 at 2:13 pm #1306931

Christian Cox

Hi, the hotfix releases are now available for download or automatic update. Please update all Toolset plugins to their latest versions and let me know if the View's results are still incorrect in the latest versions.

August 1, 2019 at 3:39 pm #1307037

matthewC-9

Yep, looks better now. Thanks, Christian!