SaaS CMS has officially launched! Learn more now.

Per Nergård
Apr 8, 2010
(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


Please login to comment.
Latest blogs
Frontend Hosting for SaaS CMS Solutions

Introduction Now that CMS SaaS Core has gone into general availability, it is a good time to start discussing where to host the head. SaaS Core is...

Minesh Shah (Netcel) | Jul 20, 2024

Optimizely London Dev Meetup 11th July 2024

On 11th July 2024 in London Niteco and Netcel along with Optimizely ran the London Developer meetup. There was an great agenda of talks that we put...

Scott Reed | Jul 19, 2024

Optimizely release SaaS CMS

Discover the future of content management with Optimizely SaaS CMS. Enjoy seamless updates, reduced costs, and enhanced flexibility for developers...

Andy Blyth | Jul 17, 2024 | Syndicated blog

A day in the life of an Optimizely Developer - London Meetup 2024

Hello and welcome to another instalment of A Day In The Life Of An Optimizely Developer. Last night (11th July 2024) I was excited to have attended...

Graham Carr | Jul 16, 2024