You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WordPress options data can be stored in multiple ways; plain, serialized, serialized arrays.
When the data is stored as serialized or serialized arrays then the core admin logic simply shows 'serialized data'., Obviously you can't edit data like this.
There are many cases where data benefits from being stored in the wp_options table as serialized data. Often the data is almost self defining.
Each entry has a key and each field has a label and value. Given the label name and the context it should be possible to determine the field type and user friendly label for the field.
It should therefore be possible to provide admin pages which deal with serialized options data.
The oik base plugin, and quite a few of the plugins which are dependent upon it, uses serialized arrays for options data. Users would greatly benefit from a consistent admin UI managed by common code.
Therefore we propose to develop a new BW_Options_List_Table class that extends the BW_List_Table class to provide a admin UI for options fields.
The text was updated successfully, but these errors were encountered:
WordPress options data can be stored in multiple ways; plain, serialized, serialized arrays.
When the data is stored as serialized or serialized arrays then the core admin logic simply shows 'serialized data'., Obviously you can't edit data like this.
There are many cases where data benefits from being stored in the wp_options table as serialized data. Often the data is almost self defining.
Each entry has a key and each field has a label and value. Given the label name and the context it should be possible to determine the field type and user friendly label for the field.
It should therefore be possible to provide admin pages which deal with serialized options data.
The oik base plugin, and quite a few of the plugins which are dependent upon it, uses serialized arrays for options data. Users would greatly benefit from a consistent admin UI managed by common code.
Therefore we propose to develop a new
BW_Options_List_Table
class that extends theBW_List_Table
class to provide a admin UI for options fields.The text was updated successfully, but these errors were encountered: