Uncaught TypeError: i.type is not a function when using the Slick Media field formatter

Working on it.

Further testing: It has nothing todo with the field formatter. The same JS error appears when using slick_views.

I have the feeling this is about jQuery.

The original line throwing the error is:

$.type is not a function

https://api.jquery.com/jQuery.type/ => deprecated since jQuery 3.3, Drupal 11 core/jquery is on jQuery 4.0.

Allright, here we go: https://github.com/kenwheeler/slick/issues/4316

So the Slick library is incompatible with Drupal 11 / core/jquery (4.x).

Feel free to use our fork to have a quickfix: https://github.com/JPustkuchen/slick

But yeah, this is kind of unfixable for this module without a forked Slick version? There was Google dev active in the official Slick repo and merged some MR, but no idea if this will be fixed anytime soon.

@thomas.frobieter should I open a MR making the required changes?

As I said in #9, I don't think the Slick module can do anything about this, because it's a Slick library problem.

The maintainers will have to decide how to proceed.

There was a similar issue. Try searching your title keywords in the search box for details.

Slick as a module and Slick as library are two separate entities with different authorities, authorship, responsibilities, lingos, maintainerships, etc. I have said this many times.

I as the module author cannot acclaim to be responsible for the library's issues. That would add me unnecessary and irrelevant burderns.

Given a few possibilities, local patch, github forks, hardcodes, not to mention different version preferences and time constraints, I refrain myself from touching the library. However your and other people's contributions with relevant solutions are very much appreciated. Anything that works well with your workflow is acceptable and just great, go ahead.

Postponed to avoid more dups, not to do anything about this.

Thank you.

Sure, that's completely understandable. But it should be made very clear on the module page that this problem exists in Drupal 11, otherwise every new user might spend hours looking for a solution.

A note and possibly a link to this issue is sufficient in my opinion. Users can then decide for themselves if they want to use our Slick fork or create their own.

Maybe just add another point in the "Broken vs. working library versions." Box?

"All versions: Incompatible for Drupal 11+ (using jQuery >= 4.x). You need to use a modified version of the Slick library, see 🐛 Uncaught TypeError: i.type is not a function when using the Slick Media field formatter Active for details."

Good suggestion, thank you!

I proceeded with the 3.0.4 update on my personal website without being aware of this issue. A view using the carousel display mode became unavailable / invisible from the Views admin page. I don't remember exactly at what stage though. Anybody else had this problem?

Now, my question is: what happens if I manually install the 1.6.0 library and run further updates of the Slick module via composer? Will the library be updated to the broken 1.8.x version?

I need a clear how-to before upgrading a Drupal farm to D11. Losing views on 25 sites is out of the question. Thanks!

Slick 2.x and 3.x are exactly the same, 99.9999%. I made it so to avoid upgrade issues.

Only Blazy has removed depreciations, with minor services changes and JS improvements specific to BigPipe.

The issue here is Drupal 11, not Slick per se. And the solutions are here and there. Try using search box.

The reason dont use Drupal11 now. I didnt find any slider for it))