When I use the front-end popup edit window, the only fields in the window are the ones being edited.

Is there any way to include some or all of the non-edit fields from the table row in the popup window?

As far as I know, the only fields which appear in the popup window are the fields being edited.

However, sometimes it would help to display other fields in the popup to clarify which record is being edited.

For example, let's say you have a table containing names and associated dates, and each record is identified by the name (which is set to edit 'None' because it is display-only in the table). If you are editing each record using the popup, you only see the date field because it can be edited. After you save your changes, if you click on the 'next' button, you cannot easily identify which record is now being edited because the name value is not displayed.

Bogdan:

Just to clarify, I am not requesting any new buttons for the popup.

I need to know if it is possible to include data fields in the popup which are display-only, i.e. cannot be changed.

Would it make sense for me to define some additional fields as 'edit' so that they will appear in the popup, and then use CSS to set them to display-only?

I developed a simple workaround.

That is, there were two fields that I wanted to show on the popup as display-only. I set each of the two extra fields to 'edit' so that they would appear on the popup. Then I went to the wpDataTables Settings to add some basic jQuery to the top of each page, and this code is executed when the page loads. The jQuery code disables each of the two new fields so that they are visible but not editable. This seems to work for now.

A better solution will be to set up an appropriate WordPress page template that will be used to contain the wpDataTable shortcode(s). This template will define jQuery code that is specific to the template requirements. Once this is implemented, I will remove the jQuery code from the general Settings so that it will no longer appear on every page using wpDataTables.

Bogdan:

I spoke too soon. There is a problem with my workaround if I use fields that are not in the record format of the primary input file. This happens if the wpDataTable record format is based on a primary input file joined to one or more secondary files.

That is, when I save the updated information from the popup, I receive an error that some of the fields cannot be updated. This is probably because the SQL UPDATE command is constructed using the fields from the popup, regardless of whether each field is editable or display-only.

The new workaround is to use jQuery to add one or more display ("<div>") elements to the structure of the popup dialog box when the page loads, and then to update the values of those elements based on the corresponding cell values from the wpDataTable row being edited. The creation of the new elements is working fine. However, I am having a problem with getting jQuery to listen for the dialog box opening so that the new element values can be updated.

Bogdan:

Using jQuery, I was able to retrieve and display a non-edit field from the selected data table record when the 'Edit' popup is opened , but now there is another issue.

Everything works fine for the data table record that is used to open the popup. However, when the popup's 'Next' and 'Prev' buttons are used, the non-edit field does not change (because its value is loaded only once when the popup opens). 

For each record displayed by the popup, I need to synchronize the loading of the non-edit field value with the loading of the editable field value(s).

Is there an event associated with the popup that is triggered when values from another data table record are loaded, including when the popup is opened or when the 'Next' and 'Prev' buttons are used? Please advise.

Understood. No problem.

Thanks for the suggestion regarding the .js file. If I have any questions, I'll let you know.