sebastianrybacki

Hello,

As I haven’t heard back from you in a while, I’ll go ahead and mark this thread as resolved. However, if the issue still persists, please don’t hesitate to reach out to us through our support form so we can assist you further: Support Form.

We’re always here to help if you encounter any other issues while using our plugin.

Have a fantastic day,

Hello,

I will go ahead and mark this thread as resolved for now. Our developers are aware of this request, and if it gets implemented in a future update, I will make sure to inform you.

Kind regards,

Hello,

I’ve sent this request to our development team, and it will most likely be addressed in one of our future updates. For now, I will mark this thread as resolved. If an update related to this issue becomes available, I’ll make sure to inform you.

Kind regards,

Hello!

Thank you for your message.

Unfortunately, the plugin doesn’t support this yet. The addition of this feature is reported to programmers, but we do not know the date of its implementation.

I will add you to the list of people interested in this functionality, and I will inform you when it happens.

In case of further questions, please contact me.

Kind Regards,

Hi,

Thank you for reaching out!

At the moment, the plugin does not offer such functionality, but I appreciate your suggestion. I’ve added it to our idea base for potential future updates. If we implement this feature, I’ll make sure to inform you.

Kind regards,

Hello,

Thank you for the information. As you mentioned, this doesn’t seem critical, but I’ve passed it along to our development team for review. They will take a look, and if any updates or changes are needed in the future, I’ll be sure to let you know.

Kind regards,

Hello,

Thank you for your follow-up and for continuing to work with us on this issue.

Unfortunately, for security reasons, I am unable to request login details or access credentials on a public forum. Additionally, as my team and I have not been able to replicate the issue in our testing environments, it is difficult to diagnose the problem blindly without being able to reproduce the error.

Given this, it appears that the issue might be tied to something specific within your environment. To identify the cause and provide a solution, we would need to log into your store or, alternatively, have you set up a staging environment where we can troubleshoot the problem directly.

For this reason, I kindly ask you to reach out to us through our support form so that we can securely gather the necessary information and debug the problem efficiently:
Support Form

We’re committed to helping you find a resolution, and this process will allow us to address the issue in a safe and effective manner.

Thank you for your understanding, and we look forward to assisting you further.

Kind regards,

Hello,

Thank you for providing feedback on the issue.

We understand that the problem persists, even with the latest update, and we appreciate your patience. Our development team has noted that the issue does not occur on our standard installations, making it challenging to diagnose without specific details from your environment.

However, since you mentioned that the issue started after version 4.1.9, we suspect it could be related to a filter that was introduced in subsequent versions. To help determine if this is the cause, we suggest adding the following filter to your site’s functions.php file:

remove_filter('woocommerce_enable_order_notes_field', '__return_false');

This filter was added in a particular scenario in recent updates, and it’s possible that it’s causing an unexpected conflict on your installation. Testing this might help resolve the issue temporarily.

That said, to accurately diagnose and fix the problem, we would still need more detailed information from your environment, which unfortunately, we can’t obtain through the forum. We strongly recommend that you contact our support team directly via our Support Form. This will allow us to securely gather the necessary details and, if needed, request access to your staging environment to troubleshoot further.

We’re committed to helping you resolve this issue, and reaching out to our support team will enable us to provide more targeted assistance.

Thank you for your cooperation, and we look forward to helping you find a solution.

Best regards,

Hello,

I haven’t heard from you in a while, so I’m marking this thread as resolved. Please don’t hesitate to open a new one if you encounter other issues while using our plugin.

Have a fantastic day,

Hello,

Thank you for reaching out. Could you please clarify a bit more about where you’re not seeing the variation_id? Some screenshots would be really helpful in diagnosing the issue.

I’ve tested this on my own setup, and when I select a variation in the admin panel, the variation_id is correctly defined. The same applies when ordering from the front-end. Even when I input a custom price, the variation_id shows up correctly in the order details.

If you could provide more details about where the variation_id is missing, it would help us troubleshoot the issue more effectively.

Looking forward to your response!

Kind regards,

Thank you for the 5-star review! I’m glad the plugin met your expectations. Your feedback is truly appreciated ??

Hello,

I haven’t heard from you in a while, so I’m marking this thread as resolved. Please don’t hesitate to open a new one if you encounter other issues while using our plugin.

Have a fantastic day,

Hello,

I haven’t heard from you in a while, so I’m marking this thread as resolved. Please don’t hesitate to open a new one if you encounter other issues while using our plugin.

Have a fantastic day,

Hello everyone,

Thank you for sharing your experiences and the detailed information about the issue.

Based on the feedback from our development team, there were some changes in the recent versions of the Flexible Checkout Fields (FCF) plugin that might be related to the problem you’re encountering. Specifically, there were updates to the hooks used by the plugin, though the older hook names should still be respected. Additionally, there were changes related to hiding the “Additional Information” section in the checkout if no fields are set there. These changes might be contributing to the issues you’re facing, although it’s unusual for them to block the order completion entirely, especially as no errors are appearing in the console or logs.

Given the complexity of the issue and that it seems to work in standard installations, we suspect there might be a specific conflict or configuration on your sites that is causing this. Unfortunately, it’s difficult to diagnose without further details.

To help us investigate further and resolve this issue, could you please reach out to our support team directly via our Support Form? This way, we can gather the necessary information in a more secure and private manner, and potentially request temporary access to your staging environment to replicate and troubleshoot the issue directly.

We appreciate your understanding and look forward to helping you resolve this as soon as possible.

Kind regards,

Hi Shandy,

Thank you for reaching out to us.

Unfortunately, the current version of the plugin does not support conditional logic to show Field A if Field B is ‘Not empty’. However, I have noted your request and forwarded it to our development and product teams for consideration. If we implement this feature in the future, we will be sure to inform you.

If you have any more questions or need further assistance, please feel free to contact us.

Kind regards,