WPIntell

Source evidence

Some orders not showing icons

Order Status History for WooCommerce · support · 2021-08-26T20:48:00+00:00

mixedsentiment
highseverity
0.94relevance
7replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

6 / 31 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

25 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
khalil43 resolved
Hi, thank you for this great useful plugin! Some orders are not showing icons. i tried to find the common point between them, without success. please check the screenshot https://ibb.co/Q9m5yfb status is completed and just translated. thanks for help The page I need help with: [ log in to see the link] Hello @khalil43 , and thanks for trying our plugin. Not sure yet why some orders aren’t showing icons in your setup. Would you please enable the debug.log and tell if there are any relevant errors? [26-Aug-2021 21:12:21 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:12:26 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:12:29 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:12:30 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:12:50 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:12:51 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:12:56 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:13:01 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:13:05 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 All these notices refer to crm_js , which is related to a different plugin, presumably something CRM/ERP related. Other thing you can do is check for conflicts, by installing the health-check plugin and running it in Troubleshooting mode, with only WooCommerce and our plugin active, and test if things are working properly that way. Note that such test won’t affect other users on a live site. This reply was modified 4 years, 9 months ago by alx359 . Hi, I think i found the common point, the email of the wordpress profile is different than the email in billing and shipping adress.they create an account with one email, then they write another email in checkout. Thanks for your feedback. That’s really a good catch, as the plugin isn’t properly handling such scenario. I was able to reproduce, but please give a few days until the next update that will address the issue. Have just pushed 1.7.0 that should fix the reported issue. I’m closing this ticket now, but please report back if you may encounter anything else. Thanks! Thank you very much, now it is working very good!

Comments

7 shown
alx359 2021-08-26T21:02:00+00:00

Hello @khalil43 , and thanks for trying our plugin. Not sure yet why some orders aren’t showing icons in your setup. Would you please enable the debug.log and tell if there are any relevant errors?

khalil43 2021-08-26T21:15:00+00:00

[26-Aug-2021 21:12:21 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:12:26 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:12:29 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:12:30 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:12:50 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:12:51 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /home/thpcyfmy/public_html/wp-includes/functions.php on line 5535 [26-Aug-2021 21:12:56 UTC] PHP Notice wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the crm_js handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.) in /hom...

alx359 2021-08-26T21:24:00+00:00

All these notices refer to crm_js , which is related to a different plugin, presumably something CRM/ERP related. Other thing you can do is check for conflicts, by installing the health-check plugin and running it in Troubleshooting mode, with only WooCommerce and our plugin active, and test if things are working properly that way. Note that such test won’t affect other users on a live site. This reply was modified 4 years, 9 months ago by alx359 .

khalil43 2021-08-26T21:42:00+00:00

Hi, I think i found the common point, the email of the wordpress profile is different than the email in billing and shipping adress.they create an account with one email, then they write another email in checkout.

alx359 2021-08-27T08:16:00+00:00

Thanks for your feedback. That’s really a good catch, as the plugin isn’t properly handling such scenario. I was able to reproduce, but please give a few days until the next update that will address the issue.

alx359 2021-08-29T16:01:00+00:00

Have just pushed 1.7.0 that should fix the reported issue. I’m closing this ticket now, but please report back if you may encounter anything else. Thanks!

khalil43 2021-09-01T19:30:00+00:00

Thank you very much, now it is working very good!