Text entries of type text are no longer saved in woocommerce orders

Hey @luca224,

Can you share more details that might help replicating this, please?

I tried replicating, but it works as expected on my end – https://vertis.d.pr/i/wLxMuB.

The text inputs ” Zeile 1″, “Zeile 2”, “Zeile 3” are displayed in the front end contional, depending on what you enter in the “select” field. This means that the text inputs that are conditional but have been filled in are not saved in woocommerce.

• This reply was modified 9 months ago by luca224.

@andreearadacina21

As with my ticket about required conditional fields this problem is also linked to a field being conditional on another field.

As I see more problems posted they all seem to link back to the fact there are problems with any field type when it is conditional on a prior field.

If you test and make some fields, text, radio or anything else , conditional, you will see that any answer given in the conditional fields is dropped in the cart/checkout and back-end order page.

• This reply was modified 9 months ago by esd3104.

I confirm that this problem also happens on my page. I can’t know the client’s selection when the field is conditional on a previous one.

Hey @luca224,

We appreciate your cooperation in reporting the issue you’re encountering. We are sorry for the inconvenience, and we have confirmed the problem. A bug report has been created and forwarded to our product development team for review.

What happens next?

Our product team will evaluate the impact of this issue compared to other open bugs and upcoming features, and assign a priority level to the bug report.

Our developers prioritized this as the highest-priority issue, so we expect a resolution soon.

If you have any additional information that may assist with prioritization or resolution, feel free to reply to this email.

We will update you once the issue is addressed and a fix is released. You may also check the product’s changelog for updates and fixes in each release.

If you have any additional questions or concerns, please feel free to start a new thread. Again, we apologize for the inconvenience and thank you for your patience.

cc: @jplerida, @esd3104 (and thank you for being actively engaged in our community ????)

Hi?@luca224,

I hope this message finds you well. I am pleased to inform you that we have recently released an update for PPOM. This update includes a resolution to the issue you reported.

We appreciate your patience and support during this process. If you have any further questions or require assistance with the update, please do not hesitate to reach out.

Wishing you a great day ahead!

Also problem for me in 32.0.12. I updated to most recent 32.0.13, didn’t fix it – unless it cached something, I didn’t test that.

Switching to Legacy Field inputs fixes it.

I suggest devs switching back to Legacy by default in this plugin until the issue is properly resolved.