-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to add new columns after 11th column created using Version: 1.1.3 #31
Comments
Just working with this again. Regardless of what we do, we are unable to build a table greater than 12 columns. To recreate, just try to add new columns to a new table - click add column 11X to replicate. At the 12th column, you are unable to add any more columns. |
I'm bumping up against this issue today. As per a prior conversation... @abjerner noticed the limitation and wasn't sure why it was in place, which leads me to believe it could be removed without any ill effects. |
Hey Heather! Yeah I did a PR fix for this. Just waiting on it's integration and release as well! Cheers. |
Sorry for the lack of action. I'm caught up in too many different things, so even small issues like this end up not being fixed/merged for waaaay too long. I'll try to find some time looking into this soon 😉 |
Awesome thanks. Heather - for Sprott lol... |
Thank you! |
Very strange an intermittent issue with Version: 1.1.3 on Umbraco 11 that we have discovered with tables greater than 11 cells when the Limbo tables are used in the block grid. I can't confirm if this happens when not in the block grid, but I would image this issue exists there as well. Under certain scenarios, we are unable to add additional columns or delete rows when these conditions exist. No errors outputted to console.
To replicate:
Even if you add a value to your 12th cell, you can't add additional values. Also the delete row function does not work during this scenario.
You can bump the table to make it start working again by deleting a column, but then you lose the data in that entire column across the board, so it's not a viable workaround.
The text was updated successfully, but these errors were encountered: