Hi,
The key to finding a solution is to find the cause. First of all, in order to ensure the issue is actually caused by a plugin malfunction, use the following clean installation: https://codecanyondemo.work/wcccf/wp-admin/ (user: demo, pass: demo) to recreate the scenario that leads to the issue you are experiencing. If so, please report to me how to experience it.

If not experiencing any issue, most likely the issue you are experiencing could be caused by a 3rd party issue. Try then to perform the steps that lead to the issue in your installation, disabling one by one all the 3rd party plugins, and see if you are still experiencing the issue. Try also to enable the WordPress debug mode and debug log to see if any further clue is reported in the debug.log (located in the wp-content folder).

If you have altered in any way the checkout form and/or workflow, restore the original template and workflow.

In order to ensure the issue is actually caused by a plugin malfunction, use the following clean installation: https://codecanyondemo.work/wcccf/wp-admin/ (user: demo, pass: demo) to recreate the scenario that leads to the issue you are experiencing. If so, please report to me how to experience it.

>> My problem is that the error does not always occur, but only sometimes, so I don’t know how to replicate the error and how to replicate my scenario. You mean I should install and enable the same theme and plugins I have on my website?

If not experiencing any issue, most likely the issue you are experiencing could be caused by a 3rd party issue. Try then to perform the steps that lead to the issue in your installation, disabling one by one all the 3rd party plugins, and see if you are still experiencing the issue. Try also to enable the WordPress debug mode and debug log to see if any further clue is reported in the debug.log (located in the wp-content folder).

>> I can’t, I need to keep the 3rd party plugins active. But I’ve enabled the debug log.

If you have altered in any way the checkout form and/or workflow, restore the original template and workflow.

>> I can’t, I need to keep the 3rd party checkout plugin active.

In short words, I need your help to find the cause of the issue but I canìt disable any plugin on my website. Do you have any other suggestion?

Just a last question: can we manage this support request by mail? Using comments seems a bit impractical to me.

Thanks!

I’m sorry, but if I cannot replicate the isse I cannot perform any analysis to determine the cause and eventually suggest a solution.

Other than the methods I’ve suggested to try to isolate and identify the cause, there aren’t other ways.

I guess the only way to replicate the issue is to make an exact copy of the website with the same plugins installed. And, since the error doesn’t occur every time, do many test orders until one of them fails. So, do you think you can help me if I make a copy of my website? If I create a copy of the site, could you run some tests and see if the problem occurs?

What you should do is try to recreate the issue exactly. If it occurs even after disabling the other plugin, then I can help by performing some analysis on my plugin code.

If the issue is caused because, for example, a 3rd party plugin hooks during the checkout process, preventing other plugins (like mine) from being able to process the checkout data (and so associate field data to the order), there isn’t much I can do.

My problem is that I don’t know how to recreate the issue, as it seems to happen randomly.

Just to be clear: I don’t need help solving the issue, since I don’t even know what the issue is. I need help FINDING THE CAUSE of the issue. So, can you help me find the cause of the issue or did I renew my support licence for nothing?

I understand that the situation is not easy to manage, since there are many third-party plugins active on my site… but in the end the only plugin that seems to be malfunctioning is yours, so I really don’t know who else to ask.

Thank you.

I’m really sorry, but what I would do is the same as I’ve reported earlier. There is no additional action I can take to help you find the issue. Indeed, the plugin does not work, but this doesn’t mean the issue is related to the plugin code. For example, the plugin hooks to the woocommerce_new_order_item action triggered by WooCommerce after the order has been placed to associate data with the order item. If a 3rd party, for some reason, prevents that action from being triggered, this doesn’t depend on a plugin malfunctioning, and there isn’t any action it can perform to avoid.

In any case, the key is to replicate the issue so I can eventually perform a proper step-by-step debug of the plugin code. It is not even possible; there isn’t much I can analyze to have a clue about the real cause.

Hi, it’s me again

Ok, I understand that you can’t help me if I can’t reproduce the issue… it’s logica indeed. So I’d like to try another approach.

I would like to activate a log for every possible operation performed by the plugin so that I can then compare the logs of a correct order and an incorrect order in order to identify the problem.

