Category: Common issues
-
I have iThemes Security plugin and Wise Chat Pro stopped working. How to fix it?
The shortest answer would be: Please go to WordPress Dashboard > Security > Settings > Advanced > System Tweaks and uncheck “Disable PHP in Plugins”. Then click Save button. Wise Chat Pro executes PHP files directly in /wp-content/plugins/wise-chat-pro/src/endpoints/ultra directory on your server. It is done strictly for performance because the standard admin-ajax.php endpoint is too…
-
How to fix “No channels open” message?
First, please try clearing the cache of your browser including Local Storage (this is crucial). Wise Chat Pro uses cache to store some part of its temporary data. In a very rare cases it requires to be cleared manually. If this does not help please follow these advices depending on your configuration: A single public…
-
Auto-scrolling does not work. How to fix it?
Our chat is designed to auto-scroll messages when a new message is posted. This way any new message becomes immediately visible for chatters. However, you may want to read past messages without being auto-scrolled down. We solved it this way: when you scroll up to see past messages the auto-scrolling feature becomes disabled. You can…
-
When I try to activate the plugin I get fatal error: Cannot redeclare wise_chat_after_setup_theme_action()
When you try to activate Wise Chat Pro and you get the following error: Fatal error: Cannot redeclare wise_chat_after_setup_theme_action() …. It means that you also installed free Wise Chat plugin. Both free and Pro version cannot operate together. Please delete free Wise Chat first. Then please install and activate Wise Chat Pro.
-
My messages are not visible until I refresh the page. What is going on?
In order to get new messages the chat is requesting the following URL: https://yourdomain/wp-content/plugins/wise-chat-pro/src/endpoints It is very likely the URL is is forbidden in your setup (403 error). It may be caused by a security plugin or theme. A specific configuration of HTTP server (.htaccess file or server settings) may be the reason too. Please…