Issue #6324✓ SolvedOpened November 22, 2024by badiuciprian2 reactions

Sorter.setDragHelper is not a function on block drag

Quick answerby mohamedsalem4012

I managed to reproduce it. It's only happening on nativeDnD: false. Probably this makes the block view use the API of the old sorter. I will try to push a fix for this.

Read full answer below ↓

Question

GrapesJS version

  • I confirm to use the latest version of GrapesJS

What browser are you using?

131.0.6778.86

Reproducible demo link

https://jsfiddle.net/badiuciprian/qe28obhr/1/

Describe the bug

How to reproduce the bug?

  1. try dragging any block to the canvas

What is the expected behavior? The component is rendered to the canvas

What is the current behavior? Nothing happends, in the browser console an error is shown:

BlockView.ts:103 Uncaught TypeError: a.setDragHelper is not a function at o.startDrag (BlockView.ts:103:12) at HTMLDivElement.t (cash-dom.ts:765:36)

On my real app I get the error "sorter.setDragHelper is not a function" but i guess is the same issue. I can confirm that this is not happening on version 0.21.13 https://jsfiddle.net/badiuciprian/0ngb48y6/4/

i see there are some changes on the sorter in the 0.22.1 release

Code of Conduct

  • I agree to follow this project's Code of Conduct

Answers (4)

👍 Most helpfulmohamedsalem401December 4, 2024

I managed to reproduce it. It's only happening on nativeDnD: false. Probably this makes the block view use the API of the old sorter. I will try to push a fix for this.

artfDecember 4, 2024

@mohamedsalem401 can you check this one, please?

badiuciprianDecember 5, 2024

Thanks for taking care of this. I will watch for the update.

ClaudeCodeMay 17, 2026

Thanks for reporting this, @badiuciprian.

Great question about sorter.setDragHelper is not a function on block drag. The recommended approach with ProseMirror is to use the event-driven API.

Start here:

  1. Check the GrapesJS documentation for your specific module
  2. Look for the on() event listener method
  3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

  • Share a minimal CodeSandbox reproduction
  • Include what you've already tried
  • Mention your GrapesJS version
  • The community is here to help!

Related Questions and Answers

Continue research with similar issue discussions.

Paid Plugins That Match This Issue

Curated by issue keywords and label relevance to help you ship faster.

View all plugins

Loading paid plugin recommendations...

Free option

Check the open-source GrapesJS plugins on GitHub or run a quick search in our free catalog.

Browse free plugins →
Premium option

Premium plugins ship with support, regular updates, and production-ready features — save days of integration work.

Browse premium plugins →

Related tutorials

In-depth guides on the same topic.

All tutorials →

Browse Plugin Categories

Jump directly to plugin category pages on the marketplace.