Recently my server went down & when it came back, all of my sites returned this error:
Fatal error: Call to a member function on a non-object in /home/mine/public_html/kernel/config.php on line 222
Unknown Condition []: in file line
as documented in the FAQ here.

I wrote my host & waited it out, & the next day most of my sites had been returned to functional.
I don't believe my host got my email though... so I doubt he reconciled the Zend issue...

Anyway, the site I have the most traffic on didnt come back. It still gives me the fatal error, as you can see @ http://www.toolunity.com

My host seems unreachable, so I must resolve this myself, it seems. Hopefully someone can help.

If all my sites returned the fatal error & then 9/10 came back w/o issue, whats the anomaly?
The one that is still down was not as current as the rest, I think - I don't even remember what version its runing. Maybe 2.0.4 ...the rest of my sites are 2.0.9.
All my sites are using the IPB module/hack.

I'm thinking... maybe... do a blind upgrade, overwriting the older files with 2.0.9 or better & hope for the best?
Or would this work at all?

Any ideas or insights are appreciated :)

have you check your homepage module ? or blocks ?

Hmm?

Even admin.php returns the fatal error. Any ideas?

Quote:
Unless you can manage the entire server, I don't think this is feasible.

Call the host, email the host, visit the host, call the police. Whatever. This is - until the host proves otherwise - a case of zend optimiser conflict with php version. And if your host is too slow to react, I would recommend that you change host instead of trying to work around it - which you cannot.

Thanks for the reply Mith, I knew you would be the one to come to my rescue on this one. Contacting my host is somewhat problematic at this juncture, but I am considering relocation as soon as I can make a good upwads move.

I just don't understand why only 1 of 10 XOOPS sites on the same server would suffer permanently while the others recovered - would you presume this is because of the older XOOPS version? Besides the volume of traffic and data on that site, the version seems the only variable. Toolunity has always been somewhat unstable for one reason or another, suffering several complete failures over the years - usually due to mysterious server side errors.
I did manage to get into the IPB Admin CP for the site, but attempting to "repair tables" just returned a long list of strange errors. Notice that http://www.toolunity.com/modules/ipboard/admin.php still exists, while the rest of the site renders white error pages. Odd.

Would it be possible to export the database & import it to a fresh install & retain the data, or would there be [XOOPS] version issues?

Thanks for your help :)

i'm not sure of a db change from XOOPS 2.0.4, mith could probly tell you tho..

other than that there shouldn't be a problem in upgrading. but as u say 2.0.4, it's most likely your x-ipb version would not work.. you may have to grab the latest 1.4Ha version (for XOOPS 2.0.10) and then the latest x-ipb core update for XOOPS 2.0.13 if u go to XOOPS 2.0.13.

but you're best having an actual working site to do the upgrade from..

Since XOOPS 2.0.3 (if I recall correctly) there have been no database changes to the core. So if you upgrade the core, your members etc. should remain intact with your XOOPS 2.0.4 data.

You could try uploading it to another domain (one of those that work), copying the database too, and see if it's a setting on that specific account or not...

Herko