• Resolved them.es

    (@themes-1)


    WordPress 6.5 is just around the corner with a planned release date in about 4 weeks. And the first RC already will published next Tuesday.

    On a test site with WordPress 6.5 (Beta 3) we noticed that viewing/generating the PDF invoices in the edit order view is not working anymore (WooCommerce v8.6.1, HPOS, using your latest plugin version v3.7.7).

    After downgrading to WordPress 6.4.3 everything is working again.

    Are you aware of this issue? It would be great if it could be resolved before the next stable WordPress version gets released.

    Thanks in advance!

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Contributor Yordan Soares

    (@yordansoares)

    Hi @themes-1,

    Could you please tell me if you receive any error message, or what happens when you try to view/generate a PDF document?

    Thread Starter them.es

    (@themes-1)

    Hi @yordansoares,

    thanks for your swift response.

    PDF invoices do get generated but when reloading the PDF preview in the browser the invoice number always increments +1.

    In the order overview the “Invoice Number” entries are blank.

    In the edit order view the PDF document data panel just shows the button “Set Invoice number & date” which triggers the confirmation “Document data saved!” when manually recreating the PDF. But again the panel doesn’t show any document data here.

    Previewing the PDF via Sidebar link does show the invoice correctly but with the same incremention bug noted above.

    No PHP errors are logged and no console error messages seem to appear 🤷

    When downgrading to WordPress 6.4.3 none of the bugs can be reproduced anymore. So there must be a regression between WordPress 6.4 and 6.5 (beta3).

    Plugin Contributor alexmigf

    (@alexmigf)

    Hi @themes-1

    I’m running WP 6.5 beta 3 on my local setup with the latest version of our plugin and I’m not having any of those issues, with our without HPOS enabled.

    Do you think you could create a new fresh setup and test if the issue persists?

    Thread Starter them.es

    (@themes-1)

    Hi @alexmigf,

    forgot to mention that the bug only has been tested and still can be reproduced on three different Multisite test instances (even on newly created sub sites with Twenty Twenty-Four installed).

    But you’re right – when testing it on a clean installation (Single or Multisite) everything is working as expected.
    It’s not easy to understand why downgrading to WP v6.4 fixes the bug. And reinstalling the plugin after clearing all “*wcpdf*” db entries didn’t help either.

    Debugging is also hard without seeing any errors in the logs and since it’s working on new installations feel free to close this issue for now. Hopefully production sites will not be affected by an overseen regression.

    Thanks for your time!

    Plugin Contributor Yordan Soares

    (@yordansoares)

    Thanks for providing more details, @themes-1.

    Although we have not been able to reproduce the issue, we are very interested in this subject: Please let us know if you find the root source of this issue, to know if it is something we have to solve from our side and take action accordingly.

    Thread Starter them.es

    (@themes-1)

    Hi @yordansoares and @alexmigf,

    just wanted to let you both know that after two more tests on clean WordPress installations with the following specifications, the bug could be reproduced even on brand-new instances and no other plugins installed. Not sure why it seemed to have worked in a previous test…

    • PHP 8.3
    • WordPress 6.5 (beta3)
    • WooCommerce 8.6.1
    • PDF Invoices & Packing Slips for WooCommerce 3.7.7

    Could you give it another try with the above specifications? E.g. via a temporary instance like https://tastewp.com: https://pasteboard.co/RnzzXOLsrsmA.jpg

    Order/Overview (invoice not visible at all): https://pasteboard.co/sCMr2iY7ZQ1h.jpg
    https://pasteboard.co/pOpXIt9ioAZR.jpg

    PDF can be accessed but the number increments +1 anytime the link gets opened: https://pasteboard.co/FBNwyo4u1BPA.jpg

    Hopefully this information helps to reproduce the bug on your side!

    Plugin Contributor alexmigf

    (@alexmigf)

    Hi @themes-1

    Bare in mind that WordPress still has limited support to PHP 8.3 and our plugin is not yet compatible with that PHP version. We will open issues to address this, but could take some time until we get it properly tested.

    Thread Starter them.es

    (@themes-1)

    Hi @alexmigf,

    just wanted to let you know that WP 6.5 RC1 has been released yesterday and everything seems to be working fine now 🥳

    The root cause for last week’s failure on WP 6.5 Beta 3 + PHP 8.3 remains uncertain.

    By the way. WordPress 6.4 does in fact support PHP 8.2/8.3 already – at least in a beta state – which means that Core is fully compatible without breaking anything.

    Also your plugin was working with PHP 8.3 when testing it with WordPress 6.4.2 (same server setup, same plugin versions).

    But in the end no further action is required on your side and this request can be closed.

    Plugin Contributor alexmigf

    (@alexmigf)

    Hi @themes-1,

    Thank you for your reporting on this!

    By the way. WordPress 6.4 does in fact support PHP 8.2/8.3 already – at least in a beta state …

    Correct, that’s why I mentioned “limited”.

    We have opened an issue to address this, we will improve this compatibility in the coming weeks.

    Thank you!

    Plugin Contributor Mohamad

    (@mohamadntr)

    Hello @themes-1,

    WordPress just recently released the 6.5 version. Everything is working fine on our end, and we couldn’t replicate the issue you reported.

    Could you run a test with the latest version of WordPress and let us know the result?

    Best regards

    Thread Starter them.es

    (@themes-1)

    Hi @mohamadntr,

    thanks for checking back. You’re right. Everything is working fine since WP 6.5 RC1 and as noted in this comment the issue can be closed.

    Thanks.

    Plugin Contributor Mohamad

    (@mohamadntr)

    @themes-1,

    Thank you for your feedback.

    All the best to you.

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