Queries about DB table entries “geodir_custom_fields” changes after GD update v. 1.6.8
Hi GD support Team Developers,
after the update I realized some database entry changes and want to make sure that they are done in purpose. I am taking about the database table “geodir_custom_fields” and its settings.
I realized following within Database Table.
PLEASE CONFIRM AND/OR USE THOSE DETAILS AS BUG DESCRIPTION TO SOLVE THE ISSUE!
I. Two new columns are now new existing
“field_type_key” – I do not know for what this field is used?
and
“show_in” [detail],[listing],[moreinfo],[owntab],[mapbubble] used now to select on what position the fields are displayed.
II. Following columns are not supported any more for all field types
– clabel (no entries on new items)
– is_default (no entries now on new items – formerly used for show on sidebar)
– show_on_listing (no entries now on new items – formerly used on listings page)
– show_on_detail (no entries now on new items – formerly used in more info tab)
– show_as_tab (no entries now on new items – formerly use to create new tab on details page)
May caused about its depreciation (> https://wpgeodirectory.com/support/topic/where-does-the-data-comming-from-within-custom-field-db-table-show_in/)
I also found out that
III. Bug or on purpose ?
– On fieldtype “email”
the data type was formerly “VARCHAR” now “nothing” is in this field type.
– On Fieldtype “file”
the data type was fomerly “noting” in this field” now fieldtype is “TEXT” in this field type.
– On fieldtype “multiselect”
a. there is no option any more existing to choose the creation of Display types (Select, Checkbox and Radio).
b. the extra_field has no entries any more. Formerly there was on Select Display type the entry in field s:6:”select”;
– On Fieldtype “phone”
the data type was formerly “VARCHAR” now “nothing” is in this field type.
– On Fieldtype “url”
the data type was formerly “VARCHAR”, now it is “TEXT” as field type
Find here a screen shot as a short overview. Yellow marked items are changed > http://screencast.com/t/eO7pU1pq4
Looking forward to your reply.
Thanks, Alex