1
davidthomas1
Admin lockout - fatal error

hmmm.

I'm getting a fatal error when I try to login.

Here's the message:

Fatal error: Call to a member function on a non-object in public_html/include/functions.php on line 145


Here's line 145 from functions.php

function xoops_refcheck($docheck=1)
{
    return 
$GLOBALS['xoopsSecurity']->checkReferer($docheck);
}


Can I disable this check? Why is it causing a fatal error?

any advice would be much appreciated.

I recently upgraded from 2.0.13.1 to 2.0.13.2
みんなちがってみんないい。

XOOPS 2.0.13.2

2
davidthomas1
Re: Admin lockout - fatal error

No response so far... must be a tough one!

I tried re-uploading the include/functions.php file and the class/xoopssecurity.php files but the problem persists.

I can disable that referrer check in that file and login but is that a safe thing to do?

Is there a risk of a XSS attack with the referrer check disabled?

any other advice would be appreciated.
みんなちがってみんないい。

XOOPS 2.0.13.2

3
davidthomas1
Re: Admin lockout - fatal error

Odd. I get a fatal error when logging in and no one knows the solution? surely someone else must have had this problem.

Ok. This is a last attempt post to get a solution from the peoples or else I'll just comment out the offending line of code.

anyone?
みんなちがってみんないい。

XOOPS 2.0.13.2

4
McDonald
Re: Admin lockout - fatal error
  • 2005/11/1 0:07

  • McDonald

  • Home away from home

  • Posts: 1072

  • Since: 2005/8/15



5
davidthomas1
Re: Admin lockout - fatal error

Thanks for your reply McDonald.

I did search the forums prior to posting this thread and saw that thread.

They had two problems

1) Fatal error when logging in (same as me)
2) Custom blocks not showing (I don't have this problem)

The thread only solved the blocks problem, not the login problem, as far as I'm aware.

So, still not sure about what to do...
みんなちがってみんないい。

XOOPS 2.0.13.2

6
davidthomas1
Re: Admin lockout - fatal error

Thank God, I solved it - FINALLY!

There must be some bug in the upgrade path to 2.0.13.2

I uploaded all the files (full version) and spent some time tweaking the site to get it back to normal.

I can now login normally.

phew
みんなちがってみんないい。

XOOPS 2.0.13.2

7
rowdie
Re: Admin lockout - fatal error
  • 2005/11/1 8:21

  • rowdie

  • Just can't stay away

  • Posts: 846

  • Since: 2004/7/21


You only upgraded from 2.0.13.1 to 2.0.13.2 and had this problem? Which package did you use? (zip/tar.gz)

Do you know if it was only happening when the admin tried to log in, or all registered users?

It's good news that you managed to solve the problem

8
davidthomas1
Re: Admin lockout - fatal error

Sure did. It was just a simple incremental upgrade, and then this fatal error.

I only tried logging is as admin and got the error. I assume it would be the same for other users as the problematic line was just a generic referer check.

Last week, I could log in fine, then, after the upgrade, I had that fatal error problem. I tried uploading the patch again in case of an FTP error but the problem persisted.

After uploading the full version, it's working fine, however, I had to:

1) Redo my custom main menu template back after it was wiped. (I used a backup, copy and pasted)
2) Edit my theme.html file to get the logo etc.. correct.
3) Patch the common.php file to keep the x-language module working.

Other than that it was standard. When uploading, I took out all the module file, except the system module for the upgrade. I also removed mainfile.php to keep the existing one.

anyway, it's all working. I hope my solution can help someone else too.

At the end of the day, I love xoops. It's a great system. Even when there is the odd glitch, it's fun figuring out the solution.

みんなちがってみんないい。

XOOPS 2.0.13.2

Login

Who's Online

248 user(s) are online (168 user(s) are browsing Support Forums)


Members: 0


Guests: 248


more...

Donat-O-Meter

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

Latest GitHub Commits