The Rite Sites

Hey Jeffylube!

The plugin has been updated to indicate compatibility with WC HPOS!

Please let us know if there is anything else if we can help with.

Best regards,

The Rite Sites

Hi Thomas,

Thanks for the kind words!
Thats a pretty custom implementation, and very dependent on your usage.
To me, that would be a CSS change. Elementor also might complicate things.

You can find the button selector on this page here: https://www.theritesites.com/docs/styling-guide/#button

There are multiple methods used to center objects, you can find guides online, a quick search of “css guide to centering elements” in your favorite search engine, those will be better at helping you than us!

As this isn’t really an issue and more your implementation, we are going to close it as support. Feel free to continue the conversation though!

Cheers!
The Rite Sites

• This reply was modified 3 years, 6 months ago by The Rite Sites.

Hi Markus,

Sorry for the delay in response, we were unavailable to the project for a short time.
This is an issue in compatibility with themes. We have found this element in the project this was originally created for, and the short list of themes this was available. This is due to it being found in the WooCommerce plugin, often used as a implementable wrapper component.

Understandably, this could be an incompatibility with any random theme that chooses not to implement this.

We are open to suggestions for solutions, but as an easy solution a target css selector in the settings page?

Otherwise, temporarily, you could add an element on your page or theme through filters or otherwise (Elementor, ‘blank’ element) with the class of “content-area”

We have considered the idea of putting notifications within the row, but haven’t quite found the right implementation to fit with the direction of the plugin.

Be your best!
The Rite Sites

I will add this to the backlog, considering adding a checkbox, or putting FALSE in the URL box to disable the a tag in the new assets/js/enhanced-ajax-add-to-cart-wc-public.js on line 286
Maybe changing it to a span element (w/ plugin class) containing the custom text?

We have another larger feature release planned for 2.4, you should see something like this reflected at or before that update!

Hi Deltacharlie,

During the big upgrade to 2.0 we made some significant changes, and one of them had to do with how we handled the cart fragments refresh functionality from WooCommerce — this is used int he “minicart” or how you can dynamically see your cart contents without going to the designated “cart” page.

Thanks to your submission here, I was able to track down this issue. Because of this, we have added 3 new settings as of version 2.3.0 which do the following:
1) Change the text of the “View cart”
2) Change the URL of the “View cart” (or custom) link/text.
3) Disable the refresh fragments executed by this plugin

You should only need to use the settings labeled 1 & maybe 2 above. The 3rd setting being disabled might reflect faster times for adding products to your cart. That being said, it should be a nominal increase in speed on most servers.

Please let me know if this solution does not fit your need, or if you run in to other issues!

Hi Sigi,

Spent the morning trying to make the plugins compatible.
We found some progress by editing their source code in multiple places to get their input in place.
After that, there was still issues which would be on our side.

If you are locked in to using both ours and their plugin, we would need to possibly get an exposed function from them to display their fields.

Specifically, this function outputs the HTML:
Alg_WC_Product_Open_Pricing_Core::add_open_price_input_field_to_frontend()

BUT this function also uses “the loop” or the global product on the page.
Even attempting brute force methods by changing the global $post (in this case a product in question), their function still returns as if no global is set.

For us to make a good integration, we would request that somehow we could pass in a specific product to get the HTML to work with outside of their own specific contexts.
Could be like:
Alg_WC_Product_Static_Functions::generate_open_price_input_field( $product_id )

I noticed you closed the ticket, but if you would like to continue working on this for your site, we are open to further integrations in a future version. Feel free to reach out if you have any other questions comments or concerns!

Cheers,
The Rite Sites

Hi Lech,

I can understand why there may be some issue!
We wrote up a way to possibly solve this here: https://www.theritesites.com/docs/add-to-cart-buttons-send-events-to-google-tag-manager/

In short: its definitely some javascript that is not implemented in any way. We do see the need for this to be able to be managed in some way! Other than that (hopefully helpful) guide, we have added the functionality to our backlog.

Thanks for the interest in the plugin, and if you have any suggestions in this implementation feel free to reach out!

As this is going to be considered a feature request, or otherwise solved by documentation, I am going to close this ticket.

Happy Pressing!
The Rite Sites

Are you able to use a WooCommerce standard Add to cart button? Or does the plugin in question have a different method of adding the gift card to the cart?

Hi Sigi!

Can you explain this a bit more for me to see what the requirements would be like?
When is the price chosen?
Are you using the shortcode, block, or did you try both?

The plugin gets the price from the WooCommerce Product that is selected. We stick as close to WooCommerce core functionality as we can, broad example: WC_Product::get_price()

Perhaps, there is another hook we can use to make our plugin compatible?
Any additional information or examples would be nice, as in a link to your (broken) implementation or to the plugin directly you are using.

Cheers,
The Rite Sites

We will be closing the support ticket as it has been a week since the last user response.
Please feel free open another ticket if problems linger or for any other reason!

I will be closing the support ticket as it has been over a week since your last message. Feel free to open another support ticket or send us a message in the future!

2.1.2 is out and should resolve this issue.
Let me know if any issues persist

Perfect, I know exactly where that is.

Look for a release later on today!

Sadly, I cannot recreate the issue. I saw on your link you seem to be running WP 5.6 and WC 4.9.2. I used similar shortcodes (changing product IDs around) and haven’t even gotten a warning.

The biggest issue I had was the double quotes used (“) I had to change to get my buttons to display your whole text as “Lis?? ostoskoriin” instead of ”Lis?? (left quote showing for me after literal copy and paste) – but this would have been present on 2.0.0 as well. (it works for you, I don’t think its a bug)

Is this your live site or a staging website? Is there any way I would be able to access the page while it is in an error state? I believe this is due to attempting to translate the string from WooCommerce, as that was the bulk of the changes to 2.1.1.

Obviously that’s a huge issue!
Can you send me the shortcode you are using on that page? Or a couple examples if there’s multiple?