Thread Starter
Kenton
(@kbsmith)
Posted fix from another user on the Time.ly discussion forum:
July 24, 2014 at 9:40 am #126922 REPLY (linux4me2)
I did not hear back from Time.ly about this, so I did a little experimenting and found a workaround for anyone who is experiencing the same issue.
Find the following line on about line 405 (line 415 for me) of /wp-content/plugins/all-in-one-event-calendar/app/controller/front.php:
if ( basename( $_SERVER['SCRIPT_NAME'] ) === 'post.php' ) {
and replace it with this:
//if ( basename( $_SERVER['SCRIPT_NAME'] ) === 'post.php' ) {
if ( basename( $_SERVER['PHP_SELF'] ) === 'post.php' ) {
Using PHP_SELF instead of SCRIPT_NAME has eliminated the error on my server, and switching back to SCRIPT_NAME I get the error filling up my error_log again, even though I have confirmed that SCRIPT_NAME is indeed available in my PHP installation.