Nathan Ingram

Update: I was informed by Printful support that the legacy API is no longer required. We have a store running Printful using HPOS without a problem now.

That’s a good question. It makes me shudder to think about giving users manual edits of the .htaccess from within the dashboard. So many ways for that to go wrong. Maybe marking sections as “keep” (or something) would be a good approach?

Wow quick response! I had actually edited my original question to add a couple more items…

Thanks for persevering with the approval process. I know it’s crazy slow right now.

@christianaprintful thank you for your update.

Does the Printful team realize that all new WooCommerce stores now are set up without the legacy REST API as well as with HPOS?

This means that if anyone wants to use your plugin to sell Printful products, they will have to manually move from HPOS to legacy posts storage, and then install the WooCommerce Legacy API plugin.

This is a poor look for Printful and will prevent most people from using your connector in the future.

What can be done to encourage development work from Printful to be completed?

We have run into the same issue. It’s related to WooCommerce retiring their legacy API and removing it from WooCommerce 9. Printful is still using the legacy API even though it was deprecated years ago. Printful needs to update the plugin.

In the meantime, you can use this plugin to add the legacy API back to Woo. This solved the issue for us.

https://www.ads-software.com/plugins/woocommerce-legacy-rest-api/

Followup – I now see that I have to hit the enter key after entering the email address, which surrounds it with the gray box. You might consider changing that, as this is not very intuitive.

Otherwise, this plugin looks great! Nice work!

Hi Reju! Thanks for your response and the helpful video.

I am using the New Registration template because I need the user to receive a password reset link when they are added to the site.

The issue I describe is not happening in the test email. The email that is actually sent to the user upon registration has the password reset link (as shown in the screenshot linked in my first message). However, the link in the email received by the user is {{reset_link}}?and not the actual URL for resetting the password.

Interesting. I had removed the plugin on my test side. Now, oddly, when I just added it back, the table was created. There were 5 completed actions for fast_woo_order in the Action Scheduler.

This time there was a fatal error (below) that appears upon activation. It disappears after I navigate to another admin page.

Fatal error: Uncaught DivisionByZeroError: Division by zero in ----/plugins/fast-woo-order-lookup/code/class-textdex.php:

Thanks Mayur! I featured your plugin on the SolidWP Plugin Roundup earlier this month. This change makes it a lot better!

I’m having this same error. Line 595.
I believe the fix is to update line 595 to this:

return get_taxonomy_image( $atts['term_id'], filter_var( $atts['return_img_tag'], FILTER_VALIDATE_BOOLEAN ), explode( ' ', $atts['class'] ) );

This changes the first $attr[‘term_id’] to $atts[‘term_id’]. Everything works for me and no more errors.

That’s awesome Samuel, thanks!!

Thanks Samuel! I just emailed you at the address on the contact page on your website.

Following up… we reinstalled the plugin and then deleted. This fixed the issue. Strange one. Thanks!

Thanks for the quick reply, John!

I’ve restarted all the things (Litespeed, PHP-FPM), and dumped every cache that I have access to. The error still persists.

Thanks Corey! I can also confirm the plugin update in the zip file you provided above does fix the issue.