Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thanks for update. Please send the post-update log file (even if there are no messages in log, it contains extended information about your installation) to [email protected].

    [email protected] is the email for communication with development team. You can see this address on the plugin’s “Set Up Chatbot” > “Having Issues” page in WordPress dashboard.

    Hello, victordella.

    Dev tem is aware of the issue you described and development team is developing and testing fix for it that will be released as soon as possible. It would be helpful if you would send development team your extended log file downloaded from “Set Up Chatbot” > “Having Issues?” page of the plugin settings to the email address specified on this page.

    If it’s the issue I’m talking about, you may upgrade you database version to MySQL 5.7.8 or higher or MariaDB 10.2.7 or higher as a temporary workaround.

    If you have any more questions, feel free to ask them.

    Hello rosboc.

    Thanks for sharing your error message and software version. Right now plugin has a compatibility issue with older versions of MySQL and MariaDB. The fix for it is developed and dev team now tests it. It will be released at the beginning of the next week. As a temporary workaround you may upgrade your MySQL to version 5.7.8 or higher or MariaDB 10.2.7 or higher.

    If you have any more questions or issues, feel free to share them.

    • This reply was modified 5 years, 12 months ago by kaneua.
    kaneua

    (@kaneua)

    The fix for your problem is included in the new version of the plugin (0.8.6) that was released a few days ago. Please update the plugin on your website (you still have 0.8.5 installed) and let us know if the issue persists.

    • This reply was modified 6 years ago by kaneua.
    • This reply was modified 6 years ago by kaneua.
    kaneua

    (@kaneua)

    It seems like you set up force redirect from https://kinoa.tech/index.php?rest_route=/watsonconv/v1/message to exactly the same address with code 301. It’s a problem with your server configuration and there are two issues with it:

    • It forces redirect to https version for this address even if https address is already requested
    • Redirect with code 301 does not preserve POST method, therefore it redirects to the same address

    You can reproduce that behaviour by going on any of your site’s pages (for example, front page, not error pages or nonexistent ones). Open developer console and execute Javascript code below (copy there, paste in cosole and hit Enter) to recreate normal chatbot request from widget. Let’s assume that you use Chrome, but this example won’t be much different in any other modern browser.

    // Simulating normal request from chatbot frontend
    
    // Creating legal object for sending user input
    // null in session_id tells that there is no session yet and plugin should create one
    var testUserInput = {
        input: {
            message_type: "text",
            text: "test text" 
        },
        session_id: null
    };
    // Serializing test user input to JSON
    var jsonUserInput = JSON.stringify(testUserInput);
    // HTTPS Address to send request to
    var testAddress = "https://www.kinoa.tech/index.php?rest_route=/watsonconv/v1/message";
    // Object representing server request
    var testRequest = new XMLHttpRequest();
    // Setting parameters for request
    // "POST" - method
    // testAddress - variable with address
    // true - making request asynchronous
    testRequest.open("POST", testAddress, true);
    // Setting header with nonce for WordPress REST API authorization
    // WP REST API nonces are stored in JS global variable wpApiSettings.nonce
    testRequest.setRequestHeader("X-WP-Nonce", wpApiSettings.nonce);
    // Setting Content-Type to application/json
    testRequest.setRequestHeader("Content-Type", "application/json");
    // Sending request to server with JSON
    testRequest.send(jsonUserInput);

    After executing this request you can go to “Network” tab and see that there are two requests: first is the POST with 301 (redirect), second is the GET with 404 (not found).

    In the plugin’s server side code there isn’t any code that responds with 301 code and redirects, therefore it’s your server’s redirect misconfiguration. It’s even more likely after previously found issues with the lack of redirect to HTTPS on your website.

    If we will change our taget address from example code to alternate one with REST API root provided by WordPress itself on its pages with wpApiSettings.root + “watsonconv/v1/message” (variable testAddress in the code above), on the Network tab we would see that request goes to https://www.kinoa.tech/wp-json/watsonconv/v1/message and fails with 404 because of nonexistent REST route (explained futher) and doesn’t have any redirects. It means that you have improperly configured 301 redirect for one exact address: (/index.php?rest_route=/watsonconv/v1/message).

    Bot’s REST route may be be nonexistent in only two cases: ether chat widget is disabled or it is not called with POST method. Fact that plugin is disabled is proven further by absence of specific plugin related code in the source code of your pages.

    REST API definitely works because request to address https://www.kinoa.tech/?rest_route=/wp/v2/posts/ responds with the list of the posts on your site. Note that it doesn’t have any redirects.

    Properly reconfigured redirect should solve the problem. If not, we will gladly investigate this issue further.

    Github Gist with normal and alternate address request code

    • This reply was modified 6 years ago by kaneua.
    • This reply was modified 6 years ago by kaneua. Reason: Prettier formatting
    • This reply was modified 6 years ago by kaneua.
    kaneua

    (@kaneua)

    While Stackexchange may reject the question, IBM Developer Answers (https://developer.ibm.com/answers/index.html) shouldn’t. It’s relevant to their product and you need a solution. It’s more likely to find someone with the same issue on IBM’s site than there.

    You can also join IBM Watson Slack channel and ask your question there. (Link is on this page: https://www.ibm.com/cloud/watson-assistant/docs-resources/)

    kaneua

    (@kaneua)

    Hello. There are a few resources I can recommend:

    Q&A sites where hundreds of willing developers can answer your questions
    IBM Developer Answers: https://developer.ibm.com/answers/index.html
    Tag “watson-assistant” on Stack Overflow: https://stackoverflow.com/questions/tagged/watson-conversation

    If you aren’t confident in your skills or feel that you need to know some basic concepts, you can check out IBM’s “How to Build a Chatbot Without Coding” course on Coursera.
    https://www.coursera.org/learn/how-to-build-your-own-chatbot-without-coding

    At last, but not least, there are lots of docs on IBM’s website: https://www.ibm.com/cloud/watson-assistant/docs-resources/ From my experience, it’s always better to check them first before posting questions elsewhere. There’s also a link to the Slack channel where you can also ask bot development related questions.

    Regarding your current question, you can go to your skill’s dashboard, then in Improve > User Conversations you can edit mistakenly recognized intents.

    • This reply was modified 6 years ago by kaneua.
Viewing 8 replies - 1 through 8 (of 8 total)