Dean N
My feedback
26 results found
-
4 votesDean N
supported this idea
·
-
6 votesDean N
supported this idea
·
-
7 votesDean N
supported this idea
·
-
8 votesDean N
supported this idea
·
-
4 votesDean N
supported this idea
·
-
2 votesDean N
supported this idea
·
-
2 votesDean N
supported this idea
·
-
3 votesDean N
supported this idea
·
-
16 votesDean N
supported this idea
·
-
28 votesDean N
supported this idea
·
-
81 votes
This feature request is added to backlog and will consider it in future updates.
Dean N
supported this idea
·
-
2 votesDean N
supported this idea
·
-
2 votes
An error occurred while saving the comment Dean N
supported this idea
·
-
4 votesDean N
supported this idea
·
-
2 votesDean N
supported this idea
·
-
2 votesDean N
supported this idea
·
An error occurred while saving the comment Dean N
commented
Posting this in case anyone else has trouble with this. The best way to troubleshoot this bug is to load the lesson's preview, then in your browser open the developer tools pane (F12 in chrome) and look at the console error messages. If you see an error that says something like "Uncaught SyntaxError: Expected ',' or '}' after property value in JSON at position 7175 (line 1 column 7176)" then you know one of the json files (likely a theme file) has something wrong with it.
In my case, I discovered that when building your custom themes, sometimes Captivate will enter the font's Family name with backslashed escaped characters, e.g. "fontFamily":"\"Open Sans"\". This will cause an error in the browser and the preview will not load.
The way I fixed it was I clicked the fonts dropdown menu at the top of the theme screen and selected "Delete Font" for all the ones I could. Then I re-added the font, deleted the first font I couldn't delete before, re-added it. And then I applied and exported the theme.
You could technically try to edit the theme.json file directly by changing the .cpth file to .zip but there's no guarantee changing it back to .cpth will not cause other errors.
-
5 votesDean N
supported this idea
·
-
5 votesDean N
supported this idea
·
-
1 voteDean N
shared this idea
·
-
32 votesDean N
supported this idea
·
This bug still persists in v13. And I just want to add for the Captivate devs that this is not at all uncommon and having such a seemingly innocuous action cause a complete crash is unacceptable, as that could meaning losing hours of work. If we need to save a duplicate cpt file and want to rename an existing one to help organize our docs, we would need to close the dialog, go into file explorer to rename the existing file, then bring Captivate back up and restart the saving process. This can really mess with our workflow because it's not intuitive. Either lock the functionality or fix it.
Anything this basic that causes such a huge failure needs to be prioritized.