Need to fully understand the function you have for the DATA option for a column. The sub option in DATA is POSSIBLE VALUES FOR COLUMN. Is this not a strict contraint because it says "possible"? I am under that impression because I thought it meant that I can list values there to limit the data so if someone tries to input a value not listed, it would halt.
For the infamous COUNTY field, we have that COUNTY table, but there is no FK in the database because we use the varchar for the COUNTY in the CLIENT table. I meant to use the COUNTY table we have to limit values from the front end. So the possible values function is not really a limiting function?
That option will only read the values for the filtering and editing and show the filters based on which option did you choose. This is usually for the selectboxes or checkboxes so the admin can "limit" the users for some of the filters or editing.
I apologize, but I did not get any more understanding from that explanation. Maybe a quick example if you have one.
Or if this helps, as mentioned, I have a field that has to be limited to 23 values that we store in MYSQL. Since I was having issues with using the option to use another WPDATA table and it's key to populate a drop down SELECT, I was hoping it would limit the values a user types in even if we changed from SELECT to TEXT BOX. Sounds like it does not.
I had to start moving away from the SELECT as it is risky with theme CSS's. Not to open that up again, but it works fine when editing the table in preview, yet has an additional issue when implementing the LIMIT EDIT option for a table. If you can understand our frustration. You do however do a better job at updates than the Form plugin folks, they do not allow any filtering on a SELECT nor do the allow any flexibility doing any picked number of fields to edit. It is all or nothing for them, you guys pick that ball up, we just have problems with your drop down SELECTs.
So we intend to try to use just the text and see if we can limit the editing on the MYSQL side. It is that or more JS, but we keep hearing and seeing that plugins and WP itself are supposed to limit or even some cases eliminate coding. Not sure of that yet.
It is not as important now, what I wanted to confirm was when we choose the DATA option when editing a column in the back end, among the 3 options is to use a Pre Defined List of values. I typed in say 21 values and saved, but I thought the table field would restrict the values to be input into the cell to those 21 values, it allows more than that so my question was what does that option actually do or am I assuming correctly that it does NOT restrict values.
When you define that 21 values , those 21 values will be shown in the filters( selectbox, checkbox) and in edit modal also ( if you have select box as an editor input type)
Define values list ( and your 21 entries there) will be the "only" values that will be shown in that selectbox or checkbox.
Later, if the user edits the table he can only choose that one ( if the select box is editor input type) from that 21 values, he can not add more values in that field.
Those 21 values will be loaded in the JSON, in the filters and in the editor input types.
This is implemented because some of our users have more than 100 different entries in one column, but they only need to display 10 or more in the filters.
Oh! Ok, sorry, I get it now of course, it is for limiting more so for volume not a strict limiting by values. I'd like to see it added if it is ok to add to wish list, but nothing huge. Thanks for hanging in to explain.
Need to fully understand the function you have for the DATA option for a column. The sub option in DATA is POSSIBLE VALUES FOR COLUMN. Is this not a strict contraint because it says "possible"? I am under that impression because I thought it meant that I can list values there to limit the data so if someone tries to input a value not listed, it would halt.
For the infamous COUNTY field, we have that COUNTY table, but there is no FK in the database because we use the varchar for the COUNTY in the CLIENT table. I meant to use the COUNTY table we have to limit values from the front end. So the possible values function is not really a limiting function?
Hi Alan,
Thank you for your purchase,
That option will only read the values for the filtering and editing and show the filters based on which option did you choose. This is usually for the selectboxes or checkboxes so the admin can "limit" the users for some of the filters or editing.
Best regards.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Hi Bogdan,
I apologize, but I did not get any more understanding from that explanation. Maybe a quick example if you have one.
Or if this helps, as mentioned, I have a field that has to be limited to 23 values that we store in MYSQL. Since I was having issues with using the option to use another WPDATA table and it's key to populate a drop down SELECT, I was hoping it would limit the values a user types in even if we changed from SELECT to TEXT BOX. Sounds like it does not.
I had to start moving away from the SELECT as it is risky with theme CSS's. Not to open that up again, but it works fine when editing the table in preview, yet has an additional issue when implementing the LIMIT EDIT option for a table. If you can understand our frustration. You do however do a better job at updates than the Form plugin folks, they do not allow any filtering on a SELECT nor do the allow any flexibility doing any picked number of fields to edit. It is all or nothing for them, you guys pick that ball up, we just have problems with your drop down SELECTs.
So we intend to try to use just the text and see if we can limit the editing on the MYSQL side. It is that or more JS, but we keep hearing and seeing that plugins and WP itself are supposed to limit or even some cases eliminate coding. Not sure of that yet.
Thanks!
HI Alan,
Sorry for misunderstanding but do you have any example of that table so I can take a look and understand better this.
Best regards.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
It is not as important now, what I wanted to confirm was when we choose the DATA option when editing a column in the back end, among the 3 options is to use a Pre Defined List of values. I typed in say 21 values and saved, but I thought the table field would restrict the values to be input into the cell to those 21 values, it allows more than that so my question was what does that option actually do or am I assuming correctly that it does NOT restrict values.
Hi Alan,
Ok let me try to explain you better this feature.
When you define that 21 values , those 21 values will be shown in the filters( selectbox, checkbox) and in edit modal also ( if you have select box as an editor input type)
Define values list ( and your 21 entries there) will be the "only" values that will be shown in that selectbox or checkbox.
Later, if the user edits the table he can only choose that one ( if the select box is editor input type) from that 21 values, he can not add more values in that field.
Those 21 values will be loaded in the JSON, in the filters and in the editor input types.
This is implemented because some of our users have more than 100 different entries in one column, but they only need to display 10 or more in the filters.
Hope this can help you out.
Best regards.
Kind Regards,
Miloš Jovanović
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
Oh! Ok, sorry, I get it now of course, it is for limiting more so for volume not a strict limiting by values. I'd like to see it added if it is ok to add to wish list, but nothing huge. Thanks for hanging in to explain.