You can replace it with a substitute token.  There are a variety of
perfectly valid ways to go about it.
-Matt

On Mon, Jun 15, 2009 at 1:57 AM, Deepak <d88...@gmail.com> wrote:

> On Mon, Jun 15, 2009 at 3:56 PM, Deepak<d88...@gmail.com> wrote:
> > On Sun, Jun 14, 2009 at 11:48 PM, Matthew
> > Ratzloff<m...@builtfromsource.com> wrote:
> >> I assume you mean you're using Form's Filter integration.  Look into
> using
> >> Zend_Filter_Callback or writing your own.  It's about the same level of
> >> effort either way.  These pages should help:
> >>
> http://framework.zend.com/manual/en/zend.form.elements.html#zend.form.elements.filters
> >>
> http://framework.zend.com/manual/en/zend.filter.set.html#zend.filter.set.callback
> >> http://framework.zend.com/manual/en/zend.filter.writing_filters.html
> >> -Matt
> >
> > I am going to try it. I guess this could solve the problem.
> > Thanks!
> >
>
> By the way I need some hint (some logical or conceptual steps
> explained in plain English).
>
> My concern is if I modify the query string in any way (such as
> removing the slash) may result in different query than that intended
> by the user, which might not get the result he/she wants. So if
> possible I want to maintain the search string intact but let Apache
> mod_rewrite ignore that portion as not the URL but the query string.
>
> Given the countless numbers of CMS in development, somebody must have
> encountered this issue when implementing the particular CMS with
> mod_rewrite enabled mode. How do they overcome this issue?
>
> Thank you again for your valuable time
>

Reply via email to