Quote:

Hi.


This is what I find under two error logs for the server. It seems that every time there is a query that times out it is the wiwimod module that does it.

I don't know how to check whether the user database tables are corrupted.

I did not want to fool with it too much until I have rebuilt the site in a different folder or on a new server using a new MySQL database, for fear of losing even the admin profile, I guess.

I do know that I am having some trouble with the templates db. Like there is one template in the content module, if I try to edit the working template file, it tells me that it does not exist, but I know it does because the modifications on that template that are different from the default template are still being rendered in the pages of the site, even after clearing templates_c folder.

I guess I should probably get rid of or reinstall wiwimod. I was using that as a base for a lot of the content of the site and it has over 5500 files in it. So, that is where the XOOPS engine is getting bogged down apparently.

I was suspicious also of the server config, tho, because I had this whole setup on two other webhosts in exactly the same config with MySQL 4.0/4.1 and it worked perfectly and never timed out on the other servers. (Moved the site for reasons unrelated to this problem.)

This engine was installed by fantastico, which I have used often enough, but I also have installed it myself before, so I don't know if that makes any diff or not. I want to mirror the whole thing on another server. Just now am a bit tired, it's a lot of work to set it up, what with uploading all these different modules I have installed, but I guess I could just install the XOOPS engine with the wiwimod and try that out.

Greetings
Glogo

Hi

Has anyone noticed that calling this page invokes a particularly inefficient script which tends to use up a lot of cpu time? My host has a rather low time-out for processes and whenever I click on any link to show userinfo my whole site goes down while the MySQL server reboots.

I am new to XOOPS and know very little about php-mysql.
Using 2.0.16 on Apache 1.3.37 with php 5.1.6 and MySQL 4.1.21.

I had been able to fix this at one point by de-activating some modules when I noticed a fatal error. The only way I was able to get it to even load to report that much was to first click on the user menu "edit profile" button, from there then go to the "view profile". If I click on user profile first, the script times out and I get an ugly grey screen telling me I have been very, very bad and used up more than 20% of the cpu capacity. That screen lasts for about 6-8 minutes and the whole site goes down, including other folders with flat files, which is rather disastrous.

I thought I had gotten this fixed, then it started again. So, I was trying to edit system_block_user.html and replace

That seemed to work for a few minutes. Then I wanted to change something and the whole thing got discombobulated and refused to work at all. I could not access my site and had to disable the user menu. After disabling the user menu, all was well. Anyway, it was a "dirty" fix, but I need to get the site in production soon, so I figure, okay, we will sort this later. But now I notice that some script that has to do with userinfo.php is still causing an overload.
After the server times out and reboots, I can access the page, no problem and it does not give any fatal error, just the usual notices and so on.



Another thing happened. Yesterday, I tried to update a password on a sample profile, and it deleted the whole login.

I wonder if I can get around this by installing a different profiles module or something. But I have never had success using that module. It always seemed to crash my site.

Thanks for any help.

Greetings
Glogo