• Resolved ulicgn

    (@ulicgn)


    Related to:

    https://www.ads-software.com/support/topic/uncaught-error-in-3-0-1/

    we had the same problems mentioned there after the 3.x Update. In our case, the problems occured after creating posts of a custom post type.

    Since there are other problems reported with 3.0.1 I would like to know your recommendation: is it safe to downgrade to the last 2.9 version or did the 3.x update contain database or metadata changes that are not backwards compatible? I would prefer downgrading over the 302 beta offered here …

    ( sorry for creating a new thread for the same problem – I had added this question to the other thread and it got deleted by the forum admins with the advice to create a new topic instead )

    Regards

    Ulrich

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    Hi @ulicgn

    Thanks for using PublishPress Future.

    sorry for creating a new thread for the same problem

    You dont have to say sorry. It’s forum regulation and we are aware of it. Thanks for creating a new thread ??

    Since there are other problems reported with 3.0.1 I would like to know your recommendation

    If the beta package that our developer sent fixes your issue, you can use it. But if the beta package cause you some other issue, please downgrade to the most stable version 2.9.2 while waiting for the 3.0.2 release.

    We still have some issues left on 3.0.2 so it might need some time for it to be released.

    Thanks for your understanding and cooperation.

    Plugin Author Steve Burge

    (@stevejburge)

    Hi @ulicgn. Thanks for using PublishPress Future. Please update to Future 3.0.2 and re-open this post if the issue remains.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Recommendation for 3.0.1 errors until fixed: downgrade or beta?’ is closed to new replies.