Question Search function in 1.5.3 doesn't work

Looks like more work. I was thinking that going to 1.5.3 from 1.0.10 might get rid of these problems with the search. As seen here I am also getting the page:



I can't even show you any debug info because the screen only shows what the image above shows.


I do not get this error when using my XAMPP localhost server but do on my live webserver.

sozzled wrote:

If this were my problem, I would create a fresh website, using a "vanilla-flavoured" Joomla 1.5.11 installation, install Kunena 1.5.3, make no changes to the configuration settings, and test my problem scenario.

I hate to jump into a 1.5.3 discussion with a 1.0.10 problem, however I feel these MAY be related in both versions.

Sozzled, I started the process you are quoted with above. I installed only a fresh 1.5.11 joomla and 1.0.10 kunena and nothing else. I then took the fixed class.kunena.php from the post #17418 because if I did not that error still occurred when doing searches.

After doing this I still get the broken page that looks like so:



Below is the complete information of the server its running on:
PHP Built on: Windows NT LEETSUPE-9I86FE 5.2 build 3790
Database Version: 5.0.45-community-nt
Database Collation: utf8_general_ci
PHP Version: 5.2.5
Web Server: Apache/2.0.63 (Win32) PHP/5.2.5
Web Server to PHP interface: apache2handler
Joomla! Version: Joomla! 1.5.11 Production/Stable [ Vea ] 03-June-2009 03:30 GMT

Feel free to experience this for yourself.
Go to the website by CLICKING HERE . The username and password are both "testuser" and you'll see it.

Now to really befuddle the searching for info and fix here, like I mentioned before when I run this site on my local server via xamp, I do not get this broken screen. To compare server info look below:

PHP Built on: Windows NT GMYLAPTOP 5.1 build 2600
Database Version: 5.1.30-community
Database Collation: utf8_general_ci
PHP Version: 5.2.8
Web Server: Apache/2.2.11 (Win32) DAV/2 mod_ssl/2.2.11 OpenSSL/0.9.8i mod_autoindex_color PHP/5.2.8
Web Server to PHP interface: apache2handler
Joomla! Version: Joomla! 1.5.11 Production/Stable [ Vea ] 03-June-2009 03:30 GMT


I know the easy answer here someone will say is, upgrade your apache, mysql, and php and all will be fine. But I would prefer we maybe find an alternative answer to fix this. It would be a challenge for my group to do this to our server right now. I really hope there is another solution with a file edit fix.

i can confirm that search function in K1.5.3 still WORKS here..

even after upgrade of..
J1.5.10 to 1.5.11, CB1.2 to 1.2.1, K1.0.9 to 1.5.3

bytebandit01 wrote:

i can confirm that search function in K1.5.3 still WORKS here..

I am in the other direction. I can confirm now, not only with 1.0.10 kunena BUT ALSO WITH Native Kunena 1.5.3 which I installed for this test, I am STILL getting the broken screen on the live server, but it works fine on the localhost xamp server.

See the live server and localhost xamp server and details in the above post #21202

This is my Vanilla2 server, same credentials as above: Click here for website running native 1.5.3 kunena. .

Kunena requires PHP >= 4.3.0 recommended >= 5.0.0 and MySQL >= 5.0.0 recommended >= 5.0.0 which both of my servers are within. There is no requirement for apache and I don't know if there is one or not but its not posted but both are at some version over version 2 as listed in my post above.

At this point I'm praying we are on a path to solution other than having to upgrade server services on our box.

Excellent work itgl72. There's a very high - 99.9% - probability that the fault lies with your server and not with Kunena.

Please check if you've renamed your htaccess.txt file to .htaccess

Please check if you've turned on Joomla SEO.

Well on the original website that had the issue running the 1.0.10 kunena, that site has ".htaccess" in its root folder. I have SEF to NO, mod_rewrite to YES, add suffix to NO.

On the vanilla website running both 1.5.3 and 1.0.10 I have it at htaccess.txt and I have SEF, mod_rewrite, and add suffix all to NO.



Tell me, what is the optimal setup for the htaccess and the SEO settings in config that I can try?