Issue #836💬 AnsweredOpened February 5, 2018by kickbk1 reactions

Intercept and prevent an asset from being removed

快速解答by kickbk1

Missed it in the docs.

Read full answer below ↓

Question

How would you go about intercepting and preventing an asset from being removed? I suspect the image may already have been removed by the time we run "asset:remove". If so how do we tap into the actions and ask for confirmation? The reason I ask is because I want to tie a deletion in GJS to permanent deletion of images from client accounts.

editor.on('asset:remove', () => {
  if (!window.confirm("Are you sure?")) {
    // HERE I WOULD LIKE TO BREAK THE REMOVE ACTION.
    ...

Answers (2)

kickbkFebruary 5, 2018

Missed it in the docs.

lock[bot]September 18, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

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.