Calendar resources not available on unpkg.com

Wappler General Need Help
1

Hi everyone
yesterday everything worked fine, but today I can no longer access resources to make the calendar work
https://unpkg.com/@fullcalendar/core/main.min.css,
https://unpkg.com/@fullcalendar/core/main.min.js,
etc …
I tried it from my browser and the result is this

Schermata 2020-06-22 alle 13.06.01
Schermata 2020-06-22 alle 13.06.011670×340 46 KB

Ver. Wappler 2.9.1
Do you have any suggestions, maybe it’s just a temporary suspension of the service …

Thank you

1 Like
2

Perhaps it’s to do with a new version of FullCalendar being released yesterday: https://fullcalendar.io/blog/2020/06/v5-official

3

Heck, this is quite serious. I’ve just checked a system I built using the calendar module and that’s stopped working, too. Can’t we store dependancies locally so this can’t happen?

4

Seems that they standard point the cdn to the latest version and that broke with the 5.0.0 release from yesterday. Here a fix. Edit all the urls from the fullcalendar to include a version number:

	<script src="https://unpkg.com/@fullcalendar/core/main.min.js"></script>
	<script src="https://unpkg.com/@fullcalendar/core/locales-all.min.js"></script>
	<script src="https://unpkg.com/@fullcalendar/interaction/main.min.js"></script>
	<script src="https://unpkg.com/@fullcalendar/daygrid/main.min.js"></script>

change them to:

	<script src="https://unpkg.com/@fullcalendar/core@4.4.0/main.min.js"></script>
	<script src="https://unpkg.com/@fullcalendar/core@4.4.0/locales-all.min.js"></script>
	<script src="https://unpkg.com/@fullcalendar/interaction@4.4.0/main.min.js"></script>
	<script src="https://unpkg.com/@fullcalendar/daygrid@4.4.0/main.min.js"></script>

You can have more includes depending on the modules being used.

2 Likes
5

Thanks @patrick. Will Wappler use version numbers in future to hopefully avoid this happening again?

6

Yes, we will. It wasn’t mentioned anywhere in their documentation that the cdn link uses the latest version and how to get a specific version, figured this out now. We will set the version to version 4.4.0, seems there are a lot of changes in 5.0.0 that will not work with our current implementation.

We will release an update of the calendar for 5.0.0 later, that version is not backwards compatible. A lot of options are renamed and the DOM structure and CSS also changed.

2 Likes
7

With so many changes, and no backwards compatibility, it’s crazy that their cdn link would return v5 scripts.

I had some css links, too, which were fixed by adding @4.4.0 so all is good again. Thanks for the speedy info.

8

Thanks for the info @patrick, I updated the new links, everything works :+1: