I don't have anything available right away, because it's hosted on a private server. You can recreate the problem in the sandbox by creating a new table with one row. In our case, we're filtering the rows specific to each user. If the table is blank, and a user clicks the blank row, the edit and delete buttons become available, which in turn throws errors.
I have created a new table that is Front-end editable and where Users see and edit only their data is enabled. I have created one row with administrator and then logout and logged-in with with another user that see No data available in table if I click on that row and click New button everything works fine for me. Maybe I didn't set it up as you said? What kind of error do you have? Can you send me a screenshot of that error?
I believe the only difference was that we did not set Users see and edit their own data. Also, the new button works fine, but the edit and delete button become active, which is the problem.
The edit and delete buttons break when you select the empty row. They start greyed out, but become active when a user selects the empty row. That is the way how these buttons works. When row is not selected then these buttons are grey but when user select any row then they are active.
What you described is the issue. Smh. If it's an empty row, you shouldn't be able to select it in the first place. A user shouldn't be able to edit or delete an empty row.
If the table is empty and user select Edit button it will be also as he clicked New. I think that this issue is not so big and crucial so that tables are not working, but we'll add this task for one of the future updates. We'll have also a lot of new features in version 2.0 that is currently in development stage.
When table is empty, and user clicks on row with text "no data available in table" user can then click edit/delete resulting in errors.
Hi Stephen,
Thank you for the purchase.
Can you please send me a link of the table where this issue is happening so I can take a look?
I don't have anything available right away, because it's hosted on a private server. You can recreate the problem in the sandbox by creating a new table with one row. In our case, we're filtering the rows specific to each user. If the table is blank, and a user clicks the blank row, the edit and delete buttons become available, which in turn throws errors.
Hi Stephen,
I have created a new table that is Front-end editable and where Users see and edit only their data is enabled. I have created one row with administrator and then logout and logged-in with with another user that see No data available in table if I click on that row and click New button everything works fine for me. Maybe I didn't set it up as you said? What kind of error do you have? Can you send me a screenshot of that error?
I believe the only difference was that we did not set Users see and edit their own data. Also, the new button works fine, but the edit and delete button become active, which is the problem.
I'll have a screenshot later today.
Hi Stephen,
So you just created editable table with Front-end editable option enabled that has no rows and when you click on row and click New it is not working?
"The edit and delete button become active, which is the problem."
You mean there shouldn't be Edit and Delete button if the table is empty?
The new button works just fine.
The edit and delete buttons break when you select the empty row. They start greyed out, but become active when a user selects the empty row.
Hi Stephen,
The edit and delete buttons break when you select the empty row. They start greyed out, but become active when a user selects the empty row.
That is the way how these buttons works. When row is not selected then these buttons are grey but when user select any row then they are active.
What you described is the issue. Smh. If it's an empty row, you shouldn't be able to select it in the first place. A user shouldn't be able to edit or delete an empty row.
Hi Stephen,
If the table is empty and user select Edit button it will be also as he clicked New. I think that this issue is not so big and crucial so that tables are not working, but we'll add this task for one of the future updates. We'll have also a lot of new features in version 2.0 that is currently in development stage.