WPIntell

Source evidence

Compatibility problem

Product Code for WooCommerce · support · 2022-08-02T15:13:00+00:00

mixedsentiment
highseverity
0.95relevance
19replies
Evidence onlycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

1 / 1 rows with source links

100.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

0 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
lisabaldrati resolved
Hi, unfortunately we found a compatibility problem between the “Product Code for WooCommerce” plugin and the “Point of Sale for WooCommerce” plugin. In particular, in the “warehouse” item I found a bug: if I increase or decrease the quantity of the products, I do not see the quantity override under the “warehouse” item Could you help me? Any news? Greetings @lisabaldrati . I will ask the developer to look at this, but there is no compatibility problem. “Point of Sale for WooCommerce” is designed to work only with the native WooCommerce fields. The developers of that plugin would have to include hooks to pass the custom “Product Code for Woocommerce” fields through their plugin for POS use. There is nothing we could do to make custom fields work with that plugin. The best course of action would be for you to ask them to add some code to hook the Product Code fields. Thanks! I confirm the incompatibility with the “Point of Sale for WooCommerce” plugin. If there is a variable product in the cart (that includes a code entered with “Product Code for WooCommerce” plugin), clicking on the POS payment button, the following error appears: Unexpected token ... is not valid JSON This error only occurs with variable products that contain a “Product Code for WooCommerce” code, but not on simple products. I’ll ask the POS developers for the change. Ok thanks. Any news about this “I’ll ask the POS developers for the change.”? his answer ☹️👇 https://wordpress.org/support/topic/compatibility-problem-with-product-code-for-woocommerce-fields/ Hello @flyangel and @lisabaldrati Our previous developer passed 60 days ago. We are still trying to secure a viable developer and think we have one in the works. Hopefully, we can address this quickly if they prove acceptable. It’s painful to find a developer that is good with LAMP and doesn’t charge an arm and leg. Since Artios Media plugins are free, the downside is sluggish results due to no budget combined with unreliable developers. We have great plugin concepts, but currently, our support is dismal. Not the way we operate overall, but how things are. Greetings @flyangel I have setup demo store to check the issue you are facing on checkout process I am unable to reproduce the issue like: Unexpected token ... is not valid JSON Please check this loom video: https://www.loom.com/share/2dc2cc4c7da44331818a56085e0dd491 Can you try to create dev environment with POS, Product Code for WooCommerce and WooCommerce plugin to make sure that you are still facing the issue or not. If you are still facing the issue, kindly request you to let us know the steps to reproduce the issue Thanks This reply was modified 3 years, 7 months ago by iqbal1486 . @lisabaldrati Hey this is Vikrant and i have joined the plugin. I am developer. Please confirm from this screenshot if that is what you have referred as conflict error ? https://paste.pics/KMUTT If this is the correct error then i would like to tell you that i am getting this with all the products even without our plugin “ Product Code for WooCommerce ” active. It will be better if you can provide me more info or screenshot so i can see any data to fix. This error is from POS plugin files and we can not do anything about that. i believe this might be coming due to “Warning: Missing translation for key: “messages.loading” . I can quickly fix the issue if i can see one in our plugin. Regards Vikrant Sampla Hi, sorry but I can’t see the screenshot: https://paste.pics/KMUTT There’s a 404 error @lisabaldrati Hello, I have checked both the plugins POS and Product code on my local server and it is working fine without any issues. It may be some conflict issue with theme or plugin. Could you please share your site admin details or staging environment so I will take backup of your website and setup on my local server and check the conflict issue and get back to you. Hello @lisabaldrati I am plugin developer and I tried with 3 plugins and it working fine – Woocommerce – Point of Sale for WooCommerce – Product Code for WooCommerce Have you any screenshot of error or any process you are doing on your website or could you please let me know which theme are you using or which plugins are you using related woocommerce? So I can check same try to trash what issue is there. Thanks. Hi, thanks for your help. The theme used is Betheme. If you give me your email I can add you as admin in a staging environment. Hi @prashantck , How can I share access to the staging environment with you? Hi @prashantck any news? Greetings, @lisabaldrati . I have had two developers look at it and they tell me the same thing, the “Point of Sale for WooCommerce” plugin is out of date and needs updating. I believe I saw where the author of the plugin acknowledged this was needing to be done but didn’t provide a date to complete the task. As it is, there is nothing we can do on our end. Hi, I have heard the developers of the “point of sales” plugin tell me the following: The plugin (Product Code for WooCommerce) adds a hook on the save_post action that echos (prints) unwanted string that breaks POS’s response. This bug can be found in product-code-for-woocommerce.php on line #172 : https://snipboard.io/Z6BpRd.jpg It also appears that the usage of echo is obsolete, prints out unwanted strings, and can be safely removed from the code. They can also inform the plugin authors of the bug so it can be fixed permanently. The fix: https://snipboard.io/LicPCK.jpg Could you help me please? Thanks @lisabaldrati , that is very helpful. I have asked the developer to apply these fixes asap. Thanks! Hello @lisabaldrati , please let us know if the new version 1.3.5 solves the problem. Thanks!

Comments

19 shown
lisabaldrati 2022-08-05T12:08:00+00:00

Any news?

artiosmedia 2022-08-08T03:47:00+00:00

