Your comments
Eric -
I think we have a workaround solution for you.
Use the "No JS" Embed code, as previously suggested, but add to your page the first portion of your JS embed code (the embed functions).
Then you would have access to the API.
Just need to add this at the top of the page - (where xxxxxx is your account id)
I think we have a workaround solution for you.
Use the "No JS" Embed code, as previously suggested, but add to your page the first portion of your JS embed code (the embed functions).
Then you would have access to the API.
Just need to add this at the top of the page - (where xxxxxx is your account id)
Eric -
You are right in that the "No JS" embed code does not support API calls. Let me take another look at what if anything we can do.
Regards
Gil
You are right in that the "No JS" embed code does not support API calls. Let me take another look at what if anything we can do.
Regards
Gil
Darin -
Each TTS text is limited to 900 characters - but you can create as many audios as you like and play them in sequence if you need a longer text.
No the audio cannot be downloaded.
It can only be spoken online by your SitePal character.
awesome profile image
Gil
Each TTS text is limited to 900 characters - but you can create as many audios as you like and play them in sequence if you need a longer text.
No the audio cannot be downloaded.
It can only be spoken online by your SitePal character.
awesome profile image
Gil
Eric -
We believe a workable solution would be to use ‘Web Page (No JavaScript)’ embed code - and then you can display the Scene when you need to.
Trying to call our JS embed function in the manner you do creates a conflict as it was not intended to be used that way.
Let me know how goes.
Best
Gil
We believe a workable solution would be to use ‘Web Page (No JavaScript)’ embed code - and then you can display the Scene when you need to.
Trying to call our JS embed function in the manner you do creates a conflict as it was not intended to be used that way.
Let me know how goes.
Best
Gil
OK - we received your example and we see the issue.
We're looking at it and will advise asap.
Gil
We're looking at it and will advise asap.
Gil
Glad to be able to assist. The problem in the last round was that although the developers applied the solution for Studio accounts, they did not retroactively apply it to all existing shows. That was an oversight, now corrected.
Sorry this took so long to clear up - & thanks for your patience.
Gil
Sorry this took so long to clear up - & thanks for your patience.
Gil
Doug -
Which browser was used? Was the demo done on your computer (i.e. laptop you brought with you) or on the host company computer?
I'm thinking possibly restrictive browser settings.
Also - was the page loaded in http or https?
LMK
Gil
Which browser was used? Was the demo done on your computer (i.e. laptop you brought with you) or on the host company computer?
I'm thinking possibly restrictive browser settings.
Also - was the page loaded in http or https?
LMK
Gil
Thanks Ellen
This should now be fixed.
Please review and let me know.
Regards
Gil
This should now be fixed.
Please review and let me know.
Regards
Gil
Eric -
We will (obviously) need to investigate further.
Do you mind using your IE10 browser to go to - http://supportdetails.com/ & send the report to support@sitepal.com
Thanx,
Gil
We will (obviously) need to investigate further.
Do you mind using your IE10 browser to go to - http://supportdetails.com/ & send the report to support@sitepal.com
Thanx,
Gil
Customer support service by UserEcho
As far as the Wizard instructions are concerned - they refer to folks using the embed code as provided - and as such are literally correct. What we did here is a "mix and match" - not our standard fare.
Anyway - very glad it worked.