Thanks McDonald for stepping up to help. You are right, I didn't give much info to help.

I was able to find the source of my problem and fix it, sort of. I'll describe my solution, just in case anyone else is searching for a solution to this problem. Or if anyone has a better solution, please let me know.

I am running a module called Mantis. Search results kicked out by Mantis were being written above my theme. I found a suggestion here that showed me how to remove a module form the Search engine by editing the xoops_version.php within the Mantis module folder.

I found the following code:



and changed it to:



This removed Matis results from my global search. Fortunately I don't need them.

I'm encountering the exact same problem. Did you find a fix?

Only the part in the Search.PHP after

is being displayed at the top of my page.

All I see is

{module name}
article username
article username
article username
article username
show all results

SEARCH BOX

The remaining part of my page is my theme, but the content is empty.


I'm guessing I have a bad template? But which one is it? It seems like all the HTML for output is within Search.PHP.

FIXED!

Thanks again for your help. The solution was to find my PHP.INI file and increase the memory allocation from 8M to 12M.

For anyone else, that encountered this problem here's my solution. Remember I'm not an expert and only fixed it through trial and error. If anyone sees any problems with this solution, please let me know.

I found my php.ini file by creating and uploading a file called show_php_info.php. This file contains the one simple command:



Upload this file to your site and then open up the file. If you upload it to the root of your website, you would just open the url:

http:// yourwebsite.com/show_php_info.php

You'll get a nice long report showing all the settings on your web server. I found out my web host is using PHP version 4.3.10 by doing this. Do a search for "php.ini" and you will find the folder on your server where this file is stored.

Fire up your ftp application again and change to the folder where the php.ini file is.

Download php.ini to your local machine.

Use a text editor to edit the php.ini (I am a huge fan of Notepad++, a free text editor).

Search for the text "memory_limit". In my case I found:



I changed this to:



I uploaded my updated php.ini back up to the server and overwrote the existing file.

And that's it... I thought I would have to figure out how to restart the server (I doubt I can do it). But it fixed the problem immediately.

Good luck, let me know if it works for you!

Joomla does look really nice, they have some very talented graphical designers helping them out.

Personally, I don't think extra load time is an issue. Most people accessing my site are on high speed. And a nice looking site doesn't have to be bulky.

But is Joomla a threat? I don't think so. I've tried it out (or attempted to try it out). And it's not as user friendly or intuitive to set up.

However, I do think that it's attracting a lot of potential XOOPS users because it does look good. And these people don't know any better.

The XOOPS community has some really talented designers. With the upgrade of this site to XOOPS 2.2 I suggest that it should look as good or better than joomla! Hold a contest, offer some prize money, pay a designer... whatever it takes.

Just my humble opinion... :)

Thanks for the info tzvook!

I'll try to see if I can find/edit the php.ini file. I'll give an update later on today.

I'm getting a similar error, see my previous post:

Fatal error: Allowed memory size of 8388608 bytes exhausted

I've still trying to find more info on this, but have been unsuccessful.

with PHPDebugmode on I get:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 11520 bytes) in /var/www/juniper/forum/modules/mantis/core/category_api.php on line 40

When I go to:

http://www.sitename.com/forum/userinfo.php?uid=1

or any member page.


I've tried removing mantis from my system, thinking that it was causing the error. But the error just moves to the next module I have installed, e.g. SmartFAQ.

I've discussed this with my web host, webserve.ca. And they say that this page looks fine from their end.

I've tried this on four different computers with different settings, different locations and different firewalls. I get the same error in Internet Explorer 6.0 and Mozilla Firefox 1.5.

Sorry, I don't know PHP version, or any other version details of the server I am using. If you have any suggestions on how I can find this, I'll post that info here.


I'm looking for any suggestions, help. Or suggested questions/requests to send to my webhost.

Just started encountering this error on my site. Running XOOPS on a shared server so upping the memory in php.ini isn't an option.

Running XOOPS 2.0.13.2

Get an internal server error every time I try to view the profile of a member. If I log out I can view the member's profile as an anonymous user without any error messages.

Background

Error was happening with 2.0.13.1, after playing around with userinfo.php. I was trying to remove anonymous access to member profiles via advice Can I stop guests from viewing registered user profiles?. This hack worked great by the way, anonymous access was denied and redirected back to main index. But registered user access also dissapeared with internal server error. Also had several new members sign up at same time, it's not a big site, now just over 40 members.

updated all files to 2.0.13.2 including userinfo.php.


Any suggestions?

Thanks Mith!

I really appreciate the work you are doing on this. If you need me to test any fixes let me know!

I wish I had an answer for you, but all I can say is "me too".

Just upgraded to 2.2.3 and my activation e-mails are doing the exact same thing with the site URL duplicated twice.

Wow, great news! xcgal is my favourite photo gallery mod. XOOPS Gallery runs a close second for me.

Can't wait for this to come out of Beta.

Was it easy to setup?

FYI for other users clicking on the link you provided, I think you will need to register with their site to read the posting.