[TYPO3-core] RFC: Bug #1347: Indexed Search results navigation relies on JavaScript

[Michael Stucki]

Hi Benni,

it relies on JavaScript because the result navigation submits a POST
request. It is not easily possible to compile all settings into a GET
parameter without getting a link which is about 300 characters long.

According to the HTTP specification, this is allowed, however (see my
post on typo3.teams.typo3org yesterday) it seems to cause problems in
some environments.

Writing this, I have not yet looked at your implementation. Probably you
are taking care of this already...

- michael

Benjamin Mack wrote:
> Hey,
> 
> Ingmar Schlecht wrote:
>> I didn't read the patch at all, but: I'm wondering why JS is needed at
>> all? And why do we need to make it optional, not get rid of JS
>> altogether at that point.
> Dude, I didn't write indexed_search but when I found out about that
> (when I used this ext) I thought the exact same thing. Why is JS needed
> here?
> 
> The patch was done by someone else, I just want this fixed. Another
> solution would be to integrate one of the extensions that take care of
> that already fix this problem, they are available in TER. Unfortunately
> I don't want to spend too much time for that since I wonder why this
> patch didn't go into the core one year ago already... Don't want to have
> this happened again. Well, if there is no volunteer, I'll see what I can
> do.
> 


-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/