Event Submit Fatal error string in browser

WordPress Event Management, Calendars & Registration Forums Report A Bug Event Submit Fatal error string in browser

This topic contains 5 replies, has 2 voices, and was last updated by  Dennis Caffey 9 years, 3 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #18477

    Hi,

    I’m having an issue when submitting an event into the database. The event submits fine into the
    system (creates the /events/ page and details are dropped in, including any custom fields… etc..

    The email responses are looking good

    What happens is this error in the browser instead of a redirect after the form is submitted
    NOTE: I tested this for both a redirect to another page and for staying on the form with a success message:

    Fatal error: Call to a member function format() on a non-object in /home/lv2015x/public_html/wp-content/plugins/event-organiser/includes/event-organiser-utility-functions.php on line 36

    Not sure how to address this… any help is very welcome

    Best,
    Dennis

    Dennis Caffey
    #18486

    Hi Dennis,

    Unfortunately that error is fairly ‘upstream’: at some point the plug-in is trying to retrieve a string representation of a DateTime object, but the object it has is not a DateTime object. This error here is just the symptom – the real problem is what that object is not a DateTime instance.

    It would be helpful to know the trace which leads to the error. For this I’d recommend adding the following to line 33:

    if ( ! ( $var instanceof DateTime ) ) {
         echo wp_debug_backtrace_summary();
    }
    

    If you need any assistance with this, I’d be happy to help.

    Stephen Harris
    #18501

    Hi Stephen,

    Thank you for your input and time on responding..

    I did add that string in the php file and this is what now is generated in the browser after submitting the “Submit Event” form:

    require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, EO_Event_Form_Controller::listen_for_submission, EO_Event_Form_Controller::form_submission, do_action(‘eventorganiser_validate_fes_form_submission’), call_user_func_array, _eo_es_process_event_submission, do_action(‘eventorganiser_fes_submitted_event’), call_user_func_array, eventorganiser_fes_email_admin_post_submission, eventorganiser_fes_email_form_submission_list, eo_format_datetimerequire(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, EO_Event_Form_Controller::listen_for_submission, EO_Event_Form_Controller::form_submission, do_action(‘eventorganiser_validate_fes_form_submission’), call_user_func_array, _eo_es_process_event_submission, do_action(‘eventorganiser_fes_submitted_event’), call_user_func_array, eventorganiser_fes_email_admin_post_submission, eventorganiser_fes_email_form_submission_list, eo_format_datetimerequire(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, EO_Event_Form_Controller::listen_for_submission, EO_Event_Form_Controller::form_submission, do_action(‘eventorganiser_validate_fes_form_submission’), call_user_func_array, _eo_es_process_event_submission, do_action(‘eventorganiser_fes_submitted_event’), call_user_func_array, eventorganiser_fes_email_submitter_post_submission, eventorganiser_fes_email_template_tags, EO_FES_Email_Template_Tag_Parser->parse, preg_replace_callback, EO_FES_Email_Template_Tag_Parser->parse_tag, eventorganiser_fes_email_form_submission_list, eo_format_datetimerequire(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, EO_Event_Form_Controller::listen_for_submission, EO_Event_Form_Controller::form_submission, do_action(‘eventorganiser_validate_fes_form_submission’), call_user_func_array, _eo_es_process_event_submission, do_action(‘eventorganiser_fes_submitted_event’), call_user_func_array, eventorganiser_fes_email_submitter_post_submission, eventorganiser_fes_email_template_tags, EO_FES_Email_Template_Tag_Parser->parse, preg_replace_callback, EO_FES_Email_Template_Tag_Parser->parse_tag, eventorganiser_fes_email_form_submission_list, eo_format_datetimerequire(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, EO_Event_Form_Controller::listen_for_submission, EO_Event_Form_Controller::form_submission, do_action(‘eventorganiser_validate_fes_form_submission’), call_user_func_array, _eo_es_process_event_submission, do_action(‘eventorganiser_fes_submitted_event’), call_user_func_array, eventorganiser_fes_email_submitter_post_submission, eventorganiser_fes_email_template_tags, EO_FES_Email_Template_Tag_Parser->parse, preg_replace_callback, EO_FES_Email_Template_Tag_Parser->parse_tag, eo_format_datetime
    Fatal error: Call to a member function format() on a non-object in /home/lv2015x/public_html/wp-content/plugins/event-organiser/includes/event-organiser-utility-functions.php on line 38

    URL:
    http://lasvegasfestivalsandmore.com/add-event/#eo-fes

    => I’ve now pulled that debug string down you sent as it was generating the code above across multiple locations (backend and frontend)

    Please advise…and if you need access to the site .. I’m happy to set you up with Admin control and/or an FTP access…etc..
    => If you want to simply setup a basic subscriber account to look over the submissions form and the site … feel free to click on the big eyesore of a CTA top right in the header…

    Thank you again for your help

    Best Regards,
    Dennis Caffey
    Project Manager

    Dennis Caffey
    #18507

    Hi Dennis,

    I’ve just sent you an e-mail regarding this.

    Stephen Harris
    #18551

    Just an update for anyone else experiencing this problem. This was found to be a bug with the %submission_date% email placeholder tag. And update shall be released shortly.

    Until that release it is recommended to remove that tag from your e-mail notification settings.

    Stephen Harris
    #18571

    Dear Stephen,

    Thank you so much for your help with correcting this bug. Our site is now working properly and we can mover
    forward with other development. I will be recommending your plugin and addons to folks I engage with.

    Thanks again for you help.. 😉

    Dennis

    Dennis Caffey
Viewing 6 posts - 1 through 6 (of 6 total)
To enable me to focus on Pro customers, only users who have a valid license for the Pro add-on may post new topics or replies in this forum. If you have a valid license, please log-in or register an account using the e-mail address you purchased the license with. If you don't you can purchase one here. Or there's always the WordPress repository forum.