<p>The query value for <code>p</code> has been the <a href="https://craftcms.com/docs/config-settings#pageTrigger" rel="nofollow">pageTrigger</a> since Craft 1.0 (and probably in the beta as well).</p>

<p>I'm not sure why you were still able to use it for other purposes up until recently. To be honest, it sounds like you were accidentally exploiting a bug, which has since been fixed.</p>

CC BY-SA 3.0
2016-10-18T17:43:32.107Z
2016-10-18T17:43:32.107Z
Lindsey D
<p>I encountered a problem which is very similar to <a href="https://craftcms.stackexchange.com/questions/10416/getparam-not-working-on-live-server#comment23803_10442">this post</a>. I've been using the letter "p" as part of a search string so <code>www.website.com/test?p=querystring</code>. It worked for more 6 months and now all of a sudden it doesn't work. Thanks to <a href="https://craftcms.stackexchange.com/questions/10416/getparam-not-working-on-live-server#comment23803_10442">the other post</a> I looked in my .htaccess file and see this rewrite rule: <code>RewriteRule (.+) index.php?p=$1 [QSA,L]</code> which was there by default when I installed Craft. I changed my query string parameter to "q" and now it works again. Not sure if something changed when I updated to the latest Craft version which at the time was version 2.6.2945, or if it's something else. </p>

<templating><params>
getParam not working anymore
# getParam not working anymore

(Asked by: username_0 on 2016-10-18)

I encountered a problem which is very similar to [this post](https://craftcms.stackexchange.com/questions/10416/getparam-not-working-on-live-server#comment23803_10442). I've been using the letter "p" as part of a search string so `www.website.com/test?p=querystring`. It worked for more 6 months and now all of a sudden it doesn't work. Thanks to [the other post](https://craftcms.stackexchange.com/questions/10416/getparam-not-working-on-live-server#comment23803_10442) I looked in my .htaccess file and see this rewrite rule: `RewriteRule (.+) index.php?p=$1 [QSA,L]` which was there by default when I installed Craft. I changed my query string parameter to "q" and now it works again. Not sure if something changed when I updated to the latest Craft version which at the time was version 2.6.2945, or if it's something else.

**Tags:** templating, params

---

## 1 answers

### Answer by username_1 on 2016-10-18. Score: 3 | Accepted answer

The query value for `p` has been the [pageTrigger](https://craftcms.com/docs/config-settings#pageTrigger) since Craft 1.0 (and probably in the beta as well).

I'm not sure why you were still able to use it for other purposes up until recently. To be honest, it sounds like you were accidentally exploiting a bug, which has since been fixed.


---

