Support

July 9, 2012 at 8:34 am

Do any of your questions have a , in them?

July 9, 2012 at 9:44 am

(that should be phpinfo() not php_info() 🙂 )

My concern was more the cause of the error itself, though maybe it’s just that this is a certain former developer’s horrible spaghetti code…

• This reply was modified 11 years, 9 months ago by  Chris Reynolds.
• This reply was modified 11 years, 9 months ago by  Chris Reynolds. Reason: my >.< emoticon was cutting off at the end of the line... >

July 9, 2012 at 10:06 am

You can try adding this to your functions.php to disable strict mode:

 /**
  * disable php strict mode
  * @author Chris Reynolds
  * @link http://stackoverflow.com/questions/1248952/php-5-disable-strict-standards-error
  * disables strict mode but logs messages
  */
 function disable_strict() {
    ini_set('display_errors', '0');     # don't show any errors...
    error_reporting(E_ALL | E_STRICT);  # ...but do log them
 }
 add_action ('after_setup_theme', 'disable_strict', 0);

I’ve actually got this running on this site.

July 9, 2012 at 10:09 am

There were changes made to that file between 3.1.15 and 3.1.24, but this is the first problem as a result that I’ve heard of. I will do some testing locally and see if I can duplicate the issue with strict mode on.

In the meantime, try adding the code I posted above to your functions.php file.

• This reply was modified 11 years, 9 months ago by  Chris Reynolds. Reason: added temporary fix

July 9, 2012 at 10:16 am

You should still be able to see errors and warnings in the server’s error log.

July 9, 2012 at 10:56 am

If there’s a fatal error on the page, your page won’t load at all, you’ll just get a white screen or an Internal Server Error. And in that case, this function would be handy, because you could just comment out the last line like so:

//add_action ('after_setup_theme', 'disable_strict', 0);

and then you can see what’s causing the error.

Everything else is just notices and warnings, which — with the code added above — will get appended to the php.log that is stored on your server. If you don’t have immediate access to your error logs (or don’t know where they are or how to get to them) you can contact your host and they should be able to help you out there.

July 9, 2012 at 11:17 am

Try setting “Full registration information” for the additional attendees, then check off the group for the additional attendees. If this additional question is in the personal information group, move it to its own group.

July 9, 2012 at 12:49 pm

I’m not able to reproduce this on my test installation. Check your payment settings in Event Espresso>payment settings and make sure that the bypass payment overview page option is set to no. Then check the default payment status in Event Espresso>General settings and the default payment status for the event. These should be set to either pending or incomplete.

July 9, 2012 at 1:02 pm

Which payment options are active?

July 9, 2012 at 1:06 pm

Try deactivating all non-ee plugins, and if that does not help, try uploading a fresh copy of Event Espresso. I’m not able to reproduce this on two installations. (one is using PayPal, the other is using Invoice)

July 9, 2012 at 1:30 pm

It’s possible, you’ll need to fill out an update request form: https://eventespresso.com/contact/update-request/