• Resolved mfghost

    (@mfghost)


    After the latest WC update I have a notification that says “The Legacy REST API plugin and HPOS are both active on this site. Please be aware that the WooCommerce Legacy REST API is?not?compatible with HPOS.”

    Now I have Printify connected to my website and I don’t want to turn off the REST API and mess up the connection from my site to Printify. Does anyone know if it is safe to disconnect the REST API?

    The page I need help with: [log in to see the link]

Viewing 14 replies - 1 through 14 (of 14 total)
  • Stef

    (@serafinnyc)

    Hello @mfghost REST API is different from Legacy API. You’ll see two different tabs under Advance for those. The notice is showing because either on an update it automatically got checked or was checked. That doesn’t necessarily mean you are using Legacy, but it’s best to check if one of your apps is still in Legacy. If that’s the case then you need to use the Legacy App in order to continue that connection until the author of that app revises it.

    Now Printify, Printful and Gelato all the top on demand print companies are already updated and as long as you are using their apps to connect you’re using REST API and not Legacy. So you’re good.

    Best to leave us a list of all the apps your using and which one is using Legacy.

    Thanks

    Thread Starter mfghost

    (@mfghost)

    @serafinnyc thanks for the response. So I would have to check if each plugin I have installed uses the Legacy API? When I look under the Webhooks in Advanced the “Printify Order” is there so I’m guessing I need to find a workaround? What happens if I leave it alone? Sorry for all the questions, I never had to touch these API settings since I connected Printify a while back.

    Plugin Support Shameem R. a11n

    (@shameemreza)

    Hi @mfghost,

    You’re correct. The Legacy REST API and the REST API are two separate entities. The Legacy REST API is an older version, and some plugins may still use it. However, as @serafinnyc mentioned, Printify, along with other top on-demand print companies, has updated its systems to use the REST API.

    If the Printify Order is showing under Webhooks in Advanced, it means Printify is using the REST API and not the Legacy API.

    If you leave it alone, there won’t be any immediate disruptions. However, it’s always recommended to keep your systems updated for optimal performance and security.

    You don’t necessarily need to check each plugin for Legacy API usage. If a plugin uses the Legacy API, you’ll likely receive a similar notification or will stop working once you disable the legacy API plugin.

    I hope this clarifies your concern. Feel free to ask if you have more questions.

    Thread Starter mfghost

    (@mfghost)

    @shameemreza understood, thanks.

    Thread Starter mfghost

    (@mfghost)

    @shameemreza One last thing I wanted to ask about…I read over as much as i can and checked the settings and noticed there is a “WooCommerce Legacy REST API” plugin that was installed on 7/28/2024. Now under “Webhooks” I clicked the “Printify Order” to see what it was using and saw next to the API Version that the one being used is “WP REST API Integration v3”. Would it be safe to remove the new Legacy Rest API plugin that was installed the other day? When I try to uncheck the box under “Legacy API” in WC Advanced Settings it doesn’t let me uncheck it. I assume that is because the plugin has been installed? So if the Printify Order is using the WP Rest API Integration v3 I could remove it as long as none of the other plugins are using it? Thanks for your help!

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @mfghost,

    It’s important to understand that this plugin provides a way for older applications to interact with your site. If your current applications, like Printify Order, are using a different API (in your case, “WP REST API Integration v3”), then it should be safe to deactivate the Legacy API plugin.

    However, please note that before deactivating any plugin, it’s always a good idea to make a full site backup so that you can always be able to revert when anything happens to your site.

    It is possible that the issue with unchecking the box under “Legacy API” in WC Advanced Settings is indeed likely due to the plugin being installed. Once you deactivate the plugin, you should be able to uncheck this box.

    Let us know how it goes.

    Thread Starter mfghost

    (@mfghost)

    (@ckadenge) that’s exactly what I was thinking, not being able to uncheck the box because the plugin is installed. I’m gonna turn it off & make sure all the other plugins work. Hopefully they do & I can delete it. I wonder if WC installed the plugin for every site or maybe just the ones that need it.

    Plugin Support ckadenge (woo-hc)

    (@ckadenge)

    Hi @mfghost,

    ’I’m gonna turn it off & make sure all the other plugins work. Hopefully they do & I can delete it.

    Sounds like a plan, please try it out and let us know how it goes.

    ?I wonder if WC installed the plugin for every site or maybe just the ones that need it.

    As I’m unable to find it in my test stores, it is possible this is not installed to every site, but specific ones based on the plugins used.

    Thank you for your understanding.

    Thread Starter mfghost

    (@mfghost)

    @ckadenge OK so it wasn’t automatically installed in every site running WC.

    So I deactivated the Legacy REST API plugin and added something to the cart & when I went to the cart page there were two errors coming from the UPS shipping plugin I have installed. Now sometimes I need to edit one line of the code for that plugin & the error disappears and the plugin works fine so I thought maybe that was the issue since WC has been updated. I wish I copied the exact errors to post here but I went back and turned the Legacy REST API plugin back on and they disappeared. Just to double-check I turned it back off and now there are no errors. So that’s weird. If there were more than the one plugin using the Legacy REST API then I assume there would have been error messages at the top of the website or each plugin using the API, correct? Anyhow, as of now I have the Legacy REST API deactivated and the site shows no errors. I’ve added products to the cart, removed them, selected variable products, checked all the account/dashboard links and went through checkout up until I had to enter card numbers to make the payment, which I didn’t do. So far everything seems to be working fine.

    I just hope while I’m out today I don’t get any e-mails from a customer having trouble checking out. That’s usually how it works lol. Anyway, it seems to be working fine so far but I’m not going to uninstall the Legacy REST API plugin just in case I or one of my customers comes across something.

    The error that did pop up when I first turned the Legacy REST API plugin off was UPS Live Rates and Access Points. But like I said, the errors disappeared when I turned the plugin back on *BUT* I turned it off once again and there are no errors showing and I have full functionality on the website. If I come across anything I’ll definitely post up right here.

    Hey, @mfghost!

    The error that did pop up when I first turned the Legacy REST API plugin off was UPS Live Rates and Access Points. But like I said, the errors disappeared when I turned the plugin back on *BUT* I turned it off once again and there are no errors showing and I have full functionality on the website. If I come across anything I’ll definitely post up right here.

    Since the error did not come back it might have just been a coincidence.

    If you see any errors with UPS Live Rates, please contact their support here, so they can assist you further ??

    For now, I’ll mark this thread as solved, okay?

    Please let us know if there’s anything else we can do to help or if you have any questions.

    Have a wonderful day!

    Stef

    (@serafinnyc)

    Hello @mfghost the UPS API legacy deprecated back in June. Everyone was supposed to be switched over by June 4th I believe the end date was.

    However, you probably need to clear cache and then things like error messages should go away.

    Thread Starter mfghost

    (@mfghost)

    @carolm29 yeah I think it was a coincidence too since it never popped up again after turning the plugin on & off a few times. You can mark this thread resolved. Thank you.

    @serafinnyc yeah I don’t see it & more than likely all the plugin devs fixed it their work before the switch.

    Stef

    (@serafinnyc)

    @mfghost nice. Glad to hear. Have a great rest of your week!

    Thread Starter mfghost

    (@mfghost)

    @serafinnyc you do the same, thanks!

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