Closed robertraf closed 4 years ago
https://github.com/kaoz70/grapesjs-blocks-bootstrap4/blob/master/src/components.js#L213
InputGroupBlock(bm, c.labels)
And fix in grapesjs-my-plugin/grapesjs-blocks-bootstrap4/src/components/InputGroup.js
label.form_group_input
label.input_group
Seeing this issue as well. Happens if you simply git clone the repo and then try to bring up the index.html file in a browser. Bad bug
I got the same error, steps
any solution??
I would soooooooooooooo LOVE to use this plugin for a work project but thats impossible with this bug which happens every time. Does anybody have any idea how one would go about fixing this?
I would be happy to do the PR submission work if anyone knows what the fix is ...
I recommended not to use this project (plugin: too many bugs) however injecting the css and js file would help to use bootstrap4 plugin in grapejs library. After that we can make custom bootstrap template using Blockmanger.
example:
canvas: {
styles: [
'https://stackpath.bootstrapcdn.com/bootstrap/4.1.3/css/bootstrap.min.css'
],
scripts: [
'https://code.jquery.com/jquery-3.3.1.slim.min.js',
'https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.3/umd/popper.min.js',
'https://stackpath.bootstrapcdn.com/bootstrap/4.1.3/js/bootstrap.min.js'
],
I think an individual who has developed such a relatively good plugin, everyone can support and join hands to fix the error, then it is perfect. Sorry about my vocabulary!
https://github.com/kaoz70/grapesjs-blocks-bootstrap4/blob/master/src/components.js#L213
InputGroupBlock(bm, c.labels)
And fix in grapesjs-my-plugin/grapesjs-blocks-bootstrap4/src/components/InputGroup.js
label.form_group_input
label.input_group
Is this the fix? can you please elaborate on this.
Below version is working
https://github.com/kaoz70/grapesjs-blocks-bootstrap4/tree/e2f8fc46bdc053a016a335e53a1beaba8c4f6d85
Hello, sorry for the late reply, yes I know this is kind of buggy, if anyone could help make this project better that would be great! Any good PRs are welcome.
That aside, I am using this on some production sites so this error is weird, I haven't seen this, It may be some GitHub security automatic NPM package upgrades that caused this, let me take a look.
Ok, can you please check if version 0.1.21 fixes this issue?
Just tested with 0.1.22 and the issue does indeed seem to be fixed for me.
Great to hear that! I will close the issue then.