Return to previous page

Server Errors - by topimr - on WordPress WooCommerce support

This topic has 5 replies, 3 voices, and was last updated 9 years, 11 months ago ago by Eva Kemp

topimr

Participant

January 7, 2016 at 22:06

Good afternoon, how are you? We just launched a site live using the Royal Theme but we keep getting server errors. I made sure to update all plugins as well and the theme. Do you know what could be causing this? Or how I can trouble shoot it? We can give you cpanel access if you need. many time s reload will fix but we can’t have clients not seeing the website.

Please, contact administrator
for this information.

#107039 Copied

4 Answers

Jack Richardson

Support staff

January 8, 2016 at 08:24

Hello,

Server error is related to your server configuration. You should contact your hosting provider regarding this issue.
Perhaps memory_limit value should be increased.

Best regards,
Jack Richardson.

#107061 Copied

topimr

Participant

January 8, 2016 at 19:11

We have tried that. There are constant errors since the theme upgrade?

#107250 Copied

topimr

Participant

January 8, 2016 at 19:17

Here are some server errors from this morning. Visual Composer also crashes sometimes.

] [notice] EACCELERATOR(14605): PHP crashed on opline 377 of main() at /home/boyarsc/public_html/wp-settings.php:163
] [notice] EACCELERATOR(32657): PHP crashed on opline 377 of main() at /home/boyarsc/public_html/wp-settings.php:163
] [notice] EACCELERATOR(23492): PHP crashed on opline 116 of getArrFontFamilys() at /home/boyarsc/public_html/wp-content/plugins/revslider/includes/operations.class.php:765
] [notice] EACCELERATOR(21927): PHP crashed on opline 377 of main() at /home/boyarsc/public_html/wp-settings.php:163
] [notice] EACCELERATOR(16656): PHP crashed on opline 377 of main() at /home/boyarsc/public_html/wp-settings.php:163
] [notice] EACCELERATOR(11464): PHP crashed on opline 377 of main() at /home/boyarsc/public_html/wp-settings.php:163
] [notice] EACCELERATOR(24381): PHP crashed on opline 377 of main() at /home/boyarsc/public_html/wp-settings.php:163
] [notice] EACCELERATOR(24239): PHP crashed on opline 377 of main() at /home/boyarsc/public_html/wp-settings.php:163
] [notice] EACCELERATOR(26484): PHP crashed on opline 377 of main() at /home/boyarsc/public_html/wp-settings.php:163

#107252 Copied

Eva Kemp

Participant

January 8, 2016 at 19:46

Hello,

This is related to server configuration.
Your hosting provider support should explain what those notices mean.
Please refer to these articles:
https://wordpress.org/support/topic/eaccelerator-php-crashed
https://wordpress.org/support/topic/wordpress-keeps-breaking-no-clue-whats-wrong/page/2
https://mu.wordpress.org/forums/topic/1407

Regards,
Eva Kemp.

#107261 Copied
Viewing 5 results - 1 through 5 (of 5 total)