• Resolved akempkens

    (@akempkens)


    Hi there,

    with the latest WP version and tracks 1.79, there seems to be a PHP8 issue – according to a google search.

    WordPress-Version 6.5.5
    Aktives Theme: Tracks (Version 1.79)
    Aktuelles Plugin: ?(Version )
    PHP-Version 8.2.18

    Issue occurs if I try to create a new post., however it is clearly linked to the theme as using one of the default themes it works directly.

    Issue location: wp-content/themes/tracks/functions.php:567

    Uncaught TypeError: Unsupported operand types: string % int?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Theme Author Ben Sibley

    (@bensibley)

    Thanks for getting in touch about this.

    Can you try installing this updated version of Tracks and let me know if it fixes the error: Download here

    Thread Starter akempkens

    (@akempkens)

    Wau that was fast Ben.

    Good day for bug hunting, I feel – it works, I can add posts again.

    There is something, that I feel is related. In the post overview it shows me the HTML code, which was not the case in the past.

    experience many leaders struggle with…<div class="more-link-wrapper"><a class="more-link" >Read the post<span class="screen-reader-text">Our Change Design Canvas</span></a></div>
    Theme Author Ben Sibley

    (@bensibley)

    Hmm I’m not sure how that would happen. I don’t think it’s related to the other error. Could you try using the WP Rollback plugin to revert Tracks to v1.78? I’d like to know if you still see the error, which would let us know if it was something in the v1.79 update, or if something else on the site has changed.

    Thread Starter akempkens

    (@akempkens)

    Hi Ben,

    Ok the presentation I had as a second issue was actually existing before. Just that I did not realized it. So no worries about this.

    The issue with the Type Error occurred in all version until 1.76, including 1.79 which is available on the server.

    The version you sent me here in the thread fixes the issue!

    Theme Author Ben Sibley

    (@bensibley)

    Okay great. Thanks bringing this error to my attention, and I’m glad we could get this resolved.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.