nikkers
Forum Replies Created
-
In the page/post editor screen to enable/disable would be good. (Probably easier as having seperate tab or page that collects all posts and pages could become cumbersome)
Cron unschedule event error is now not showing in Version 2.3.2. Thanks for persisting with finding a fix.
Also a feature request: could the Pinecone Knowledge Base manager have indidual selection to delete the selected items in bulk?
Hi Maxwell – v 2.2, deleted the error, cleared cache, restarted site and this still shows:
Cron unschedule event error for hook: mxchat_reset_rate_limits, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”hourly”,”args”:[],”interval”:3600}In 2.2.0 the error still appears for:
Cron unschedule event error for hook: mxchat_reset_rate_limits, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”hourly”,”args”:[],”interval”:3600}
is this “old from the previous version?” meaning I delete the cron event: mxchat_reset_rate_limits?MxChat_Integrator->mxchat_reset_rate_limits()
wp-content/plugins/mxchat-basic/includes/class-mxchat-integrator.php:4417- Re:” rate limits are working as expected for all user roles EXCEPT for administrator role.”
v 2.2.0 now uses rate limits for admin role - Error Log Monitor Pro for error logging and Ultimate member pro for roles: https://profiles.wordpress.org/ultimatemember/
- This reply was modified 1 year, 5 months ago by nikkers.
Thanks – have updated to 2.1.9 and still have same error of:
Error – Cron unschedule event error for hook: mxchat_reset_rate_limits, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”hourly”,”args”:[],”interval”:3600}Timestamp: 2025-05-09 02:06:56 UTCCron job:
Cron item is: mxchat_reset_rate_limits
Once Hourly MxChat_Integrator->mxchat_reset_rate_limits()
wp-content/plugins/mxchat-basic/includes/class-mxchat-integrator.php:4417
Am also asking hosting support if any issues from their end.- This reply was modified 1 year, 5 months ago by nikkers.
Test the 1st item – rate limits are working as expected for all user roles EXCEPT for administrator role. Have emailed the error log directly to you.
It works:
MxChat cleanup: Removed 1 orphaned chat history entries is in the logfile and the mxchat_history_mxchat_chat_xyz is removed from table options when the chat transcript is deleted.
Thanks!I had same error – found disabling XML-RPC caused it. Suggest look for options that “Disable XML-RPC,” “Block XML-RPC,” or “Limit XML-RPC Access.”
- we have: webpc_cloudflare_cache_purge: yes
So it has successfully connected to the Cloudflare API. Thanks! - So for webpc_cloudflare_cache_config it states 403. “webpc_cloudflare_cache_config: 403”. This means for a free Cloudflare account it is always getting the images from the origin server?
Brave search works thanks
Update – I replied too soon…. In 2.1.4 it does not populate the API or add question field, however if the browser and/or server cache is cleared it still populates both fields.
Also – the page often sends the message “Error saving: Update failed or no changes”Fixed thank you – browser is NOT filling the Loops API field or the added questions.
- This reply was modified 1 year, 6 months ago by nikkers.
yes – on “Loops API field and not any of the other API fields such as the chat or embedding model APIs” AND “Additional Quick Questions field”
It does look like auto filling from the browser.
Thanks - Re:” rate limits are working as expected for all user roles EXCEPT for administrator role.”