Skip to content

Secondary custom field ordering - wrong option value #115

Closed
@ernestmarcinko

Description

@ernestmarcinko

Describe the bug

The secondary custom field oldering uses the same option value as the primary, therefore it has no effect when used in combination with primary custom field oldering.

In backend/tabs/instance/general/ordering.php the lines:

        $o = new wpdreamsCustomSelect("orderby", __('Secondary ordering', 'ajax-search-pro'),
            array(
	            'selects' => array_merge($common_orders, array(
		            array('option' => __('Custom Field descending', 'ajax-search-pro'), 'value' => 'customfp DESC'),
		            array('option' => __('Custom Field  ascending', 'ajax-search-pro'), 'value' => 'customfp ASC')
	            )),
                'value' => $sd['orderby']
            ));

where the options should be:

    array('option' => __('Custom Field descending', 'ajax-search-pro'), 'value' => 'customfs DESC'),
    array('option' => __('Custom Field  ascending', 'ajax-search-pro'), 'value' => 'customfs ASC')

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions