Home Learn More Purchase Knowledge Base Support Contact

Community Forums

KBPublisher Forums » KBPublisher General discussion

Fatal Error

(10 posts)
  • Started 3 years ago by simonphp
  • Latest reply from simonphp

No tags yet.


  1. simonphp
    Member

    I get this following error intermittently when trying to access the KB frontpage.

    Fatal error: Call to a member function Execute() on a non-object in kb/admin/modules/setting/inc/SettingModel.php on line 47

    My temporary fix each time this occurs is to remove the cookie. Any ideas how I can fix this issue?

    Posted 3 years ago #
  2. onesign
    Key Master

    How often it occurs?
    Would you please give more details.
    What is your configuration? Browser? PHP? Server?

    Posted 3 years ago #
  3. simonphp
    Member

    It occurs multiple times through out the day but at odd intervals. It is on an Apache Server, PHP 4, Firefox, I don't know you mean by configurations.

    Do you think another software may have the same cookie name that is overwriting KBPub's cookie?

    Posted 3 years ago #
  4. onesign
    Key Master

    >> Do you think another software may have the same cookie name
    >> that is overwriting KBPub's cookie?

    I do not think so. But ....
    All of this looks strange.

    And I can't see on line 47 any Execute() function

    Do you still have this problem?
    Can you repeat it?

    Posted 3 years ago #
  5. simonphp
    Member

    That's odd, I posted line 47 that shows the Execute() function and now it's gone. I'm guessing you took it down because I posted code. Sorry if that troubled you.

    I hope you got to look at it before you pulled it down. I'm still experiencing this error. Any help is appreciated.

    Posted 3 years ago #
  6. onesign
    Key Master

    What version we are talking about? 2.0.1 I believe?
    Where do you use it, inside any CMS? Are there any other $this->db variable that somehow interrupt it?
    Really strange...

    Posted 3 years ago #
  7. simonphp
    Member

    Yes, I use 2.0.1. I don't use it inside any CMS. That's the only one so far that interrupts it. The only way to get it to temporarily work is to remove the cookie. But it will do it again at least 3 times a day at different intervals.

    Posted 3 years ago #
  8. onesign
    Key Master

    What cookies do you have when it stop working? You can check it with Firefox.

    Posted 3 years ago #
  9. simonphp
    Member

    PHPSESSID - That's the cookie name.

    Posted 3 years ago #

RSS feed for this topic

Reply

You must log in to post.

© 2008 Double Jade LLC | customer.service@kbpublisher.com