Q=chicken/page=2 is not parsable by Zend Frameworks' router. The router will only see search The router relies on the Path Info provided by the server and anything after the? Is the query string You would need to use a path such as this: search/word (default page 1) /search/word/page In which case your regex would become much simpler.
Q=chicken/page=2 is not parsable by Zend Frameworks' router. The router will only see /search. The router relies on the Path Info provided by the server and anything after the?
Is the query string. You would need to use a path such as this: /search/word (default page 1) /search/word/page In which case your regex would become much simpler.
Thanks for the input, now I know why my search button doesn't work. I edited my original question for more details. – Qin Dec 8 '10 at 19:06 My answer is still the answer.
What you are trying to do is not possible with the request string /search? Q=chicken/page=2 will result in the pathinfo being /search and a single $_GET param of q having the value chicken/page=2 - the Zend Framework router uses the pathinfo ONLY. – Darryl E.
Clarke Dec 8 '10 at 19:10.
Does fix the regex, but my routing still doesn't work for the reason pointed out by Darryl. – Qin Dec 8 '10 at 18:51.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.