Is there a method for debugging URL parameters? In the process of chasing down a rendering bug on Chrome, I unintentionally did something that broke the uri params necessary for the simplesearch plugin, eg. query:something returns a 404.
Has anyone had the issue before? Apache and Grav logs are clean.
Oddly this was because a reformat of system.yaml had left out param_sep: ';', but this time this did not yield any error from Apache.
Glad you got it sorted. That ; separator is only needed on certain windows/apache setups.
Gotten used to keeping it there for development, but in fixing some errors in the language-setup it got lost between development, testing, and deployment.
Log in to reply.
| Topic | Participants | Replies | Views | Activity |
|---|---|---|---|---|
| 0 | 1361 | 9 years ago | ||
| 2 | 939 | 9 years ago | ||
| 2 | 4069 | 9 years ago | ||
| 1 | 2958 | 9 years ago | ||
| 3 | 1123 | 9 years ago |