kognetiks

Hello Alex,

Thank you.

I’ll leave this issue open until I can push out an update.

If you find there is additional info you can share, send it along here or directly to me at support @ kognetiks dot com.

Best,

Stephen

Alex,

What needs to happen here it table create needs to happen only on activation or upgrade.

I was originally worried about making sure that the table was altered with the new layout.

Most likely it’s an artifact left over from my development envirnoment.

I’ll move it and release a version 2.2.7.

As for the transients, these facilitate the asynchronous nature of the chatbot and UI/UX interactions.

The transients keep track of key chatbot attributes so that you can leave the page and return to it later and the chatbot doesn’t loose it’s place.

One optimization that I can do is see if I can load the data into an array and make one transient do all the work rather than have several, thus collapsing several DB calls into one DB.

I’ll see what I can do in the next release. It depends on how complicated it gets to untangle this.

You mentioned that “seems that the script cannot write to the table”. Can you expand on that?

Best,

Stephen

Hello Alex,

I noticed this “ALTER TABLE” call as well when I fired up a fresh version of the chatbot.

Can you edit the main plugin file (chatbot-chatgpt.php)?

Let’s try commenting out lines 932 and 935.

You can put a “//” in from of the call to the create_chatbot_chatgpt_assistants_table() so that it reads

// create_chatbot_chatgpt_assistants_table();

Then do the same for the create_cvhatbot_azure_assistants_table() too

// create_chatbot_azure_assistants_table();

Then let’s see if responsiveness improved.

I’m investigating this to see if there is a problem there.

Best,
Stephen

Hello awegerer (@awegerer) Alex,

Thanks for reporting this. Since the slowdown happens on all pages, even those without the chatbot, it’s likely that something is being loaded or executed globally.

To help diagnose this, could you try the following:

1. Enable Query Monitor – This will help identify slow queries and excessive API calls, as well as a comprehensive view of your installation. You’ll find it here:
   https://www.ads-software.com/plugins/query-monitor/
2. Check for AJAX Calls – Open the Network tab in your browser and see if what might be related to chatbot-chatgpt or other chatbot-related requests are running on non-chatbot pages.
3. Temporarily Disable Chatbot Session Storage – If possible, test by disabling session storage or transients related to the chatbot.
4. Monitor Memory Usage – Add this temporary function in functions.php:
   
   function debug_memory_usage() { error_log('Memory usage: ' . (memory_get_peak_usage(true) / 1024 / 1024) . ' MB'); } add_action('shutdown', 'debug_memory_usage');
   
   Then check wp-content/debug.log after loading pages.
   
5. Turn On Debug Mode – If you haven’t turned on debug mode, you may need to do so in your wp-config.php file:
   
   define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

I’m actively investigating this, and I’ll keep you updated on potential fixes. Let me know if you find anything in Query Monitor or the debug logs!

Best,
Stephen
[email protected]

Hello Geleosan (@geleosan),

Do you have are you using the Knowledge Navigator to index your site? If so, is there published content that would mention the best beaches?

On the Knowledge Navigator tab of the Chatbot, you can try increase the “Maximum Top Words” and the “Tuing Percentage”. Both of these factor into how deep the Knowledge Navigator will go when creating a TF-IDF map of you site.

At the bottom of the same tab, you can “Download Data” (in csv format) and inspect your content to see if the expect key words are present.

Alternately, have you consider using an Open AI Assistant with more specific knowlege?

Let me know what you learn.

Stephen

Hello dwsowash (@dwsowash),

In order to enable the Sentential Model as an option take these steps:

1. Navigate to the Messages tab
2. Scroll down to the bottom of the page
3. There you will find the Beta Feature Settings
4. Set Enable Beat Features to YES
5. Then click the Save Settings button
6. After the page reloads, navigate to the General tab
7. Set teh AI Platform Choice to Transformer
8. Scoll to the bottom of the General Tab ans click the Save Settings button
9. After the page reload, navigate to the API/Transform tab
10. When the Transform settings page loads, you can adjust the Advanced Settings for the model.
11. If you make changes to the Settings be sure to click the Save Settings button

If you have any feedback on this option, please let me know.

Respectfully,

Stephen

Hello everyone,

It came to my attention that this might be an issue with Firefox.

I just deployed a fix in Version 2.1.8 that seems to have resolved this problem.

Let me know if this continues to be a challenge.

