Chatbot window not displaying anymore after update

In the browser console I see this error when the cache plugin is enabled and the JS gets combined and minified:

SyntaxError: "" string literal contains an unescaped line break

Not sure if it’s related, but this error msg doesn’t appear when the cache plugin is disabled and the chatbox appearing.

When excluding the following file path from the cache, it works again:

/wp-content/plugins/conversation-watson/app.js

So apparently something in the Javascript file has changed which made it not compatible for JS minifying.

Hello @nicoter.
To solve your problem we need extended information about your plugin installation and Watson Assistant credentials you are entering into plugin. To get the file with the extended information, follow these steps:

• Go to your WordPress Dahsboard (sample screenshot)
• Go to “Watson Assistant” > “Set Up Chatbot” in the left menu (sample screenshot)
• On the “Set Up Your Chatbot” page go to “Having Issues?” tab (sample screenshot)
• On the “Having Issues?” tab, download full log file with extended information by following the link (sample screenshot). Don’t publish it openly on sites like WordPress Forums as it may contain sensitive information.
• Send email with description of your issue and attached file to [email protected]

Please note that we need both extended information file and Watson Assistant credentials. Don’t post them on the forum, send them to [email protected] instead.

If you have more questions, don’t hesitate to ask them.

Mail including log sent.

Thank you, @nicoter.
We are looking into it.

Hello @nicoter.

Yes indeed, in the last update there were changes in the app.js. To solve this problem, please exclude the path to the app.js file from the cache. Then, if your caching plugin saves data about the excluded file, clean the data for the app.js file and try adding it again.

If you have more questions, don’t hesitate to ask them.

To solve this problem, please exclude the path to the app.js file from the cache.

I did this already like I mentioned in my 2nd reply to this thread and this solved the issue, although I’d prefer to have it minified and combined with the other JS files.

Then, if your caching plugin saves data about the excluded file, clean the data for the app.js file and try adding it again.

I’m not following you. I should exclude the file and then re-add it?

Anyway, I just tested it both ways after updating to the new release:
– Excluding from cache obviously workes anyway
– But it also worked when including it with the cache and minifying and combining it with the other JS files. Like it used to work before one of the recent updates broke it.

Thanks for fixing it!

@nicoter, you are welcome!