Flexible Checkout Fields PRO WooCommerce

Download Link:

This is a support topic for Flexible Checkout Fields PRO WooCommerce

The intention of this topic is to give you the opportunity to discuss problems and difficulties with other Festinger Vault customers, e.g. how to address incompatibilities or fix bugs, report malfunctioning features, or get help on how to configure this download.

:warning: You can ask us for update requests here as well! :love_you_gesture:

To request an update of a particular theme or plugin, kindly let us know your preferred version number and we will update it as soon as possible. Although update requests usually do not make much sense because we publish them as soon as they are available and we have the time to upload them.

Please update to version 3.2.4

1 Like

Flexible Checkout Fields PRO WooCommerce has been updated to 3.2.2

Please update to 3.2.5

We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.

Meanwhile, please have a look at this thread which explains the entire process. :slight_smile:

Hi, Is it possible to update to 3.3.0?

1 Like

Flexible Checkout Fields PRO WooCommerce has been updated to 3.2.6

Why not update to 3.3.0?

We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.

Meanwhile, please have a look at this thread which explains the entire process. :slight_smile:

Flexible Checkout Fields PRO WooCommerce has been updated to 3.3.0

Please update Flexible Checkout Fields PRO WooCommerce 3.3.0 to 3.4.2. @Steve

We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.

Meanwhile, please have a look at this thread which explains the entire process. :slight_smile:

Please update Flexible Checkout Fields PRO WooCommerce 3.3.0 to 3.4.4. @Steve

We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.

Meanwhile, please have a look at this thread which explains the entire process. :slight_smile:

Please update Flexible Checkout Fields PRO WooCommerce 3.3.0 to 3.5.0. @Steve

We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.

Meanwhile, please have a look at this thread which explains the entire process. :slight_smile:

Please update Flexible Checkout Fields PRO WooCommerce 3.3.0 to 3.51. @Steve

We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.

Meanwhile, please have a look at this thread which explains the entire process. :slight_smile:

Please update Flexible Checkout Fields PRO WooCommerce 3.3.0 to 3.5.1. @Steve

We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.

Meanwhile, please have a look at this thread which explains the entire process. :slight_smile: