Chief Alchemist - Business Consulting For The 21st Century Via A Holistic & Intelligent Approach
Share RSS 2.0 feed for Sign up for the mailing list. Follow Chief Alchemist on Twitter. 'Like' the Chief Alchemist's page on Facebook. See what Chief Alchemist has been Q&A'ing on Quora. Chief Alchemist bookmarks & highlights on Follow the Chief Alchemist on Chief Alchemist channel on Chief Alchemist on Flickr. Mark 'Chief Alchemist' Simchock on LinkedIn. Free Initial Consultation. Email Chief Alchemist. Phone Chief Alchemist.
  • Mark ‘Chief Alchemist’ Simchock
  • 'Email me.Email => ca .at. ChiefAlchemist .dot. com
  • 'Phone me.Alchemy United => 732 997-0028
  • Free initial consultation.Free => Initial Consultation
  • Please be sure to subscribe to your communication channels of choice.
  • Click To Close => The small green (consultation), red (email) or blue (phone) icons in the top upper right.
Business Consulting For The 21st Century Via A Holistic & Intelligent Approach

ExpressionEngine 2.x Channel Parameters Quirk

It looks like there’s a slight quirk in how ExpressionEngine processes the channel parameters category vs category_group. It’s not really documented one way or another so I won’t call it a bug but it does strike me as a quirk.

The difference is, category allows for the use of and (i.e., &). For example, category=”1&2″. However, category_group does not support and, only or (i.e., |). In fact, when I tried category_group=”1&2″ EE didn’t error, it just treated the & as an | and kept going.

Maybe it’s just me but I kinda expected (and was counting on) some consistency between the ExpressionEngine channel parameters category and category_group. Not to worry, I revisited my web dev strategy and the new solution side steps this unexpected quirk and actually appears to be an improvement in meeting the biz needs of the project.

One step back, two steps forward!

Will not be published. Required.
Please include http://