Hi Dan,

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

1. Setting the entire Editor to Read only Display ( and a side Note about LightBox effect):

Thank you for this suggestion.

At the moment, we don't have a built-in option to set the entire Editor Modal to 'read only', and we also do not have any built-in "LightBox" feature.

For our images to have a LightBox effect, we have to install a 3rd Party Plugin, such as, for example the WP Lightbox 2.

And this only works for our Image Columns, it does not work for Email content/if we were to do cells that contain something like "mailto" links, or Emails as text - for that it would need to be a String Column, thus we won't be able to use a LightBox for this type of data.

Also, the functionality for Lightbox on our Images can only be used only with non-editable tables, as we noted on this Documentation for Image columns;

or in other words "non-server-side tables";

You could try a workaround.

For example, you won't be able to use it for Manual Tables.

But you could make a new SQL table which pulls the same data,

and disable server-side processing in the Data Source settings of that table.

For Manual Tables, you can check under Editing tab,  what is their "MySQL Table name".

Then make a new SQL Table like this :  "SELECT * FROM Table_Name", 

and disable server-side processing, this way you could make the LightBox work.

-

If you need the main source data to be editable from our plugin,

for example, a use-case could be to use the main Manual Table for Administrators to edit in the back-end,

and for front-end to be able to open images in LightBox,  you could pull that data into the new SQL Table and disable server-side on it ( and add any other limitations, such as disabling editing on that second Table, etc).

Let me know if that makes sense, and if you have any questions.

-

If you wish to add Development Suggestions, you can do so, of course, we just can't promise an ETA on them.

You can suggest it to our developers, though - they will do their best to make a solution in the future.

Please feel free to search on our suggestions page, 

 to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there,  and as more people vote, the feature will move higher on the priority list.

You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.

-

If you have coding skills and wish to try to make a custom solution now,

you can check out our available hooks for Developers on this documentation and see if you can find any hook that might help.

Please be advised that custom solutions with hooks are not included in our support.

You can also research resources such as Stack Overflow to see if any other user perhaps found a workaround.

( We do like to give examples for certain solutions, but for this use-case, we, unfortunately, don't have anything yet)

New Feature Request #2:
Allow specific fields to be Read/Only Display (non editable):

This is also not available currently as built-in options.

At the moment, we can only use our Editor Roles, but that limits editing to the entire Table/all Columns;

So any Column that has a chosen Editor input Type, will be editable by selected user Roles;

it can not be set 'per each column', as you described.

But we already had a couple of other Users request something like that, so probably there might be already requests, but you can double-check and add your own if those users haven't written them up already on our Development Suggestions Page.

Thanks again for these suggestions, we truly take great value from them, and we will do our best to work on them as soon as possible.