Ok, after more tinkering then I care to type out the problem turned out to be the persistent connections option in mainfile.php. I had it set to 1 (the default and the choice if you are 'not sure') but with the failure to connect I turned it off and the problem is gone. I'm not sure why XOOPS looses the connection (does MySQL have a timeout?) but it works fine with XOOPS_DB_PCONNECT=0 so I'm not bothering with it anymore...

Ok...I got enough time to do a roll back to 2.0.5 and I now get this error:

This page cannot be displayed due to an internal error.

If you are the administrator of this site, please visit the XOOPS Troubleshooting Page for assistance.

Warning [PHP]: mysql_pconnect() [function.mysql-pconnect]: Link to server lost, unable to reconnect in file C:\Program Files\Apache Group\Apache2\htdocs\xoops\class\database\mysqldatabase.php line 72
Error [Xoops]: Unable to connect to database in file C:\Program Files\Apache Group\Apache2\htdocs\xoops\class\database\databasefactory.php line 34

I have even tried going back to MySQL 3.21 and the error is still there. So, by rolling back a version it is plain to see that something has changed...

I'm going to try to roll back even further...

It seems odd that it would be a SERVER issue when I have NEVER had the problem before upgrading to the new XOOPS. Also, how could the mainfile.php suddenly become a problem? It has worked ever since I first installed XOOPS and worked 5 seconds ago before I got the error page. As far as the 'too many connections' theory that doesn't hold up in my standalone setup either unless XOOPS goes crazy and needs more then the default of 100 for max_connections in MySQL. In addition, I access the database numerous times for tweaking with PHPMyAdmin (v2.5.5-pl1) and MySQL Control Center (v0.9.4-beta) and have never had any timeout/connection errors.

It almost behaves like a login/timeout issue. If I let it sit for a while and click a link it gives me the error. If I click logout first and then log back in the link works fine.

I should really do a rollback to see if it fixes the problem so I will try that...Maybe XOOPS debug would give a more verbose error message???

I have the same problem and I can guarantee that it is NOT related to a slow ISP. I am running everything on my local machine (W2k, Apache 2.0.44, PHP 4.3.0, MySQL 4.0.18, P4-1.7GHZ) and this error started happening right after the upgrade to 2.06.

I haven't had any time to try a roll back but it seems pretty clear something is up with XOOPS...

If you enter a search and get results in the FAQ section the link which is shown will not take you DIRECTLY to the faq but dumps you at the top of the category page. The actual difference in the link which takes you directly to a FAQ and the results from a search which shows the same FAQ is a 'q' character. Like so:

From search results:

http://../xoopsfaq/index.php?cat_id=1#1

From FAQ section:

http://../xoopsfaq/index.php?cat_id=1#q1

I hacked the xoopsfaq_category.html and xoopsfaq_index.html template files to remove the 'q' and then updated the FAQ module in the admin section.

It works fine for me now...

Someone posted a similar problem covering both the FAQ and the News but I haven't checked on the news end of this...

I noticed this as well...I would think it is a bug. The actual difference in the link which takes you directly to a FAQ and the results from a search which shows the same FAQ is a 'q' character. Like so:

From search results:

http://../xoopsfaq/index.php?cat_id=1#1

From FAQ section:

http://../xoopsfaq/index.php?cat_id=1#q1

Stupid little q...

I hacked the xoopsfaq_category.html and xoopsfaq_index.html template files to remove the 'q' and then updated the FAQ module in the admin section.

It works fine for me now...

I haven't checked into the news problem but I ASSume it would be the same.