Thank you for your patience.

Thank you for using the Kognetiks Chatbot for WordPress

Respectfully,

Stephen

Hello rolandpr (@rolandpr),

Thank you for the compliment! I appreciate the positive feedback.

I just released version 2.1.6 to the Plugin Directory.

Please update the chatbot to the latest version at your convienece.

Once, you do, then proceed to the Messages tab, then scroll down to the Messages and Diagnostics Settings and change the Chatbot Diagnostics to “Error”.

I’ve greatly enhanced the error handling for various tables included the assistant’s table.

If you experience any errors, proceed to the Tools tab where you may see an error log just for the chatbot. You can use the “Download” button to retireve the log and save it locally. It’s a text file.

This log will be very helpful in determining if there is an error in the code.

However, you’ll still want to monitor the debug.log found in the wp-content folder of your WordPress installation. This file in conjunction with the chatbot error should inform us where the error is occuring and why.

I appreciate your help in resolving this issue. Please keep me posted here or directly at support at kognetiks dot com.

Regards,

Stephen

Hello rolandpr (@rolandpr),

I’m going to add some additional error handling to the assistant table actions in the next release for the chatbot (2.1.6) which should be push to the Plugin directory tomorrow morning. I have a bit more testing to do. In that version, if you have turned on error logging in you WP instance, we should be able to catch the error and figure out what is not working here.

You’ll want to turn on error loggin in your wp-config.php file.

define('WP_DEBUG', true);
 define('WP_DEBUG_LOG', true);
 define('WP_DEBUG_DISPLAY', false);
 define('SCRIPT_DEBUG', true);
 @ini_set('display_errors', 'Off');

You’ll wnat to enable WP_DEBUG so that we can catch the errors after the plugin is updated.

Stephen

Hello rolandpr (@rolandpr),

If you have access to phpMyAdmin, from the admin interface to find and delete/drop the chatbot_chatgpt_assistants table, then the table will be recreated when you reactivate the plugin.

You’ll want to open phpMyAdmin, select your database from the list on the left hand vertical column. Then select the “_chatbot_chatgtp_assistants” table from the list of tables in your DB. Now click on the Operations tab. Scroll to the very bottom, click the “Delete the table (Drop)”, confirm the delete. Then reactivate the plugin. The table will be created again. You should now be able to add/modify/delete assistants from the table.

Note: Any information in the table will be deleted by this action. If you don’t have this data elsewhere, please record it.

Reminder: Always backup your database before making any changes to ensure data safety and prevent loss.

Feel free to reach out to me directly at support at kognetiks dot com.

Stephen

• This reply was modified 5 months, 3 weeks ago by kognetiks.

Hello everyone,

I’m starting to work on this now. I’m not sure just how much effort this will take. It may require rewrite some core functions. But, I’ve started on it.

Stephen

Hello michalwoszczyk (@michalwoszczyk),

I’m pleased to inform you that Version 2.1.2 of the chatbot plugin has been released and is now available in the WordPress Plugin Directory.

This update addresses the issues identified in Version 2.1.1 and should resolve any problems you may have encountered. I sincerely apologize for any inconvenience caused by the previous version and appreciate your understanding as we work to improve the plugin.

Please take a moment to update to the latest version to ensure optimal performance.

Thank you for your continued support.

Stephen

Hello lmg7 (@lmg7),

I notice that there is an error (see screen gab below) referencing the variable “plugin_vars”.

In the latest release of the chatbot, I changed “plugin_vars” to “kchat_plugin_vars” to removed a conflict with another plugin.

I’m thinking this is a server and/or plugin caching issue. If you’re running a caching plugin, can you clear (or delete) the cache and try to load the page again?

You might also need to stop/start your server to clear any server cache.

Let me know if this resolves your problem.

Stephen

• This reply was modified 7 months, 1 week ago by kognetiks.
• This reply was modified 7 months, 1 week ago by kognetiks.

Hello?Charlie312cz?(@charlie312cz),

Since I haven’t heard back from you in the last few days, I assume that your concern or issue has been resolved.

Should you have any further concerns or issues, please do not hesitate to contact me.

Stephen

Hello?moritzllm?(@moritzllm),

Since I haven’t heard back from you in the last few days, I assume that your concern or issue has been resolved.

Should you have any further concerns or issues, please do not hesitate to contact me.

Stephen