7.3.4 Upgrade worked, but front-end not showing

Hi!

I followed the instructions here: https://www.boonex.com/trac/dolphin/wiki/7.3.3-7.3.4 exactly.  As well as the instructions at the bottom of the upgrade page. 

It seemed to work. my admin dashboard is working fine, the DOLPHIN 7.3.4 is showing at the top.

But My front page and events is down, giving me a 500 error.  All the other pages are working fine

I cleared my cache via Tool>Cache, and still nothing. 

Anyone else ran into this issue?  Any help would be appreciated! 

EDIT: checked the logs:

[23-Oct-2017 19:45:07 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function set_magic_quotes_runtime() in /inc/header.inc.php:147 

[23-Oct-2017 19:43:59 UTC] PHP Fatal error:  Call to undefined method BxEventsTemplate::filterDateUTC() in /modules/boonex/events/classes/BxEventsModule.php on line 974

A 500 error is an internal server error generated by the webserver, not php.

500 Internal Server Error : A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

I know that doesn't help much.  A misconfigured .htaccess file can cause a 500 error so check the .htaccess file in the root of your site.

It looks like you are trying to run Dolphin on PHP 7, since "set_magic_quotes_runtime" function is removed as of PHP 7.0.0. Dolphin is compatible with PHP 5.3.x (5.4.x for some modules) - 5.6.x

Regarding another error please refer to this reply:

https://www.boonex.com/forums/topic/7-3-3-to-7-3-4-Error-BxEventsTemplate-line-974.htm#286195

commenting out the "set_magic_quotes_runtime" function worked like a charm.  Resolved. 

Interesting, those are not in the .htaccess file.  It should have shown the errors to the screen or if display errors was turned off then a blank screen.  Why would php errors trip a webserver 500 code if they were not part of the .htaccess file.  However, looking on the net someone had simple php errors such as double semicolon in a script tripping a 500 error.  They tried to track it down but could not find a reason.  It must have something to do with the way Apache is configured.  It could be tied to the version of Apache.  Who knows?