1
FullestEmpty
Site was working fine - then Fatal Error for NO REASON (theme.php, line 499)



Help would be very much appreciated.

My site was working perfectly fine. I hadn't edited anything in ages, nor had I logged in for ages.

Then I checked the website after a while and I get the following error:

Fatal error: Call to a member function on a non-object in /home/www/USERNAME/class/theme.php on line 499

I can't access user.php either to log in.

I've searched the forum for similar problems and the only time this problem seems to have occured is after a fresh installation of version 2.2.3. Suggestions for that problem have been to install the Extended Profiles module. However, I think I do have that module installed but I can't log in to confirm or reinstall it.

Would it be possible to reinstall XOOPS whilst retaining the website content and database?

Thanks very much for any suggestions you might have.

FURTHER INFO:
XOOPS 2.2.3 Final
php version 4.4.2
phpMyAdmin - 2.8.2
MySQL - 4.1.20-standard
MySQL client version: 3.23.49

Modules installed:
Standard 2.2.3 profile module,
Content 0.5,
News 1.44,
AMEvents 0.22,
Google 1.10
[I have a few other inactive modules but I can't remember whether I uninstalled them or not ]

2
trabis
Re: Site was working fine - then Fatal Error for NO REASON (theme.php, line 499)
  • 2008/7/26 15:10

  • trabis

  • Core Developer

  • Posts: 2269

  • Since: 2006/9/1 1


The version info is in include/version.php

Also it would be good to give us php version as well as modules you have installed.

3
FullestEmpty
Re: Site was working fine - then Fatal Error for NO REASON (theme.php, line 499)

Quote:

trabis wrote:
The version info is in include/version.php

Also it would be good to give us php version as well as modules you have installed.

Hi,

I've added that info to my first post now.

Thanks.

4
FullestEmpty
Re: Site was working fine - then Fatal Error for NO REASON (theme.php, line 499)

If anyone's interested, I've managed to fix the problem (I hope!).

I re-installed XOOPS 2.2.3 but I kept the old database [i.e. re-uploaded XOOPS files, didn't delete database and went through installation process again].

This allowed me to access my admin area although the error message still existed on the frontpage.

I then updated the System module, uninstalled/installed the Extended Profiles module, and uninstalled unneeded modules.

It seems to be working now. I've a small amount of duplicated info in my database but I can live with that. Also, sometimes I get errors when trying specific tasks with modules, but I just reinstall/update those modules and it works fine.

Cool.

Login

Who's Online

112 user(s) are online (67 user(s) are browsing Support Forums)


Members: 0


Guests: 112


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits