[devicename | *] [\\computername\sharename[\volume] [password | *]]
[/USER:[domainname\]username]
[/USER:[dotted domain name\]username]
[/USER:[username@dotted domain name]
[/SMARTCARD]
[/SAVECRED]
[[/DELETE] | [/PERSISTENT:{YES | NO}]]
NET USE {devicename | *} [password | *] /HOME
NET USE [/PERSISTENT:{YES | NO}]
Turns out WordPress 5.3 does not want anyone to use the date_default_timezone_set() function anymore. You are suppose to use the new wp_date() function instead of setting timezone and using date(). I’ve fixed your plugin by doing the following few steps. Super easy btw:
1) Erase line 96
2) line 98 goes from:
$tnow = intval( date( 'Hi' ) );
to:
$tnow = intval( wp_date( 'Hi' ) );
3) Line 100 goes from:
$twday = intval( date( 'w' ) ) + 1;
to:
$twday = intval( wp_date( 'w' ) ) + 1;
4) Line 252 goes from:
wp_enqueue_script( 'front-page-scheduler-js', plugin_dir_url( __FILE__ ) . '/front-page-scheduler.js', array( 'jquery' ), date( 'YmdHis', filemtime( dirname(__FILE__) . '/front-page-scheduler.js' ) ), true );
to:
wp_enqueue_script( 'front-page-scheduler-js', plugin_dir_url( __FILE__ ) . '/front-page-scheduler.js', array( 'jquery' ), wp_date( 'YmdHis', filemtime( dirname(__FILE__) . '/front-page-scheduler.js' ) ), true );
Just noticed the plugin was updated this morning. Very cool! However, this problem still exists. Should be patched ASAP since it completely breaks calendar based plugins.
Thanks!