|
mblair
|
February 10, 2014 at 4:59 pm
Uh, oh. I deactivated Ver. 3 and installed and activated Ver. 4. I moved everything over via your handy tool. Unfortunately, I am getting the following Fatal Error message when I try and look at my website now.
Fatal error: Call to a member function is_set() on a non-object in /home4/mblair/public_html/motorsdrivestraining.com/wp-content/plugins/event-espresso-core-reg/core/EE_Module_Request_Router.core.php on line 102
Any ideas what went wrong or how to fix it?
|
|
Seth Shoultes
|
February 10, 2014 at 5:12 pm
@mblair were there any errors during the migration?
|
|
Seth Shoultes
|
February 10, 2014 at 5:17 pm
@mblair I talked to one of the developers about this issue. He said it sounds like there’s another plugin or something interfering with EE and removing the action where we setup the request handler. Can you try deactivating other plugins and find if there is one that conflicts?
|
|
mblair
|
February 10, 2014 at 6:40 pm
Back at work now. I deactivated plugins and found the culprit. It is the CalPress Pro plugin. http://www.calpresspro.com/ I need that plugin for other training calendars. 🙁
Could there be a work around?
|
|
Josh
|
February 10, 2014 at 7:38 pm
Hi mblair,
If we can get a copy of calpresspro we may be able to find a fix. Is this something you can send? If so, you can send it to support@eventespresso.com.
|
|
mblair
|
February 10, 2014 at 7:47 pm
@josh I just sent it. Thanks!
|
|
Seth Shoultes
|
February 10, 2014 at 10:06 pm
@mblair thanks for sending over a copy of the CalPress Pro plugin. I am seeing the same error you have reported. Unfortunately, we cannot support conflicts with third party plugins. However, because we have seen a similar error, with another plugin that we submitted a patch for (https://github.com/bradt/wp-migrate-db/pull/43), I have sent this over to our developers to take a look at.
You might pass the link I posted above to the CalPress Pro plugin developer to look at, since it looks like an issue that will may to be fixed in that plugin to prevent similar incompatibility issues with other plugins.
I hope that helps.
|
|
Carl Bendorf
|
February 11, 2014 at 12:47 pm
I’m having a similar issue as MBlair in that deactivating EE3 and activating EE4 results in the following error message on my site: Fatal error: Call to a member function is_set() on a non-object in /hermes/waloraweb035/b2371/moo.wildfinchfarmcom/youngiowabirders/wp-content/plugins/event-espresso-core-reg/core/EE_Module_Request_Router.core.php on line 102
I deactivated ALL of my plugins except EE4 and still get the same message. I then activated all my plugins and deactivated EE4 and the message went away and the site works normally?
Help?
|
|
Seth Shoultes
|
February 11, 2014 at 1:06 pm
@Carl the developers are hard art work fixing the issue. We sold have an update out soon.
|
|
Josh
|
February 11, 2014 at 1:13 pm
Hi Carl and @mblair,
One of the developers has come up with a possible solution if you are willing to test it?
If so, you can try the steps available within this Gist:
https://gist.github.com/nerrad/8936298
Please note – this may not be a permanent or full solution but will help isolate if this is contributing to the issue you reported until the main developer for this area of Event Espresso can look into the system further.
|
|
mblair
|
February 11, 2014 at 1:16 pm
@josh, I would love to help test but I’m a marketing person. LOL I read the steps on Gist and have no idea what it means. Everything takes me 10 times longer because I learn by trial and error. If you can translate that and tell me what I need to do, I would be happy to test it.
|
|
Garth
|
February 11, 2014 at 1:26 pm
I’ve split this discussion from the main EE4 announcement to its own topic: https://eventespresso.com/topic/calpress-pro-plugin-conflict/
|
|
Carl Bendorf
|
February 11, 2014 at 1:40 pm
OK, I did the fix you outlined in Gist above which seems to have fixed the prior error message but now the EE event page AND other pages on my website have an EE related error message overlaid on them. See http://www.iowayoungbirders.org/events/young-birder-weekend/
|
|
Josh
|
February 11, 2014 at 1:53 pm
Hi Carl,
If you’re going to use EE4 beta on a public facing site (really any public facing site, ee4 or not) Error display should be turned off.
Usually you can set error display to off by adding this line to your wp-config.php file:
@ini_set( 'display_errors', 0 );
You’ll also want to be sure that WP_DEBUG is set to false.
|
|
Josh
|
February 11, 2014 at 1:54 pm
@mblair We’ll be releasing an update that you can update your website to shortly.
|
|
Carl Bendorf
|
February 11, 2014 at 1:55 pm
I’ve turned off the EE4 plugin since it’s adding error messages to all my live site pages. Attached are two screensnaps showing the errors. and
|
|
Dean
|
February 12, 2014 at 1:06 am
Hi Carl, your message cut short and there were no images attached.
|
|
Carl Bendorf
|
February 12, 2014 at 7:41 am
Sorry, here are the images I hope.
|
|
Carl Bendorf
|
February 12, 2014 at 7:42 am
trying yet again:
http://www.iowayoungbirders.org/?attachment_id=3975
http://www.iowayoungbirders.org/?attachment_id=3976
|
|
Josh
|
February 12, 2014 at 7:46 am
Hi Carl,
If those errors appear will all other plugins deactivated, can you send a copy of your WordPress theme to support@eventespresso.com so the developers can investigate this further?
|
|
Carl Bendorf
|
February 12, 2014 at 7:50 am
Sent. Thanks, Josh.
|
|
mblair
|
February 12, 2014 at 7:53 am
@josh, should I continue to bug CalpressPro guys about a fix or wait until your update?
|
|
Garth
|
February 12, 2014 at 9:08 am
Hi mblair,
We released 4.1.1 this morning which includes a fix for CalPress (and similar plugins). Please update and let us know if you still have the same issue.
|
|
Garth
|
February 12, 2014 at 9:25 am
If your WordPress site is not showing that there is an update, you can save the “Your Organization” settings tab to manually check for the update (as long as you have a valid support license key).
|
|
mblair
|
February 12, 2014 at 9:29 am
It’s working perfectly! I did show a notification but had to install the old fashioned way because I’m using my license key on my old site. What I’m working on with this is the new site which I will be launching soon. Awesome support! Thank you so much for the quick response to my issue!
|
|
Josh
|
February 12, 2014 at 10:13 am
Thanks @mblair!
|
|
Josh
|
February 12, 2014 at 10:14 am
@carl,
Can you try updating to the latest Event Espresso 4 release? I loaded up your theme and the only PHP errors that I’m seeing are from your theme.
|
|
Carl Bendorf
|
February 12, 2014 at 10:25 am
OK, updated to latest release. seems to be working fine except there are 3 or 4 red * at the top of each page. I did change the error message setting in the wp confi file but haven’t yet change the debug option. Would that be it?
|
|
Carl Bendorf
|
February 12, 2014 at 10:35 am
Josh, I’ve also now set the debug to false and am still getting three red asterisks near the top of every page. If I deactivate EE4, they go away. I’ve reactivated EE4 so they are present for now if you have time to take a look: http://www.iowayoungbirders.org/about/
Otherwise, it’s looking good.
|
|
Josh
|
February 12, 2014 at 10:51 am
Hi Carl,
I’m glad it’s working better now. I’ve sent a note to one of the developers about the little red x’s displaying on the front end. Now that we have a copy of the theme that should help us figure out what’s going on.
In the meantime you can hide those by adding this bit of CSS to your custom stylesheet:
.close-espresso-notice {
display:none;
}
|
|
Carl Bendorf
|
February 12, 2014 at 10:59 am
Thanks, Josh, that did it.
|
