Senff - a11n
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce] Trying to get shipping class costs to workHey @msincome
By default, WooCommerce does not have the option to charge a $11 flat fee shipping if the order contains 1 product, and $16 flat fee shipping if it contains 2 or more.
For that sort of setup, we generally suggest using a plugin that can apply different flat shipping fees based on the quantity of products in the cart. One that can do that is Table Rate Shipping, so you might want to give that a try.
Hope this points you in the right direction!
Hey @majidseifi
To change the size/style of that button, you can use some CSS code. However, we can’t check that based on a screenshot — could you give us the URL of your site so we can take a look?
Thanks!
Forum: Plugins
In reply to: [WooCommerce] Translation is not completeHey @tsangmelinda
The text that is showing in your screenshot (“Welcome to your account page” and “today is a great day to….“) is not standard WooCommerce, so it is either coming from another plugin, or it was specifically customized.
If it’s coming from another plugin or your theme, you will need to use LocoTranslate and then select that specific plugin/theme to find, select and translate that text.
If you did that and it’s still not working, have you checked that with the plugin developer?
Hey @gavintbh
By default, the description shouldn’t change when you switch between payment methods — it should always say “Credit card / debit card”, as you can see in this quick screencast:
Image link: https://d.pr/i/i1VULeCan you share a link to your site so we can see what the issue might be?
- This reply was modified 4 years, 8 months ago by Senff - a11n.
Hi @michele6231
Can you tell me which text you’re trying to translate exactly, and how/where you’ve added the translation in Loco Translate?
Forum: Plugins
In reply to: [WooCommerce] “>” Displays as “5” on WooCommerce ButtonsHey @jnaes
It looks like this is supposed to look like a symbol (instead of a “5”), using Divi’s ET Modules icon font.
Since this is not direclty coming from WooCommerce, I’d recommend reaching out to the Divi’s support team for this.
While we’re experts on our own products, third party plugins are best supported by their own resp. developers (and more importantly, I’d rather not give you any incorrect information).
Hope this points you in the right direction!
Forum: Plugins
In reply to: [WooCommerce] Custom User Registration Fields No Image ShowingHey @valhallaskies79
Since our Custom User Registration Fields is a premium product, support for this is handled through WooCommerce.com.
To request any support for this plugin, please go to https://woocommerce.com/my-account/create-a-ticket/?form=ticket
From there, select the Custom User Registration Fields extension in the “I need help with” dropdown. Here is a screenshot for your reference:
Image link: https://d.pr/i/md7RfJThis will ensure that your request it routed to the extension’s support team right away, and they will reach out to you shortly via email.
Forum: Plugins
In reply to: [WooCommerce] Wrong company name when using Stripe – GiropayHey @luckyluke44
If you’re using our Stripe extension, then the descriptor can be set in your Stripe settings under Webhook Endpoints:
Image link: https://d.pr/i/eVmVFWIf you’ve set it correctly there (and you’re 100% sure it’s not set anywhere in your site’s code or other settings), but customers are still seeing the wrong statement descriptor, then it must be set somewhere in your Stripe settings on Stripe.com.
We don’t have access to that ourselves, so for that it will be better to explain this to Stripe and ask them for further support.
Hope this points you in the right direction!
Hey @stephunique!
When using the WooCommerce Payments plugin, you won’t be able to access the Stripe dashboard directly. Instead, everything is managed in the Payments menu within your site’s admin dashboard.
The Stripe dashboard is only available if you sign up with Stripe.com directly, and you can then use our Stripe plugin to accept payments on your site.
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] Stripe Subscriptions Not Recurring NowHey @wesleysoccer
As the error message indicates, it appears to be an issue with Elementor Pro:
2021-08-06T08:34:06+00:00 CRITICAL Uncaught Error: Call to undefined method Elementor\DB::get_plain_editor() in /home1/seva/modernzenwarrior.com/wp-content/plugins/elementor-pro/modules/forms/classes/ajax-handler.php:67I’d recommend reaching out to Elementor’s own support team first for any assistance. While we’re experts on our own products, third party plugins are best supported by their own resp. developers (and more importantly, I’d rather not give you any incorrect information).
It looks like that plugin’s info and support page can be found here:
https://elementor.com/help/Hi @mlesniowski
Could you please try the following and see if that works?
1. Go to Apple Pay management in Stripe dashboard.
2. Remove the existing Apple Pay domain
3. Add it again inside the dashboardForum: Themes and Templates
In reply to: [Storefront] Remove page titleHi @laura7979
You can use the following CSS code for this:
.page-id-2 .entry-title, .page-id-568 .entry-title, .page-id-7 .entry-title, .page-id-8 .entry-title { display: none; }Hey @convospanish
For this, we generally suggest using a translation plugin, such as Loco Translate. Using that, you can “translate” specific text in your site to any other text you like.
You can find a step-by-step guide on how to do that right here.
Let us know if that helps!
Forum: Plugins
In reply to: [Sticky Block for Gutenberg Editor] Sticky, only inside a BlockHey @stefank1
If the Sticky Block is placed within another block, it should still be sticky to the screen. Is that what you mean?
Forum: Plugins
In reply to: [Sticky Block for Gutenberg Editor] Update RequiredHey @varunpahwa
Gotcha, thanks for explaining. The reason why it hasn’t been updated in a while, is simply because no bugs have been found/reported that need to be fixed, and at this time there are no improvements for it planned.
It’s basically a case of “if it ain’t broke, don’t fix it” but rest assured that the plugin will be maintained if there’s a need for it (e.g. fixing bugs and/or adding new features if needed).