I have been lurking and reading everyone's trouble with 2.2. I told myself that I was not going to upgrade any of my sites untill all of the issues were fixed. Then I thought why not at least try it and see how it goes not only to provide feedback on how it went for the people here at XOOPS but to give my users the best of what is out there. Well I upgraded and now I cannot access the site that I did. Every page leads to a white screen. I cannot even turn on debug because I can't access anything! So now I am stuck with one of my sites broken which myself and my users put a lot of time and effort in.

I am very disapointed in this release. It seems as if it was thrown together just to make a release date or a delayed release date. I am also disapointed in the response that the bug reports have gotten from the dev team. I have seen long standing members of this community report bugs only to get ignored or be told it will be fixed in the next release. Some people have even been banned or have been ridiculed (sp?) for reporting bugs and slamming XOOPS for this buggy release.

Xoops has been hurt badly by this release and the way that the bugs have been handled in my opinion. Just think about the new XOOPS user that found us and downloaded 2.2 for the first time. What do you think they thought of XOOPS after this? I am assuming that any smart webmaster deleted the install and went on to test the next CMS that actually functions. I know I would have if this was my first taste of Xoops.

So to get back to my problem. Where do I go from here? How do I get my site back? Any suggestions?

first point...before installing new system new XOOPS new anything make an backup just in case you have problems like you have now:)
if you have backed up you can easily put back your backup and you`re done...without no breaking of hearts..

Does this help?

https://sourceforge.net/tracker/index.php?func=detail&aid=1247454&group_id=41586&atid=430840

Quote:

Thanks Dave it worked!

Stupid question .... where exactly do I find the xoops_config file???

Thanks
Peter

That is refering to a table in the database.

Thank you ...

I actually had to change the "1" to "0" to get it to work. My site seems fine now. WHEW!?!?!?!

and it may not start with 'xoops'.

substitute 'xoops' with your own database prefix and you should find it

edit: too late hehe

make sure you disable gzip compression, then you can turn debug off again.

Herko

Thanks Jim ... Rowdie ... & Herko

The assist is greatly appreciated.

Thankfully, I don't use the gzip

Peter