Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author DBAR Productions

    (@dbar-productions)

    Yes, still works just fine with latest versions of WordPress. No updates have been necessary.

    Thread Starter dev grl

    (@siqve006)

    Ok just wanted to check as it was untested with my theme.

    Plugin Author DBAR Productions

    (@dbar-productions)

    There is no theme test status for any plugins on here. You can only indicate the version of WordPress itself that it is tested up to. I have not had to update the plugin for a long time, so I have not updated that “tested up to” version #.

    Thread Starter dev grl

    (@siqve006)

    Ok I’m testing it out now and I’m seeing ‘error updating sheet’ every time I hit save. It started doing this after I selected a start time and end time from the calendar on a task. I know the format is right too because I adjusted that based on the first error. It still saves properly though.

    • This reply was modified 5 years, 10 months ago by dev grl.
    Plugin Author DBAR Productions

    (@dbar-productions)

    Still working just fine here with WP 5.2, and not getting any such errors, nor any reports from any other users of anything similar.

    Possible plugin conflict?

    Thread Starter dev grl

    (@siqve006)

    Would you be able to take a peek? It still functions ok on my end, but notice upon saving a task is error updating.

    Plugin Author DBAR Productions

    (@dbar-productions)

    Are you actually changing anything when you hit update/save? If not, then you may see that error since nothing has been changed and there was nothing to update.

    Thread Starter dev grl

    (@siqve006)

    Yes I am.

    Plugin Author DBAR Productions

    (@dbar-productions)

    The only time you should see that error is if the WordPress function that updates a table row returns a “false” type result, meaning that either the table data was not successfully update, or nothing was changed. If there was not an error, WordPress returns the # of rows updated, which would be 0 if nothing was changed in the sheet (not the tasks). There is one spot in my code that I didn’t fully check if it was a 0 value versus “false”, which can both evaluate the same if you don’t check exactly for false, so that may be what you are seeing… nothing changed for the sheet, so nothing was updated (although tasks data may have been changed, but that’s a separate table).

    If everything is working fine, then that’s most likely what you’re seeing, and I’ll fix that minor code discrepancy in the next release.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘is this up to date or no longer supported’ is closed to new replies.