Greetings @lisabaldrati . I will ask the developer to look at this, but there is no compatibility problem. “Point of Sale for WooCommerce” is designed to work only with the native WooCommerce fields. The developers of that plugin would have to include hooks to pass the custom “Product Code for Woocommerce” fields through their plugin for POS use. There is nothing we could do to make custom fields work with that plugin. The best course of action would be for you to ask them to add some code to hook the Product Code fields. Thanks!

flyangel 2022-09-16T09:34:00+00:00

I confirm the incompatibility with the “Point of Sale for WooCommerce” plugin. If there is a variable product in the cart (that includes a code entered with “Product Code for WooCommerce” plugin), clicking on the POS payment button, the following error appears: Unexpected token ... is not valid JSON This error only occurs with variable products that contain a “Product Code for WooCommerce” code, but not on simple products. I’ll ask the POS developers for the change.

lisabaldrati 2022-09-19T14:58:00+00:00

Ok thanks.

lisabaldrati 2022-11-04T10:18:00+00:00

Any news about this “I’ll ask the POS developers for the change.”?

flyangel 2022-11-04T10:35:00+00:00

his answer ☹️👇 https://wordpress.org/support/topic/compatibility-problem-with-product-code-for-woocommerce-fields/

artiosmedia 2022-11-05T02:05:00+00:00

Hello @flyangel and @lisabaldrati Our previous developer passed 60 days ago. We are still trying to secure a viable developer and think we have one in the works. Hopefully, we can address this quickly if they prove acceptable. It’s painful to find a developer that is good with LAMP and doesn’t charge an arm and leg. Since Artios Media plugins are free, the downside is sluggish results due to no budget combined with unreliable developers. We have great plugin concepts, but currently, our support is dismal. Not the way we operate overall, but how things are.

iqbal1486 2022-11-24T12:29:00+00:00

Greetings @flyangel I have setup demo store to check the issue you are facing on checkout process I am unable to reproduce the issue like: Unexpected token ... is not valid JSON Please check this loom video: https://www.loom.com/share/2dc2cc4c7da44331818a56085e0dd491 Can you try to create dev environment with POS, Product Code for WooCommerce and WooCommerce plugin to make sure that you are still facing the issue or not. If you are still facing the issue, kindly request you to let us know the steps to reproduce the issue Thanks This reply was modified 3 years, 7 months ago by iqbal1486 .

vikrantsam 2022-12-24T21:56:00+00:00

@lisabaldrati Hey this is Vikrant and i have joined the plugin. I am developer. Please confirm from this screenshot if that is what you have referred as conflict error ? https://paste.pics/KMUTT If this is the correct error then i would like to tell you that i am getting this with all the products even without our plugin “ Product Code for WooCommerce ” active. It will be better if you can provide me more info or screenshot so i can see any data to fix. This error is from POS plugin files and we can not do anything about that. i believe this might be coming due to “Warning: Missing translation for key: “messages.loading” . I can quickly fix the issue if i can see one in our plugin. Regards Vikrant Sampla

lisabaldrati 2023-01-12T14:37:00+00:00

Hi, sorry but I can’t see the screenshot: https://paste.pics/KMUTT There’s a 404 error

Prashant 2023-02-01T06:02:00+00:00

@lisabaldrati Hello, I have checked both the plugins POS and Product code on my local server and it is working fine without any issues. It may be some conflict issue with theme or plugin. Could you please share your site admin details or staging environment so I will take backup of your website and setup on my local server and check the conflict issue and get back to you.

Prashant 2023-02-02T06:14:00+00:00

Hello @lisabaldrati I am plugin developer and I tried with 3 plugins and it working fine – Woocommerce – Point of Sale for WooCommerce – Product Code for WooCommerce Have you any screenshot of error or any process you are doing on your website or could you please let me know which theme are you using or which plugins are you using related woocommerce? So I can check same try to trash what issue is there. Thanks.

lisabaldrati 2023-02-02T08:37:00+00:00

Hi, thanks for your help. The theme used is Betheme. If you give me your email I can add you as admin in a staging environment.

lisabaldrati 2023-02-17T16:16:00+00:00

Hi @prashantck , How can I share access to the staging environment with you?

lisabaldrati 2023-02-22T08:07:00+00:00

Hi @prashantck any news?

artiosmedia 2023-02-22T09:27:00+00:00

Greetings, @lisabaldrati . I have had two developers look at it and they tell me the same thing, the “Point of Sale for WooCommerce” plugin is out of date and needs updating. I believe I saw where the author of the plugin acknowledged this was needing to be done but didn’t provide a date to complete the task. As it is, there is nothing we can do on our end.

lisabaldrati 2023-07-03T09:16:00+00:00

Hi, I have heard the developers of the “point of sales” plugin tell me the following: The plugin (Product Code for WooCommerce) adds a hook on the save_post action that echos (prints) unwanted string that breaks POS’s response. This bug can be found in product-code-for-woocommerce.php on line #172 : https://snipboard.io/Z6BpRd.jpg It also appears that the usage of echo is obsolete, prints out unwanted strings, and can be safely removed from the code. They can also inform the plugin authors of the bug so it can be fixed permanently. The fix: https://snipboard.io/LicPCK.jpg Could you help me please?

artiosmedia 2023-07-03T20:33:00+00:00

Thanks @lisabaldrati , that is very helpful. I have asked the developer to apply these fixes asap. Thanks!

artiosmedia 2023-07-03T23:46:00+00:00

Hello @lisabaldrati , please let us know if the new version 1.3.5 solves the problem. Thanks!