Our expert settings are designed to offer high level setup. It is something you would usually not use nor change.

The suggestion we have is to leave them on default unless you either know exactly what will happen, or you were instructed to do the same by someone in our support.

We know how much it means having some information shown during development yet not available within production. This is why we have added development mode.

Simply changing this on and off will make our script output all of the console entries that were register. When turned off, it will keep them for itself.

We had and still support having file used for the templates storage. For large amount of templates, complex websites with a lot of options loaded on start and alike the file approach would offer speed with reads and writes compared to database.

Having that said some hosts or setups make it difficult to safely work with files. For that reason we have decided to offer you the files option if you know how to set it all up securely.

If you already have the files and want to switch to the very common database option instead, that is also possible.

Just use the sync option and there you go, quick way to have both database and files synced up.

All you would do is set the location where the templates should be saved.

Have you been testing a lot of different setups and how will things work? Have a huge number of templates in your list and prefer not to delete them one by one?

Sure, just use the clear the templates option and have them all cleared up.

Note: Some versions of our core WordPress plugin (2.0, 2.1 and 2.2) had a strange issue where template ID would be saved as empty and otherwise would not be possible to remove. This would sort them out.

There are few different WebRTC settings that you can change. The defaults are made to have WebRTC (preferred) used on as many decides as possible.

WebRTC for mobile is option that allows you to have WebRTC used on mobile devices that support it.

The WebRTC streaming would affect your recording quality based on your network speed, however it is the only variant of WebRTC that is available in some browsers (Safari).

Now the WebRTC Streaming when needed is going to be smart and use the streaming implementation if no other WebRTC implementation is available. That way you avoid the use of the native camera app. This is recommended and needed for Safari due to Safari's implementation of WebRTC.

There are few more interesting fields that you might want to play around at times under the Expert Settings.

Set version field allows you to choose between v1 and v2. We recommend using v2 only, however this option was added while the v1 was available and the goal is to help with transition.

Set revision field is similar to version however allows you to pick between any of our revisions. Please add in following format "rXY". So if you wish to use revision 40 you would set it as r40. Alternatively use word "stable" to load the revision we mark with stable tag (default) or "latest" to use the very latest codes. There is also lazyload approach field. When it is active it will allow you to have our scripts and codes added to the page when the embedding is present. In other cases it will stop our system from doing so. This is great if you wish to set the codes to only load when they are needed.

Older templates version support field is a way for you to specify if you are going to use the latest version of templates or if you want to use the older ones as well. If you are new, you will receive benefit of setting this to NO. If you have older templates then you might prefer having this option turned ON so that older types of templates are parsed as well.

The defaults are designed to offer you and your customers the best experience. As such you do not really need to make any edits or changes to these, unless you want to for some reason.

If you are not sure what they would do or if you should use them, reach out and we would be happy to help.