Search results : moving to another page – URL problem

[pt20100201]

Search results : moving to another page – URL problem

Dear Thorsten

In phpMyFAQ v 2.6.14 – and 2.6.15 - after a search operation, clicking on a page number returns an invalid URL.

Example

Code: Select all

https://faqs.up.pt/faq/index.php?search=impressao&submit=Procurar&action=search

 

The (invalid) generated page 2 URL is

Code: Select all

http://search.html/?search=impressao&searchcategory=0&seite=2

 

In order to work, one must manually change that link to

Code: Select all

https://faqs.up.pt/faq/search.html?search=impressao&searchcategory=0&seite=2 

(or

Code: Select all

http://...

 )

The situation was tested in different phpMyFAQ installations - with the same result.

A similar (but much less harmful) behavior continues to exist in 2.6.15 version on the administrative translation interface (already reported - Translation interface : moving to another page - problem ).

Notes

• URL rewrite is active.
• This situation was first detected in version 2.6.14.
• We are (still) using modified templates of an old phpMyFAQ version.
• There was no modification between versions in the webserver’s configuration and in the used templates.

We really tried to solve these problems before posting (even having a lot of active simultaneous tasks at the moment).

Help would be much appreciated (specially on the search results page transition).

We are using:

• phpMyFAQ 2.6.15
• Apache/2.2.3
• PHP 5.3.6RC2 (5.3.5 with phpMyFAQ’s previous version)
• Mysql
• Database Client Version : 5.1.54
• Database Server Version : 5.5.9 (5.5.8 with phpMyFAQ’s previous version)

Please continue the good work on phpMyFAQ.

Kind regards
2011-03-10
pt20100201
.

[Thorsten]

Hi,

I'll check it.

bye
Thorsten

[Thorsten]

Hi,

fixed for 2.6.16: https://github.com/thorsten/phpMyFAQ/co ... eca2dd22e9

bye
Thorsten

[pt20100201]

Dear Thorsten

...
fixed for 2.6.16: https://github.com/thorsten/phpMyFAQ/commit/e2c2fbb40ab70956cf54319ada9f6ceca2dd22e9
...

Thanks for your quick answer.
We made the changes listed on that page and the problem disappeared.

Sorry about replying to you only today.

Kind regards
2011-03-14
pt20100201
.