Fatal Error on v32.0.10

  • Resolved LaurentAngeli

    (@laurentangeli)


    8 months, 4 weeks ago

    Hi, after updating PPOM to 32.0.10 (it is the only change on site unsing latest WP version), a fatal error appear :

    [29-Feb-2024 07:58:05 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function wp_get_current_user() in /home/bigi2377/public_html/wp-includes/capabilities.php:877
Stack trace:
#0 /home/bigi2377/public_html/wp-content/plugins/woocommerce-product-addon/classes/admin.class.php(65): current_user_can('manage_options')
#1 /home/bigi2377/public_html/wp-content/plugins/woocommerce-product-addon/woocommerce-product-addon.php(101): NM_PersonalizedProduct_Admin->__construct()
#2 /home/bigi2377/public_html/wp-settings.php(473): include_once('/home/bigi2377/...')
#3 /home/bigi2377/public_html/wp-config.php(118): require_once('/home/bigi2377/...')
#4 /home/bigi2377/public_html/wp-load.php(50): require_once('/home/bigi2377/...')
#5 /home/bigi2377/public_html/wp-admin/admin.php(34): require_once('/home/bigi2377/...')
#6 /home/bigi2377/public_html/wp-admin/edit-comments.php(10): require_once('/home/bigi2377/...')
#7 {main}
  thrown in /home/bigi2377/public_html/wp-includes/capabilities.php on line 877

    Reverting to 32.0.9 and site works normally.

    Can you fix it this error ? Thanks in advance.

    • This topic was modified 8 months, 4 weeks ago by LaurentAngeli.
Viewing 13 replies - 1 through 13 (of 13 total)

  • Yes, same issues here.

    Auto-update to 32.0.10 last night has broken the plugin.

    Same here.. you can download the previous version 32.0.9 at the bottom of the page here: https://www.ads-software.com/plugins/woocommerce-product-addon/advanced/

    • This reply was modified 8 months, 4 weeks ago by oyacom. Reason: Found solution

    Same. In case it is of help to plugin developers :- wp_get_current_user() is being called before it is defined as init hook is not being used.

    woocommerce-product-addon/woocommerce-product-addon.php:101

    Plugin Author Themeisle

    (@themeisle)

    Hi everyone,

    Thank you for sharing this issue, our development team is already looking into the problem and we hope to have a solution soon.

    Apologies for the inconvenience.

    Plugin Support AndreeaR

    (@andreearadacina21)

    Hello?there @laurentangeli,

    We appreciate your cooperation in reporting the issue you’re encountering. We are sorry for the inconvenience, and we have confirmed the problem. A bug report has been created and forwarded to our product development team for review.

    What happens next?

    Our developers prioritized this as the highest-priority issue so that it will be taken care of immediately.

    We will update you once the issue is addressed and a fix is released. You may also check the product’s changelog for updates and fixes in each release.

    If you have any additional questions or concerns, please feel free to open another post. Again, we apologize for the inconvenience and thank you for your patience.

    cc: @abcdavid, @oyacom, @tgo_dc

    Best regards,

    Andreea

    Hi there, I updated to the new 32.0.11 but the PPOM options don’t show on the front-end of my website?

    Any ideas here?

    I checked PPOM fields in WordPress admin and they’re definitely assigned to the products. The issues only occurred after updating from 32.0.09.

    Thanks for any help so far!

    Oddly enough, the options are showing now again on the front end when I enable / check this box in PPOM settings:

    Legacy Inputs RenderingPPOM Version 22.0 is major update, if some issues occur you can revert back to old version by this.

    Plugin Author Themeisle

    (@themeisle)

    Hi @tgo_dc,

    We identified the reason this is happening and will make a patch release tomorrow after an additional review.

    Thank you for your patience and cooperation.

    Plugin Author Themeisle

    (@themeisle)

    Hi @tgo_dc,

    We made a new release that addresses the mentioned issue.

    Please check with version 32.0.12?and let us know if you still encounter any problems.
    Thanks!

    Thanks, everything now seems sorted and I’ve disabled that Legacy option again.

    Thread Starter LaurentAngeli

    (@laurentangeli)

    Thanks for your work. Every thing is fine now with 32.0.12.

    Plugin Support AndreeaR

    (@andreearadacina21)

    Hey @laurentangeli, @tgo_dc,

    Thank you for your confirmation and we again apologize for any inconvenience you may have experienced!

    If you have any other questions, feel free to start a new thread.

    Best regards,

    Andreea

    No the new version dont work for me. Same issue. I cleared cache, tzested on incognito browser. Only when I check the legacy option ppom fields are back.

    Strange

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Fatal Error on v32.0.10’ is closed to new replies.