artiosmedia

Hello @sonia-zzzz ,

Our developer has corrected your conflict with the Divi theme, and the latest plugin version 1.1.2 has been uploaded to repair it permanently.

A donation from the main plugin page on the right would be helpful, found under the title “Donate”, where the developer had to be paid for the support of this free plugin. 100% of all assistance aids our not-for-profit for impoverished children.

Please kindly leave a plugin review ??

Thanks for your “frank” feedback, @optimizingmatters,

I read your cautionary tale and comprehended the hosted account that incurred “Out of Space” for the hosting was likely the sum composite of too many JavaScript files caching. The cache was burgeoning at 300 MB, with emails nearly full, causing the 2GB limit account to freeze up. Since I have been trying to keep the cache trimmed on all accounts. Apparently, that approach defeats largely the purpose of caching in the first place. I will incrementally remove the cache cleaner across accounts and watch for cache size problems.

In my case, “Also aggregate inline JS?” is always unchecked. I use the ThemeFusion Avada theme across all my accounts since inception and they include a host of performance options that replicate many of the functions that Autoptimize provides, therefore I am careful to disable those features so as not to have two sources trying to perform the same optimizations.

Thanks for your clarifications and the exceptional module! I have been using it since I think 2016 starting with 2.1 ??

@d0153 As expressed in the support ticket, I simply don’t have time to jump through hoops right now to isolate the issue with Event Calendars. As previously noted, I moved back five versions on the Avada theme and several versions on the calendar and they get along fine. Will address this issue further after a few releases are generated, to hopefully self-correct the problem in time.

I also use the account (@inndesign).

Hello @sonia-zzzz,

I have asked my developer to look at this.

Also, I see from the screen capture that the language files are not working properly either, where all the setup panel text should be in French. We will address these issues ASAP, as he is busy at the moment.

Hello @leddirect1,

In response to your question, as of version 1.4.1, an administrator can choose to hide the default and secondary product code from the user-side product posts while the other display injections still work (checkout, cart, and receipts).

A $50 donation from the main plugin page on the right would be helpful (the cost I paid the developer), or any amount for that matter, under the title “Donate”. It aids our not-for-profit for impoverished children.

Please kindly leave a plugin review ??

Hello @leddirect1,

In the settings panel, the option “Display product code on user side on the products posts, checkout, cart, and receipts” must be active for the injection to appear on the purchase order. If you have it unselected, it will not appear on the order. There is no option given to hide it from the user side but allow it to only post to the order.

Thanks

Thanks @mostafas1990. That was very fast support results!

I tested the shortcode and it works very well now ??

I do have five active plugins on the WordPress repository that take too much time as it is, but thanks for the Github invite.

@laserspiegel Having not heard back and other updates required, we have posted the new version with the requested modification.

An administrator can optionally enter a global value in the settings panel, to limit the total number of comments allowed on all posts. If the field is left blank, the default value of WordPress is maintained.
|
Any donation amount would be appreciated, from the plugin description page, on the lower right. Thanks.

Great to hear you have found the issue. Yes, Cloudflare Bot Fight Mode is a problem for many API’s and third-party connectivity. Again, this is where IP whitelisting solves the problem.

Better yet, Bunny CDN Network is superior to Cloudflare on several levels, fully eliminating many of these types of bottlenecks.
https://bunny.net/network/

@robertpurnomo It is possible with all the attempts to connect, even though reducing the situation to the least common denominator (only the WooCommerce Plugin and the Printful plugin) the repeat API connection attempt threw a red flag on your host which resulted in an automatic black listing of the connecting IP. The problem with Hostinger virtual hosting, you don’t have the ability to personally dig deep into the hosting to see if there is a block. The main reason I have a dedicated hosting server, I can service every possible scenario without having to wait on a support person NOT to figure it out. I would set it back to the basics (on the two plugins) and then call Hostinger to look over the connectivity.

If you are using a Hostinger account with Cloudflare, that adds another level of complications other Printful users completely fail to anticipate. You do need an IP white list installed to prevent the sync from being blocked (even if not using Cloudflare or another CDN). Here is a post that digs deep into this issue with a IP whitelist solution: https://community.cloudflare.com/t/cloudflare-blocks-printful-woocommerce-integration/357449/9

Granted, some of the IPs could have been changed by now since it was a 2022 support thread, but an email to Printful support might gain you a fresh IP list, although it is reported that they will not share them.

@laserspiegel Please let me know what your updated plugin test results are from my last post above. We are waiting to upload the plugin update if okay.

Greetings @laserspiegel,

I took your meaning to add a global entry for all entries in the plugins setting panel as I outlined above. However when you said, “…for any specific blog post or static page.” The word ‘specific’ told the developer you wanted to assign a comment limit value to only certain posts. Therefore the plugin modification added a line in the following location outlined by a red box “Maximum comments allowed [xxx]” below the existing option. See: https://ps.w.org/limit-comments-and-word-count/assets/screenshot-5.jpg?rev=2665085

The entered value is only good for that post while each post can have a different comment limit.

Please install this 1.1.8alpha update and test: https://file.io/SZ01DdZLf3Yq If this is what you were wanting, then I will update the plugin repository immediately.

An $80 donation from the main plugin page on the right would be helpful, or any amount for that matter, under the title “Donate”. It aids my not-for-profit for impoverished children.

Thanks,
Steven
Artios Media

Greetings @squishworx,

You can check via WooCommerce > Settings > Advanced > Features. The plugin is now HPOS compliant.

Please kindly leave a plugin review ??

Thanks!

It is possible with all the attempts to connect, even though reducing the situation to the least common denominator (only the WooCommerce Plugin and the Printful plugin) the repeat API connection attempted threw a red flag on your host which resulted in an automatic black listing of the connecting IP. The problem with GoDaddy, you don’t have the ability to personally dig deep into the hosting to see if there is a block. The main reason I have a dedicated hosting server, I can service every possible scenario without having to wait on a support person NOT to figure it out. I would set it back to the basics (on the two plugins) and then call GoDaddy immediately to look over the connectivity.

If you are using a GoDaddy account with Cloudflare, that adds another level of complications other Printful users completely fail to anticipate. You do need an IP white list installed to prevent the sync from being blocked (even if not using Cloudflare or another CDN). Here is a post that digs deep into this issue with a IP whitelist solution: https://community.cloudflare.com/t/cloudflare-blocks-printful-woocommerce-integration/357449/9

Granted, some of the IPs could have been changed by now since it was a 2022 support thread, but an email to Printful support might gain you a fresh IP list, although it is reported that they will not share them.

I simply disabled all WooCommerce plugins and then re-enabled them, as noted. It then synced when I clicked to connect from the Printful plugin. The comment about the HPOS was simply an example of how the developers of the Printful plugin lack knowledge and/or initiative. The HPOS cannot be activated if any plugin active is not code compliant.