claco

Also, using year/m to retrieve an archive on a Page (not a post, or a template for a category, multiple posts, etc) seems broken. It’s a single entry for a single page. Year should be ignored.

The problem is, a) I’ve found no definitive list of reserved query string params, and b) Magic is bad.

I have a single page template, and I want to use various query string params in custom code to control the behavior of different elements on that page. It seems silly that I have to play a guessing games about how I can write PHP and pass query string elements (just like I would do in any other web framework in the world). Why m and not month? Why year and not y? Just because the wordpress urls are friendly, doesn’t mean all use of the query string params for applications, plugis and custom code can’t be used. And since my custom permalink style doesn’t include %year%, it seems broken.

Here’s the real example. I have a template called vulunteer.php, tied to the Volunteer page. That template displays the pages content and all is well. Now I added a block of code to pull a set of unrelate information form the database, and that code was going to look for the year and month query params to determine what information they were interested in.

Worked fine for ?year=2009&month=3. The minute year went to 2010, or 2008, I get a 404. The minute I change my code to use ?y=2010&m=3, I get a 404 because WordPress is in love with the m param.

That’s why I’m frustrated. I could understand if year is a reserved query string param, but then I would expect month to be reserved, not m.

All in all, it’s a big fail in terms of expectations.

Which relates to my problem how?