Yes, it is the same. I never bother changing the look and feel, so I quickly tried out the other templates. Something that may get you closer to the problem: I tried it on a new database that only had two tables, and it worked fine. Could it possibly become an issue at the point when the tablelist view says "There are too many objects to display. Find objects matching:"
Last edit: Ilia 2020-01-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there perhaps something about the name or number of tables selected that triggers this? Like table names with special characters or capital letters?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Now you're onto something, I think. Added a table to the test database I mentioned earlier which has a name starting with a capital letter letter, it fails on that one. Is it possible that in some of the commands the database, role or table names are not enclosed in in quotes?
Last edit: Ilia 2020-01-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Great, thank you. Just off the top of your head, there's another issue, also long-standing, where data cannot be edited in tables. The message is that the data cannot be altered because there is no primary key on the table. Should I raise a seperate ticket, or could this have also fixed that?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I expect you have the same issue when using Gray Theme?
Yes, it is the same. I never bother changing the look and feel, so I quickly tried out the other templates. Something that may get you closer to the problem: I tried it on a new database that only had two tables, and it worked fine. Could it possibly become an issue at the point when the tablelist view says "There are too many objects to display. Find objects matching:"
Last edit: Ilia 2020-01-04
Is there perhaps something about the name or number of tables selected that triggers this? Like table names with special characters or capital letters?
Now you're onto something, I think. Added a table to the test database I mentioned earlier which has a name starting with a capital letter letter, it fails on that one. Is it possible that in some of the commands the database, role or table names are not enclosed in in quotes?
Last edit: Ilia 2020-01-04
Yep, that's the cause - we'll fix this in the next Webmin release.
Great, thank you. Just off the top of your head, there's another issue, also long-standing, where data cannot be edited in tables. The message is that the data cannot be altered because there is no primary key on the table. Should I raise a seperate ticket, or could this have also fixed that?
That one is expected - if a table doesn't have a key, webmin has no way to select a unique row to edit in the GUI.