Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter Peter Arthur

    (@peterdarthur)

    Mark,

    I totally understand – I’m still unpacking after a cross-country move in early August (AL to CA). I searched around in the plugin files and found where dtg_first and dtg_last are converted from “now” to timestamps: mstw-schedules-scoreboards/includes/mstw-ss-schedule-table.php, starting on line 98.

    I noticed that dtg_first is evaluated like this:

    if ( $atts['first_dtg'] == 'now' ) {
    	$first_dtg = current_time( 'timestamp' );
    }

    and dtg_last is missing the ‘timestamp’ string (on line 109), so I added it in the corresponding place, and now dtg_last="now" works (but only if dtg_first is also set, to a time in the past). This will work for me, but if you don’t mind checking this for yourself and including this in any updates, then I won’t have to worry about any future version issues. Thanks!

    Thread Starter Peter Arthur

    (@peterdarthur)

    I just discovered the solution. On a team’s settings page, I scrolled all the way to the bottom, to where it says

    “In this release, the following fields are for use by developers only. They have no impact on the plugin’s current user interface.
    Read more here.”

    In this section, I added a Team Sport/Season, and when I refreshed the affected page, the table displayed as “Sport @ Opponent” (or “Sport vs Opponent”) in the opponent field. 🙂 Note that I had to create Sports for the field to show Sport options.

    Thread Starter Peter Arthur

    (@peterdarthur)

    Thanks for the reply, Mark.

    I tried setting last_dtg to “now” in a Schedules and Scoreboards table shortcode, but it resulted in a “break the page completely and don’t display anything” issue. The current page editor in WP dashboard also broke (white page) after setting last_dtg=now in the shortcode (thankfully I was able to log in again and deactivate the plugin, so I could return and remove =now before re-activating the plugin. Are you able to replicate the issue?

    As for SSL, here’s a link to the request by @gusc: https://ww.wp.xz.cn/support/topic/mstw-doesnt-support-ssl/

    I can’t verify if this is true or not, since my website will not be SSL until this athletics portion is ready to go, but according to him, the fix would be a simple find-replace of all http:// -> // . I’m not sure what the correct syntax would be in the plugin, but as long as http requests are replaced with root-relative ones, it should work fine.

    The issue is that a site configured for https must only contain and operate with links that are also either https or root-relative. A resource loaded from an http link on an https site won’t work. Images, files, stylesheets, db queries, etc.

    I’m a front-end guy with zero plugin experience (yet), so I don’t know PHP/MySQL enough to pinpoint a plan of action. Thanks for such a great plugin!

Viewing 3 replies - 1 through 3 (of 3 total)