Tihomir Dmitrovi?

Thank you for providing more details. It appears that the issue is related to the MySQL settings. Our plugin utilizes table keys that are VARCHAR(255), and it fails to create such tables due to these settings.

This situation is somewhat unusual and is typically associated with older MySQL versions that have lower default settings for key lengths. You can find more information on this topic here: https://www.baeldung.com/mysql-fix-key-length-error.

At this moment, we do not plan to change the database definition to use shorter key lengths since it could impact existing installations. Altering the charset for these fields might be a solution, but I cannot guarantee if or when this will be implemented.

However, I will certainly work on improving the detection and reporting of such issues.

I apologize for any inconvenience this may cause. Currently, the only solution is to consult your hosting provider’s support team regarding the possibility of adjusting the MySQL settings or consider trying another hosting service.

Just tried it with fresh installation on PHP 8.0 and it was working well, so we can cross that one.

We’ll have to wait to see detailed error in the debug.log.

Hi Rivello,

Thanks for trying Convoworks!

These kind of issues are usually related to the server environment, but let we see. Can you please share some additional information so I can try to reproduce it:

• what version of PHP do you have?
• is it running on Apache or Nginx?
• when you open New Service view, does it have listed template services?

Additionally, if you have proper access to it, can you please try to turn on WordPress debug settings on and see if there will be more error details in debug.log

Tihomir

Hi,

We just published a new Convoworks WP version. It has improved search, can scan nested folders and is sorting files by filename.

We also updated the File Player skill template, but everything should work even with an old template.

Cheers

Yes, it seemed to easy.
Thing is that we are not sorting files at all. We are just using the order filesystem returns to us, which on Windows works just as expected, sorted by filename.
I reported the issue in our tracker too, it should not be an issue to fix it, I’ll try to push it for the next release (in 2 weeks max).

Well, according to computers, 12 is before 2 ??
If you open that folder in explorer, you’ll see the same issue.
You have to name your files with leading 0. 01, 02, …

Hi Luca,
Thanks! I’m glad you like it.

Right now it supports only one folder level. We might change it in one of the next versions.
How does it search? It tries to match the search phrase first with the folder name and if it is a match, the whole folder goes in the playlist. Otherwise it tries to match each song from the folder. If there is an ID3 tag in it, it will use its data, otherwise it tries to match filename.

But, I just tested it and found two issues: First is with our matching function which currently does not account filename if it has ID3 and the second is related to ALexa which in some cases gives us search value something like this: “My Playground” by The Chikitas.

Until we release fix for it, here is the quickfix you can apply in convoworks-wp/vendor/zef-dev/convoworks-pckg-filesystem/src/Convo/Pckg/Filesystem/FilesystemMediaContext.php
Just open that file and replace _readFolderSongs() method with this one:

private function _readFolderSongs($root, DirectoryIterator $folder, $baseUrl, $artwork, $background, $search = null, $minMatchPercentage = self::MIN_MATCH_PERCENT)
    {
       if (preg_match('/"([^"]+)"/', $search, $m)) {
            $search = $m[1];
        }
		
        $songs = [];
        foreach (new DirectoryIterator($folder->getRealPath()) as $folder_file) {
            if ($folder_file->isDot() || !$folder_file->isFile()) {
                continue;
            }
            if (\strtolower($folder_file->getExtension()) !== 'mp3') {
                continue;
            }
            if ($root) {
                $file_url = $baseUrl . '/' . \rawurlencode($folder_file->getFilename());
            } else {
                $file_url = $baseUrl . '/' . \rawurlencode($folder->getFilename()) . '/' . \rawurlencode($folder_file->getFilename());
            }
            $song = new Mp3Id3File($folder_file->getRealPath(), $file_url, $artwork, $background);
            if ($search) {
                if ( $this->_acceptsSong( $song, $search, $minMatchPercentage)) {
                    $songs[]  =   $song;
                } else if ( stripos( $folder_file->getBasename(), $search) !== false) {
                    $songs[] = $song;
                }
            } else {
                $songs[] = $song;
            }
        }
        return $songs;
    }

