Moving stable tag to new revision

If you have been using Ziggeo for a while you are aware of our revisions, latest and stable tag. If you are new, you might not be familiar, and this will help you with the same.

First if you are not familiar with our revisions you should head over to this post: Am I using a stable revision? It goes into details about all revisions so that you can learn more about them.

Now let us talk about the switch that we will make.

In a weeks time – on 1st of February 2022, we will be moving our stable tag to point to r39. Currently it is pointing to r36.

We believe that the week time will be enough for you to see if there are any things due to which you might prefer to stay on r36 for a bit more time.

If the r39 works fine for you, then all you would need is to leave it on stable as is, and starting 1st of February you will be using the r39 automatically.

  • We actually recommend using our stable tag, because we update it over time to the next best revision for you to use. That way your website is never left out of date and all security and feature updates are available.

How to try r39?

Our revisions are easily changed by changing the URL. There are different ways you would change this depending if you are using some integration such as WordPress, or if you are adding our service directly.

In all cases, there is a code on your website (usually in header), that looks something like so:

<link rel="stylesheet" href="https://assets.ziggeo.com/v2-stable/ziggeo.css" />
<script src="https://assets.ziggeo.com/v2-stable/ziggeo.js"></script>
<script>
	var ziggeoApp = new ZiggeoApi.V2.Application({
		token:"APPLICATION_TOKEN",
		webrtc_streaming_if_necessary: true,
		webrtc_on_mobile: true
	});
</script>

To test r39 you would change it to this instead:

<link rel="stylesheet" href="https://assets.ziggeo.com/v2-r39/ziggeo.css" />
<script src="https://assets.ziggeo.com/v2-r39/ziggeo.js"></script>
<script>
	var ziggeoApp = new ZiggeoApi.V2.Application({
		token:"APPLICATION_TOKEN",
		webrtc_streaming_if_necessary: true,
		webrtc_on_mobile: true
	});
</script>

Again, we recommend leaving your website on “v2-stable” instead of using specific revision. For test purposes however you can always switch to something more specific.

How to stay with r36 (current stable)?

Your developers working on integration with Ziggeo might be on a leave. Maybe your Product Manager took few days off. Your team might already be working on something that takes a lot of time. There really are many reasons why you might want to stay with r36 and not switch right away.

We hear you! If you want, you would just replace the “v2-stable” into “v2-r36” just like we changed it to r39 above. As you do, you will stay on the very same scripts and styles you are using now.

While not recommended, it is possible, just remember to switch back as soon as you are able to the stable revision.

What is new in r39?

r39 has a lot of different changes added to it. First and biggest change is the introduction of our audio system.

You can now easily (if not already) use our audio recorder and player just as you have been using video recorder and player already for years.

There are also many improvements such as faster and sturdier uploads.

Next to these there are other things we have improved upon such as embedding resizing engine and added many new parameters that you can use.

Most of these features are automatically enabled for you, allowing the best experience. For the added parameters you can see more about them on our parameters page. The new parameters are:

  1. aspectratio
  2. maxheight
  3. maxwidth
  4. minheight
  5. minwidth
  6. posterfitstrategy
  7. sticky
  8. videofitstrategy

Have questions?

Having questions is awesome. Having thoughts about our changes is great as well. This is why we have introduced our https://feedback.ziggeo.com/ page to which we invite you to go and check out.

To reach out to us, you can always use our support email at support@ziggeo.com.

PREV NEXT