I know how to create a custom log (I’ve found this useful guide: https://www.businessbloomer.com/woocommerce-create-custom-logs/) but I don’t know which actions to use as ‘hook triggers’ or exactly which data to log, so I’m asking you to list every useful “hook triggers” and data so that I can create the functions to generate all the custom logs i need.

I understand that this request may be a little beyond what is normally expected from support, but I really don’t know what else I could try to do to identify the cause of the problem. I hope you understand

Just a last question: I’ve found out you’re italian and I’m italian too, maybe I can start write in italian? I guess it would much easier for me

Thanks in advance

Ciao, sì possiamo parlare in italiano.

Quello che potresti fare allora è modificare il file WCPFP_Checkout.php. Alla linea 14 troverai la definizione dell’handler dell’action woocommerce_new_order_item. L’handler è la funzione add_field_meta_to_order_item_meta definita nella linea 187.

Questo action è “sparato” da WooCommerce durante la creazione degli “items” (cioè i prodotti) da associare all’ordine durante la creazione dell’ordine stesso dopo la fase di checkout. Da quello che scrivi, sembra che quest’operazione ogni tanto non venga eseguita.

Quello che potresti fare è creare un log in cui tieni traccia degli ordini creati (se non mi sbaglio quando un ordine viene creato dopo il checkout, WooCommerce “spara” questo action: woocommerce_checkout_process) e vedere se questo handler viene di conseguenza eseguito. Se non viene eseguito, controllare se nel log di debug di wordpress alla stessa data, sono riportati dei errori.

Hi,
The plugin is fully compatible wth the latest WooCommerce and WordPress versions.

If you haven’t altered the software in any way, the issue could be caused by 3rd party interference.

To continue having support, you need to use the account you used to purchase the plugin with a valid support license associated wth it.

Hi, thanks for your reply. Sorry I wrote you from the wrong account. Ok, I’m gonna renew the license and contact from the right account.

Just a further question: right now my license is expyred, if I renew my license you will help me fix the issue even if the issue is caused by a 3rd party plugin?

I mean, I don’t want to renew the license only to be told that you can’t fix the problem because it’s caused by another plugin. It’s happened to me before, and I’d like to avoid it

Thanks, please let me know

The plugin hasn’t any option for that.

The date field is however managed by the field-renderer.js (js folder) at line 119. You can add the date to disable by adding this option: https://amsul.ca/pickadate.js/date/#disable-dates . is an array containing the dates to disable.

Thanks, that looks to be exactly what I need, However, any edits that I make here do not seem to have any effect on the dates shown in the date picker.

I also tried some non-date changes such as changing the text on the close button (close: ‘Cancel’), but this did not affect the date picker.

I disabled all other plugins, in case of a conflict, but it still behaved the same with no changes to the date picker.

Am I missing something?

Thanks

Thank you for your purchase. The plugin doesn’t offer any shortcode. It automatically renders the fields after the checkout billing/shipping form. Ensure to be using the default checkout template ([woocommerce_checkout]) otherwise, WooCommerce won’t trigger any action allowing the plugin to render the fields.

I entered the HTML code to do shortcode. And yes I’m using classic checkout.

Hi,
the key is to properly identify the cause of the issue and implement the solution. It would be important to understand if a plugin malfunctioning or a 3rd party interference causes the issue.

If you can provide a precise step-by-step guide on how to experience the issue, eventually using this site: https://codecanyondemo.work/wcpfc/ (user: demo, pass: demo) I can perform some further investigation and analysis, determine the cause, and then implement a fix.

Thank you for your collaboration.

Hi, thank you very much for your quick reply.

Unfortunately I don’t have a step-to-step guide to experience the issue, I cannot identify a specific cause for every time this issue occurs. As far as I know, most times it does not happens but few times it happens, and I really don’t know why

If you like, I can provide you an access to a copy of my website on a DEV enviroment, so you can have a look by yourself. Please let me know if we can proceed in this way and how I can privately send you the credentials to access the DEV website.

Thanks again. PS: I’just noticed you’re located in Italy, I’m italian too

Yes, I’m located in Italy!

Unfortunately If you do not report a guide on how to replicate the issue, it is quite hard to know what to do to make the issue raise and investigate the possible cause.

You could eventually do it in the following way: enable the WordPress debug mode, disable the debug display, and enable the debug log by entering the following in the wp-config.php file you find in the root of your WordPress installation:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'WP_DEBUG_LOG', true );

wait for the issue to re-happen and then give a look to the debug.log located in the wp-content folder to see if any message related to a crashing script is reported. It could be a script of the Product Fields plugin or a 3rd party plugin that is crashing prevents the Product Fields script from being properly executed an so associates the field data with the order.

Hi,
the VAT number field is a field created with the plugin? From my tests, the plugin works even with the latest version of WooCommerce and WordPress. Are you sure that the issue is not caused by a crashing javascript library of other 3rd party plugins/theme? That issue might lead the browser to not properly execute the plugin javascript libraries.

In order to not miss anything, please try using this clean installation of the plugin: https://codecanyondemo.work/wcpfc/ (user: demo, pass: demo) and recreate your scenario. Let me know if you experience the issue and how to. Thank you.