About that search issue on your current version, can you please check in the ASK console, test view. That test view can not reproduce the audio player, but you can see the request on the right side. It should be “PlayTrackIntent” for an utterance like “ask file player to play Madonna”.

How to set it up for non English languages:

For this you have to configure Alexa in manual mode https://convoworks.com/docs/publishers/platforms-configuration/amazon-alexa/
In that mode, all intents and utterances are defined and maintained in the ASK console. You even have to paste the url to your Convoworks service webhook there. That way you can set it up with IT language, while having EN in Convoworks.

1. Create file player service in Convoworks
2. Create Alexa skill, with enabled audio player interface.
3. Connect your Convoworks service with Alexa in the manual mode.
4. Go to Releases view in your Convoworks and copy endpoint url of your development version (button on the right)
5. Paste that url to ASK. Now is a good point to check will it trigger a webhook in the Convoworks.
6. In Convoworks, Import/Export view, download Amazon Alexa export. This is JSON, containing all required utterances. It should be quite easy to translate it directly here.
7. Paste that JSON in the ASK console, Interaction / JSON Editor.

Basically that should be that.

Strange.
Several things come to my mind.

– what OS/browser do you use? We have a known issue with Safari on Mac
– have you connected your installation with your Alexa developer account like described in https://convoworks.com/docs/publishers/platforms-configuration/amazon-alexa/
– were you able previously to create skills on Alexa? Are they still working OK?
– can you create new service from a template (e.g. Quote of the day) and publish it to Alexa?

No, unfortunately currently just English is supported.
We might have that feature in several months (we already had such inquiries) and we would appreciate your help with it.

If you are inpatient, there is a workaround for it. It uses “manual mode” in Amazon Alexa configuration, meaning that Convoworks will not propagate any changes to the ASK console. Alexa skill in the ASK console has to be manually created and configured. There are a couple of more hints about it and if you are interested to try I can elaborate.

Having mp3s on a separate disk should not be a problem. You just have to map that folder to be accessible through Apache. In “Filesystem mp3 source” context, use “MP3 folder path” to set a physical path from which Convoworks can read files. “Base URL” should point to the same folder, but through Apache.

Great to hear that!

Please be free to reach for help if you have any other issues or questions with usage! You can ask here or below any article on our website.
Happy Alexa development!

This is strange.
Can you please send me the following
– turn on log file and check in log file are there any error messages
– when it lands on not found, please send me the url
– please send me couple of lines, or screenshot from the modal on create service view

Alternatively, you can schedule a call with me and we can check it using the share screen – https://calendly.com/convoworks/convoworks-demo

Btw. Permalinks fix is only for InstaWP. I talked to the founder today and he said that they will fix that issue in a couple of days.

• This reply was modified 2 years ago by Tihomir Dmitrovi?.

Glad to help! Besides that, it seems that we are in the same time zone ??

We never encountered issues with regular installations, but the good part is that it is easier to troubleshot.
Please check what PHP version you have on your server and you can try to enable log file like described in https://convoworks.com/using-the-convoworks-log-files/

Hi,
Thanks for reaching out. 

Let us check the easier issues first.
* "no permission" after activation - known issue, it will be fixed, but reload solves it.
* There is known issue when using with InstaWP - you have to set "Settings/Permalinks" to "Post name". Not sure why is that, InstaWP founder told me that and after that it was working alright - https://convoworks.com/create-your-first-amazon-alexa-skill-using-convoworks-wordpress-plugin-and-instawp-no-server-no-registration-required/

For other reported issues, were you using localhost installation or on a publicly accessible server?

As I can’t find an error among the usual suspects, I’ll ask on Google forum.
Thanks for your response anyway!