开发者 |
fluidwebco
diegoversiani luiggiab |
---|---|
更新时间 | 2024年12月11日 23:10 |
PHP版本: | 5.0 及以上 |
WordPress版本: | 6.7.1 |
版权: | GPLv3 or later |
版权网址: | 版权信息 |
Yes. You can view all details and list of features of the Fluid Checkout PRO version on our website.
Yes! Fluid Checkout should work with most theme out-of-the-box. However some themes may need adjustments due to not using WooCommerce standard hooks or styles or if they add their own customizations which might conflict with Fluid Checkout. If you have any issues using Fluid Checkout with your theme please let us know through the support forum and we'll fix it asap.
Although Fluid Checkout was built in a way that it should be compatible with most plugins, the checkout page is a really complex part of WooCommerce and there are myriads of plugins that extends it. Because of that, it is likely that some plugins won't work optimaly with Fluid Checkout out-of-the-box. If you have any issues using Fluid Checkout with other plugins please let us know through the support forum and we'll fix it asap.
We value your privacy and your customers' privacy. While we cannot guarantee that the plugin is fully compliant with privacy laws in every country. We assure you that Fluid Checkout does not, and will not, collect any customer data from your shop. In the future, and with your explicit consent, we might collect some non-sensitive usage data from your website such as the plugin and WooCommerce settings, which other plugins and themes you have installed on your shop to help us to improve the plugin. Details and examples of the data collected will be shown on the plugin interface for you to review prior to sending the data to our servers for collection and storage.
No. While Fluid Checkout does improve the accessibility of the checkout page by implementing support for keyboard-only navigation and screen readers, we can't say if your webshop will be 100% compliant or not with ADA, WCAG or any other accessibility requirements. Did you know that only about 30% of accessibility issues can be detected with automated tools? The majority of the issues can only be detected with manual testing on each page of the website. Read the article: Automated Accessibility Testing Tools: How Much Do Scans Catch?. We have plans to add an "accessible layout" feature that will ensure most accessibility issues will be fixed.
The plugin provides widget areas in strategic positions on the checkout page for adding the trust symbols. Head over to WP Admin > Appearance > Widget Areas, and add any type of widget to boost the perceived trust customers have on the website.
fc_substep_text_contact_field_keys_skip_list
to allow skipping displaying some fields in the contact substep review text.select2
component from the plugin when using the enhanced select fields (with TomSelect
) from Fluid Checkout.fc_force_register_steps
as checkout steps and substeps needs to be registered for some functions to be available.fc_checkout_before_step_<step_id>
and fc_checkout_after_step_<step_id>
and replaced them with fc_checkout_before_step
and fc_checkout_after_step
which passes the step id as a parameter.fc_checkout_start_step_<step_id>
and fc_checkout_end_step_<step_id>
and replaced them with fc_checkout_start_step
and fc_checkout_end_step
which passes the step id as a parameter.$is_sidebar_widget
from action hooks fc_checkout_before_order_review
, fc_checkout_before_order_review_inside
, fc_checkout_after_order_review_title_before
, fc_checkout_after_order_review_title_after
, fc_checkout_order_review_sidebar_before_actions
, fc_checkout_after_order_review_inside
, fc_checkout_after_order_review
.fc_proceed_to_next_step_button_label
to allow more control when changing these button labels.overflow: hidden
from styles to allow elements to be displayed.optional_expand_link_label
directly when setting the optional field expansible link button label. The link label should now contain the Add
part as well as the desired field name.$context
for the hook fc_css_variables
. Defaults to frontend
.