Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter richardferlow

    (@richardferlow)

    Oh, I guess this bug should be reported to the post-expirator developers.

    Thx

    Plugin Support Andy – a11n

    (@andyr94)

    You’re on the right track, this looks like it’s coming from PublishPress Future (post-expirator) rather than Action Scheduler itself.

    Action Scheduler’s newest major release changed some of its internals, and PublishPress Future hasn’t been updated to match yet. That mismatch is what’s triggering the fatal error on the ScheduledActionsTable class. The PublishPress Future team has an open issue tracking this: https://github.com/publishpress/publishpress-future/issues/1655, with a fix planned for their upcoming 4.11.0 release.

    Until that update is out, you can check with PublishPress Future’s support if there’s an interim workaround for your setup.

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

You must be logged in to reply to this topic.