Not able to use removeRowPlugin on version 1.11.0

Tags: #<Tag:0x00007efc6570f270>
#1

After updating to version 1.11.0 from 1.10.2, I am not able to use removeRowPlugin

#2

Hi @ankushgoel

According to docs in 1.11.0 between a few other breaking changes:

The /plugins directory was deleted (with the “removeRow plugin” included)

src: https://docs.handsontable.com/pro/1.11.0/tutorial-release-notes.html

Although if you include the following code back to your resources it should work

#3

Hey, even after adding removerow js and css, the plugin did not work

#4

Can you share any demo?

It will be also helpful if you could check if you are getting any console errors?

#5

Here is the console error

Uncaught TypeError: Handsontable.eventManager is not a function at new removeRow (remove-row.js:10) at remove-row.js:138 at remove-row.js:152

#6

It’s my bad! I have forgotten that we have changed the way you get to the Handsontable object structure.

At the link that I have sent you before is also a note that

Handsontable.eventManager

has been changed to Handsontable.EventManager.

You should also check the Handsontable.Dom > Handsontable.dom

#7

Now it throws this error
handsontable-pro.js:2014 Uncaught TypeError: Cannot call a class as a function at _classCallCheck (handsontable-pro.js:2014:99) at Function.EventManager (handsontable-pro.js:2038:5) at new removeRow (handsontable/remove-row.js:10:37) at handsontable/remove-row.js:138:21 at handsontable/remove-row.js:152:3

#8

I think that I would need you to create a demo where this issue could be replicable. Could you send it please?

#9

ok i am trying to create a demo.

#10

Demo - http://jsfiddle.net/nhgbgx1k/

After removing all console errors, plugin is still not initalized
Demo - http://jsfiddle.net/nhgbgx1k/1/

#11

Thank you.

Please check this demo http://jsfiddle.net/pav7xm46/ it uses the latest Handsontable PRO 1.10.0 with removeRow plugin resources from 0.31.2

I have taken your data and hiddenRows settings. Let me know if it works for your project as well.

#12

@aleksandra_budnik Thanks for your help, It’s working fine now.

#13

Great, I am happy to hear that.

Thank you for an update. I guess that we can close the issue now.

#14