Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Fatal error: Call to a member function main() on a non-object in | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Fatal error: Call to a member function main() on a non-object in

Fatal error: Call to a member function main() on a non-object in

Posted: October 28, 2013 at 4:53 pm

Viewing 5 reply threads


Sam John

October 28, 2013 at 4:53 pm

Hi
We have started getting this error (as below) in one of our WordPress install and have found if we remove Event Espresso the login page is OK.

Fatal error: Call to a member function main() on a non-object in /home/vetnetwo/public_html/wp-includes/functions.php on line 779

It only appears when we try and login via the WP Admin page http://www.vetnetwork.mobi/wp-admin

Just wondering if you have come across this before and if you know of a fix. I updated after the error showed up.

We are using versions;
WP 3.5.1
EE Version 3.1.35.2.P
Espresso Ticketing Version 2.0.10.2.p

Thanks
Sam


Dean

  • Support Staff

    •

October 29, 2013 at 2:48 am

Hi Sam,

Event Espresso does not affect the login screen, so it is likely a different type of conflict. Looking around the web, this error has occurred before and without Event Espresso being involved.

Pinning down the exact conflict is hard with the information provided, but from what I have read it seems to be a coding problem within the theme, in respect to where files are required/included.


Sam John

October 30, 2013 at 12:06 am

Thanks – have contacted the theme creator.


Josh

October 30, 2013 at 11:32 am

Hi Sam,

You can rule out whether it’s a theme issue or not by switching to the default WP theme. Also, it may help to install a fresh copy of WordPress from wordpress.org.


Sam John

October 30, 2013 at 4:59 pm

Hi
Yes I have done this and turned off all plugins and all was OK – then started activating them all including the theme. When I re instate Event Espresso the error occurs. So I presumed it was an EE issue or conflict. I have also emailed the template creator to see if they have come across the same issue.


Anonymous

October 31, 2013 at 2:37 am

Hi Sam,

Have you made any modifications to Event Espresso at all?

If you de-activate all plugins and have only EE and twentytwelve active is the outcome the same?
Viewing 5 reply threads

The support post ‘Fatal error: Call to a member function main() on a non-object in’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Anonymous 11 years, 3 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server