|
codingforsail
|
May 29, 2019 at 2:16 pm
Hi,
My client reports that “sometimes the system crashes”. I have been unable to reproduce this on the small copy I made from a backup file. That is admittedly a development server with few resources but there is just one user.
Can you suggest what kind of server resources you would recommend for a plugin such as EventEspresso? Or what kind of questions you would need answered before you could consider such a question.
Here are a couple of the things they’ve said:
“System crashing mid booking The system crashes regularly during bookings. When this happens it appears as though the booking has not been made and you are taken back to the screen to add the participant details. If you re-enter the details then you end up with a duplicate booking. However, sometimes the system crashes and customers are left with a booking that has no activities on and a zero invoice. This needs to be corrected.”
I’m not sure whether this is related to the crashing or not:
“Bookings Why are bookings being generated that show no activity registrations and therefore no value. If this is done, is it possible to go into this shell and add registrations? At the moment I am having to raise a new booking, but then there is a mismatch between the booking reference that the customer has and the reference that the payment needs to be logged against.”
Please notify registrations@codingforsail.uk when you respond.
Kind regards,
Anita
|
|
Josh
|
May 29, 2019 at 2:20 pm
Hi Anita,
We recommend PHP 7+ and a sufficient amount of RAM. The amount will depend on more than a few factors including number and types of WordPress plugins, the theme, and the amount of traffic.
Since they’ve noticed the crashing happens on bookings, it will be good to check the site’s PHP error logs at the times when these crashes occurred. There may be a clue in those error logs that show what to do to next. e.g. if the error says “PHP Fatal error: Allowed memory size of x bytes exhausted” then the solution will be to bump the memory limit for PHP.
|
|
codingforsail
|
May 29, 2019 at 2:38 pm
Thanks Josh,
They have given me access to the hosting cPanel, so I can check the PHP version and the logs in the morning. (Nearly bedtime here!) At least I’ll know what to look for.
Kind regards,
Anita
|
|
codingforsail
|
May 30, 2019 at 7:06 am
Hi,
I have looked in the error_log and don’t see any errors related to memory. What I do see that is related to EE is:
[26-Aug-2018 23:41:52 UTC] PHP Fatal error: Uncaught TypeError: Argument 2 passed to EEH_Parse_Shortcodes::parse_ticket_list_template() must be an instance of EE_Ticket, null given, called in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php on line 100 and defined in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php:110
Stack trace:
#0 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(100): EEH_Parse_Shortcodes->parse_ticket_list_template(Array, NULL, Array, Array)
#1 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(70): EE_Ticket_List_Shortcodes->_get_ticket_list_for_main()
#2 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(54): EE_Ticket_List_Shortcodes->_get_ticket_list()
#3 /home/essa/p in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php on line 110
[26-Aug-2018 23:42:50 UTC] PHP Fatal error: Uncaught TypeError: Argument 2 passed to EEH_Parse_Shortcodes::parse_ticket_list_template() must be an instance of EE_Ticket, null given, called in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php on line 100 and defined in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php:110
Stack trace:
#0 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(100): EEH_Parse_Shortcodes->parse_ticket_list_template(Array, NULL, Array, Array)
#1 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(70): EE_Ticket_List_Shortcodes->_get_ticket_list_for_main()
#2 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(54): EE_Ticket_List_Shortcodes->_get_ticket_list()
#3 /home/essa/p in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php on line 110
[26-Aug-2018 23:47:29 UTC] PHP Fatal error: Uncaught TypeError: Argument 2 passed to EEH_Parse_Shortcodes::parse_ticket_list_template() must be an instance of EE_Ticket, null given, called in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php on line 100 and defined in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php:110
Stack trace:
#0 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(100): EEH_Parse_Shortcodes->parse_ticket_list_template(Array, NULL, Array, Array)
#1 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(70): EE_Ticket_List_Shortcodes->_get_ticket_list_for_main()
#2 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(54): EE_Ticket_List_Shortcodes->_get_ticket_list()
#3 /home/essa/p in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php on line 110
[26-Aug-2018 23:51:58 UTC] PHP Fatal error: Uncaught TypeError: Argument 2 passed to EEH_Parse_Shortcodes::parse_ticket_list_template() must be an instance of EE_Ticket, null given, called in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php on line 100 and defined in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php:110
Stack trace:
#0 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(100): EEH_Parse_Shortcodes->parse_ticket_list_template(Array, NULL, Array, Array)
#1 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(70): EE_Ticket_List_Shortcodes->_get_ticket_list_for_main()
#2 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(54): EE_Ticket_List_Shortcodes->_get_ticket_list()
#3 /home/essa/p in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php on line 110
[26-Aug-2018 23:52:19 UTC] PHP Fatal error: Uncaught TypeError: Argument 2 passed to EEH_Parse_Shortcodes::parse_ticket_list_template() must be an instance of EE_Ticket, null given, called in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php on line 100 and defined in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php:110
Stack trace:
#0 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(100): EEH_Parse_Shortcodes->parse_ticket_list_template(Array, NULL, Array, Array)
#1 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(70): EE_Ticket_List_Shortcodes->_get_ticket_list_for_main()
#2 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(54): EE_Ticket_List_Shortcodes->_get_ticket_list()
#3 /home/essa/p in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php on line 110
[27-Aug-2018 00:05:25 UTC] PHP Fatal error: Uncaught TypeError: Argument 2 passed to EEH_Parse_Shortcodes::parse_ticket_list_template() must be an instance of EE_Ticket, null given, called in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php on line 100 and defined in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php:110
Stack trace:
#0 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(100): EEH_Parse_Shortcodes->parse_ticket_list_template(Array, NULL, Array, Array)
#1 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(70): EE_Ticket_List_Shortcodes->_get_ticket_list_for_main()
#2 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(54): EE_Ticket_List_Shortcodes->_get_ticket_list()
#3 /home/essa/p in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php on line 110
[27-Aug-2018 09:50:51 UTC] PHP Fatal error: Uncaught TypeError: Argument 2 passed to EEH_Parse_Shortcodes::parse_ticket_list_template() must be an instance of EE_Ticket, null given, called in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php on line 100 and defined in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php:110
Stack trace:
#0 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(100): EEH_Parse_Shortcodes->parse_ticket_list_template(Array, NULL, Array, Array)
#1 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(70): EE_Ticket_List_Shortcodes->_get_ticket_list_for_main()
#2 /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php(54): EE_Ticket_List_Shortcodes->_get_ticket_list()
#3 /home/essa/p in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php on line 110
[22-Mar-2019 12:18:26 UTC] PHP Fatal error: Maximum execution time of 120 seconds exceeded in /home/essa/public_html/wp-includes/formatting.php on line 1597
[22-Mar-2019 12:20:46 UTC] PHP Fatal error: Maximum execution time of 120 seconds exceeded in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/services/collections/Collection.php on line 229
Kind regards,
Anita
|
|
codingforsail
|
May 30, 2019 at 8:37 am
Hi,
I checked in the error log. There is nothing that would suggest memory is being exhausted, and nothing that would imply the system “regularly crashing” as they report.
I see this recently:
[22-Mar-2019 12:18:26 UTC] PHP Fatal error: Maximum execution time of 120 seconds exceeded in /home/essa/public_html/wp-includes/formatting.php on line 1597
[22-Mar-2019 12:20:46 UTC] PHP Fatal error: Maximum execution time of 120 seconds exceeded in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/services/collections/Collection.php on line 229
and then a bunch of instances of:
PHP Fatal error: Uncaught TypeError: Argument 2 passed to EEH_Parse_Shortcodes::parse_ticket_list_template() must be an instance of EE_Ticket, null given, called in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/shortcodes/EE_Ticket_List_Shortcodes.lib.php on line 100 and defined in /home/essa/public_html/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Parse_Shortcodes.helper.php:110
from last August.
Kind regards,
Anita
|
|
Josh
|
May 30, 2019 at 11:44 am
Hi Anita,
The first errors from March would be related to crashing because they’re related to maximum execution time being exceeded. You can contact your host about that.
The other errors are related to an incorrect usage of the ticket selector shortcode where the event ID provided to the shortcode doesn’t match up with any actual event (or it’s pointing to a deleted event). Those would not be related to the site crashing.
|
|
codingforsail
|
May 30, 2019 at 11:16 pm
Hi Josh,
Thanks.
Will bring the max execution time to their attention. Have no idea what they were doing in August to cause those errors.
Sorry about posting twice. The system seemed to tell me that I hadn’t posted the first time.
Kind regards,
Anita
|
|
Josh
|
May 31, 2019 at 6:52 am
Hi Anita,
The first of those replies that included the long strings of error messages was held for moderation because it triggered Akismet’s spam rules.
|
