London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

Per Nergård (MVP)
Apr 8, 2010
  4383
(0 votes)

FilterRemoveNullValues change in CMS 5

In CMS 4 for the filter to remove a page the property specified  had to exist on the page being filtered as well as the value being null.

In CMS 5 this has changed so the filter always assumes that the property always exist and only checks if the property value is null.

I guess that’s not wrong but depending on the circumstances I can see a possibility that you have a mixed page data collection from different sources where you just want to do the filtering on only the pages that have this particular property and just ignore the rest.

In my case we hade some old code that used this filter and still returned pages due to the property exist check. But after migrating to CMS 5 all pages got filtered out.

Apr 08, 2010

Comments

Please login to comment.
Latest blogs
Integrating Address Validation in Optimizely Using Smarty

Address validation is a crucial component of any ecommerce platform. It ensures accurate customer data, reduces shipping errors, and improves the...

PuneetGarg | May 21, 2025

The London Dev Meetup is TOMORROW!!

The rescheduled London Dev Meetup is happening tomorrow, Wednesday, 21st May, at 6pm! This meetup will be Candyspace 's first, and the first one he...

Gavin_M | May 20, 2025

From Agentic Theory to Practicality: Using Optimizely Opal’s Instructions Feature

A practical look at Optimizely Opal’s Instructions feature — from built-in agents to creating and managing custom instruction workflows. Ideal for...

Andy Blyth | May 19, 2025 |

Common Mistakes in Headless Projects with Optimizely

Adopting a headless architecture with Optimizely is a major shift from the traditional MVC-based development that has been the standard for years....

Szymon Uryga | May 19, 2025