Plugin Author
Rafin
(@rafinkhan)
@girlgold,
Hi, there. I am sorry to hear that you are facing some issues with NotificationX. Regarding the console errors, I will have to check before commenting on anything. The link you have provided doesn’t actually work so I couldn’t check as a result. Can you please take a look at this?
Adding Custom CSS option sounds like an interesting idea. I will talk this over with our dev team and maybe, we will even implement this in the future. Thank you for your suggestion.
Thank you for your wonderful feedback as well. Have a nice day!
Hi,
Thanks for your reply! Could you try .com rather than .ca with the original URL provided?
Thanks!
Leanne
Hi,
Have you managed to take a look at this? Do you have any updates or suggestions for what I could try?
Thanks!
Looking forward to pushing a fix on Thursday’s update, stay tuned.
Plugin Author
Rafin
(@rafinkhan)
@girlgold,
Hey, how are you doing? We have released a new version of NotificationX today with few improvements. So, can you please update to the latest version and check back? Let me know how it goes.
Thank you!
Hi! Thank you so much for looking into this. I’m super impressed with your support!
I just updated to the latest version and I’m still seeing the increasing console errors in the site with the URL I provided earlier. Let me know if you see something different or if there’s anything else you’d like me to try in terms of troubleshooting.
Thanks again!
Plugin Author
Rafin
(@rafinkhan)
@girlgold,
Hi, there. Well, we have investigated your website and it seems very strange. It’s difficult to say judging by the errors whether they are coming from NotificationX or not. Have you tried disabling Tawk and check back?
Besides, Even after deactivating NotificationX, if you are still getting these errors, we will have to actually deeply investigate your website to find the root cause of the issue and resolve it. For that case, can you please contact us here.
Thank you!
-
This reply was modified 6 years, 1 month ago by
Rafin.
Thanks for looking into this!
I’ve disabled the Notification X plugin on the staging.wpengine.com site provided. You can see that the Uncaught TypeError notifications in the console have disappeared, so we can indeed infer that the plugin is causing them.
On the staging.wpengine.com site we actually don’t have Tawk up and running, and we can see that the large amount of console errors is still present when the Notification X plugin is activated. On the live version of the site we do have Tawk activated, but since a conflict with Tawk doesn’t appear to be causing the errors I don’t think that disabling Tawk would be helpful.
If you need admin access to the site to experiment with the effect of activating and disabling the Notification X plugin, please let me know.
Thanks!
Plugin Author
Rafin
(@rafinkhan)
@girlgold,
Yes, please contact us here for further support as we need more investigation: support[at]wpdeveloper[dot]net
Thank you
Plugin Author
Rafin
(@rafinkhan)
@girlgold,
Hey, there. seems like you have found out the issue (not related to NotificationX) and I am glad that it’s resolved now.
I am closing this ticket now. Have a nice day!