[Resuelto] Passing arguments to a view / Views 3.6.26 breaks code that’s worked for years

[Autor]

Mensajes

[Creme]

Has the syntax or mechanism for passing arguments from one view to another changed with Views 3.6.26?

Situation: An online magazine, one Volume per year, 10 Issues per Volume

Data structure:

Type: Magazine Volume
Field: magazine-volume-year

Type: Magazine Issue
Field: magazine-publication-year (relates to Volume year)

VIEW 1: magazine-all-volumes-vw, displays all Volumes sorted on magazine-volume-year descending (2026, 2025, etc)
For each Volume, call VIEW 2 magazine-issues-per-volume-vw, with argument magazine-volume-year

<wpv-loop>
  [wpv-view name="magazine-issues-per-volume-vw" volume="[types field='magazine-volume-year' output='raw'][/types]"]
</wpv-loop>

VIEW 2: magazine-issues-per-volume-vw
FILTER Magazine publication year is a number equal to VIEW_PARAM(volume)

<wpv-loop>
  <!-- display Month & Year of Magazine Issue, sorted on month number descending (July/August 2026, June 2026, May 2026, etc) -->
</wpv-loop>

For clarity, much detail has been omitted from the actual code.

This construct has worked perfectly for years, but with Views 3.6.26 the argument passed from VIEW 1 appears not to reach VIEW 2, which now displays nothing. Calling [wpv-attribute name="volume"] within VIEW 2 displays nothing.

Many thanks
Julian

[Minesh]

Hello. Thank you for contacting the Toolset support.

This is a known issue to us and we already fix the issue. We will publish the official hotfix version in near future.

For now, you can download the hotfix version from the following link:
= enlace oculto

Replace your existing view's plugin with the above donwloaded hotfix version and hopefully that will help you to fix this issue for now and I will update you here when we officially publish then new version for Toolset Views/Blocks.

[Creme]

Hello Minesh
That works perfectly.
Yes, please notify me when the new version is officially published.
Many thanks