deeveedee

Thank you for the quick reply. Since I want to receive alerts for most post-updates, I will configure the specific post-type alerts to ignore. Thanks again.

I’m sorry that our firewall settings are blocking your foreign servers. I have attempted to gather more information to help you diagnose this. Again, I am content with the “no-lazy” solution, so this is to help you in case it indicates an issue.

The tooltip on my page is processed by bootstrap.min.js (the event fires when the user hovers their mouse over the label). It appears that Lazy Loading and bootstrap.min.js are conflicting.

@vmarko Thank you for the quick reply! We believe we have unblocked your CIDR. Please try again when you are able. Thank you.

@vmarko It looks like you (or one of your peers) attempted to access our website from another CIDR. We block non-US traffic, so it may be difficult for us to give access to you. I aplogize for the inconvenience and understand if you’re not able to help without this access.

• This reply was modified 2 years, 9 months ago by deeveedee.

JQuery Helper identified an issue that appears to have solved the problem. I replaced instances of .live with .on in themes/fruitful/js/init.min.js and the hamburger menu is working with WordPress 5.8.2 and the default WordPress jQuery version.

I was able to temporarily restore functionality of fruitful theme hamburger menu with WordPress 5.8.2 by setting JQuery Helper’s “Legacy JQuery” option.

@fruitfulcode, Downgrading to WordPress 5.5.7 “fixes” the hamburger menu. This appears to be a compatibility issue between Fruitful theme and WordPress 5.8.2.

This can now be marked SOLVED.

Now that I understand more about the problem and solution, I would have worded my question to ask: what’s the best way to programatically submit a new product item from PHP to the WooCommerce Shopping Cart.

The answer is: WC()->cart->add_to_cart().

We designed our custom product page / WooCommerce interface when we were first learning WordPress and WooCommerce. It’s unfortunate that we stumbled upon the WooCommerce /cart/add-to-cart URL/query string API before we found the WC()->cart->add_to_cart() api.

I think that I’m over complicating this. Could it be that if I want to insert something into the WooCommerce Shopping Cart with PHP, that I simply call function

WC()->cart->add_to_cart()?

• This reply was modified 3 years, 11 months ago by deeveedee.

I’m going to ask what is probably a dumb question, but I’ll ask anyway. If WooCommerce default add-to-cart buttons use $_POST to pass product data to cart, shouldn’t I be able to create my own custom add-to-cart buttons that use $_POST to pass product data to cart?

I have highly customized product configurations produced by the customer when they design their product on my custom product design page. The product design page has an “Add To Cart” button that currently invokes /cart/?add-to-cart with a query string that specifies the custom product attributes.

Does WooCommerce offer support for a custom “Add To Cart” button that passes data to the cart via $_POST?

@riaanknoetze – thank you for your quick response. We are invoking WooCommerce add-to-cart from PHP (/cart/?add-to-cart). We populate the add-to-cart query string with our custom product parameters. This is problematic for us, because the Sucuri firewall occasionally misinterprets the long add-to-cart query string as XSS (Cross Site Scripting) and blocks the transaction (preventing the user from adding their order to the cart).

We’re hoping that WooCommerce offers another mechanism that permits us to invoke /cart/?add-to-cart without passing custom product parameters via query string.

Thank you.

I should have posted this in the Fruitful Shortcodes forum – sorry about that. The solution for me was to open Settings > Fruitful Shortcodes and do the following:

• Uncheck “send data to fruitful” (disappointed to see that the default was to send diagnostic data to Fruitful without an option to disable this during install).
• Select “Old Shortcode Version”
• Click “Save”

Fruitful team – your option to send data to Fruitful should be configurable during install and should NOT be something that is hidden until the user opens Settings. Very disappointing.

I found that if I save the post and then edit to the previously saved post, the link will appear in the public post. The link would not appear if I inserted the link when first creating the post.

• This reply was modified 5 years, 1 month ago by deeveedee.

@jacksturner – I’m not a CSS expert, so I’m afraid I won’t be much help. With Fruitful theme, the only way I see to distinguish between the conflicting info-circles is with the :before modifier. Without the :before modifier in the CSS “fix,” both info-circles are hidden (try it yourself). If you can figure out a way to apply display: none; to the other info-circle, you’ll have your solution.

I’m sorry I don’t have a better answer.

• This reply was modified 5 years, 11 months ago by deeveedee.

Thank you, @yorman!

@yorman,

I appreciate your help and know that you are extremely busy. If .htaccess is not modified by Sucuri Security plugin, I don’t expect you to find the cause (although I do appreciate your offer). If it’s not Sucuri, then I suspect it might be something in cPanel.