• Resolved Adendum

    (@adendum)


    After updating to WP5.2 I noticed an odd looking layout in all pages/posts built with Blocks. On attempting to create a new page the Site Health message popped up and stopped me from creating a new page. The resulting email follows…

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

    In this case, WordPress caught an error with one of your plugins, Printful Integration for WooCommerce.

    First, visit your website (https://www.harmonica123.com/) and check for any visible issues. Next, visit the page where the error was caught (https://www.harmonica123.com/wp-admin/post-new.php?post_type=page) and check for any visible issues.

    Please contact your host for assistance with investigating this issue further.

    If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

    https://www.harmonica123.com/wp-login.php?action=enter_recovery_mode&rm_token=SkzdaSkFlaWLgoFxVO0quB&rm_key=czB9r7nEOYqWwJ2HJ9Darb

    To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

    Error Details
    =============
    An error of type E_ERROR was caused in line 6 of the file /home/harmon28/public_html/wp-content/plugins/printful-shipping-for-woocommerce/includes/class-printful-rest-api-controller.php. Error message: Class ‘WC_REST_Controller’ not found

Viewing 15 replies - 1 through 15 (of 26 total)
  • Hey there,

    Thank you for reaching out to us with this concern!
    Updating your Printful plugin to the latest version could fix the error you’re encountering.

    Let me know if this helps! ??

    Thread Starter Adendum

    (@adendum)

    I only installed the plugin 3 days ago and I am using version 2.1.1 so I think I am on the current/latest version.

    Alright, thank you for the update!
    We would be happy to check in with these concerns in more detail, could you send us your Woocommerce system status report (in Woocommerce->System status)?

    You can email it to us at [email protected].

    Looking forward to hearing from you! ??

    Thread Starter Adendum

    (@adendum)

    1. Email sent.

    2. You need to uncheck the ‘resolved’ box in this thread….for now.

    Thank you for sending us your WooCommerce status report!
    I’ve forwarded this issue to our developer team and will follow up with you as soon as we have an update on what could be causing this issue! ??

    P.S. The thread status has been updated, thank you for noting!

    Thread Starter Adendum

    (@adendum)

    Any feedback guys?

    Thank you for reaching out!
    Our developer team is still looking into the specifics of this issue.

    Meanwhile, could you let me know if you had made any changes to WordPress/WooCommerce/your server or installed new plugins before this error appeared?

    Looking forward to your update! ??

    Thread Starter Adendum

    (@adendum)

    No. The site was setup just a week or so ago and PrintFul was added and working.

    WordPress was updated to 5.2 and Site Health notified me of the errors and WordPress deactivated the plugin.

    Thank you for the additional information, this will give us a better idea of what could have caused this error.
    As soon as I have an update from our developer team, I’ll let you know!

    Thread Starter Adendum

    (@adendum)

    Guys,

    It’s been over a week and this thread has made no progress in that time. The client isn’t happy and already looking at Spreadshirt and others…so don’t be surprised if you lose this particular PrintFul client.

    I’m truly sorry for the delay in solving this issue, it’s definitely a new one for us!
    I do hope that we can offer a solution to you early next week.

    I will certainly follow up with you early next week with a status report!

    Good morning,

    I have an update for you! ??
    I am truly sorry that we did not catch this earlier, but it looks like our plugin is among your inactive plugins, so we suggest activating it.
    This error occurs as we’re checking for active plugins from the Woo API.

    We appreciate you bringing this to our attention and will add an additional disclaimer to the error message that suggests checking, if the plugin is active.

    I hope this helps!

    Thread Starter Adendum

    (@adendum)

    You are kidding right???????? Or are you just stalling???????

    Of course the plugin is inactive….SITE HEALTH deactivated it because of the error.

    If I activate the plugin Site Health immediately identifies the problem and deactivates it.

    Unbelievable….

    Thank you for getting back to me!
    Could you let us know what the original error is, which makes Site Health deactivate our plugin?
    The error you are receiving currently is due to our plugin being deactivated, so we are not getting any additional info on this from our end.
    Our plugin cannot work, if it is deactivated.

    It is possible that these two plugins are not compatible, so you could try disabling Site Health to see if that fixes the issue.

    We are also hoping to launch a new plugin version very soon, which could improve the situation. Our developers are notified of the errors you are receiving and have added this to their list of stuff to look into.

    Looking forward to hearing from you!

    Thread Starter Adendum

    (@adendum)

    1. Site Health is not a plugin it is a feature within WordPress (Tools>Site Health)

    2. Has anyone from PrintFul ACTUALLY READ the original support post at the top of this thread? Read the very first post – ALL the information I have was put in that first post.

    A. Site fully working since launch
    B. WP updates to 5.2
    C. The backend page display breaks and unable to create new pages/posts.
    D. A message flashes up and an email is sent from the site (full content above)
    E. Site Health deactivates the plugin with the problem – PrintFul
    F. Backend page display returns to normal.
    G. I contact PrintFul support and supply a description and the email in full.
    H. Then we start going in circles…..

    • This reply was modified 5 years, 9 months ago by Adendum.
Viewing 15 replies - 1 through 15 (of 26 total)
  • The topic ‘PrintFul plugin incompatible with WP 5.2’ is closed to new replies.