‘Features’ issues and questions – not in documentation

Resolved torndownunits
(@torndownunits)

7 years, 6 months ago

The developer has said he won’t be active on these forums, I am hoping maybe a member will see this and reply RE the code question.

There is documentation here: http://codex.easypropertylistings.com.au/article/250-eplpropertyadditionalfeatureslist that covers adding additional features, but it’s not very clear. An example would be perfect to clarify it. I don’t know where exactly to add the features. EG how do I add “hardwood floors”?

To the Developer if he happens to see this:

Now here are the issues. Why are there ‘main’ features under “House Features”, and then “Additional Features” when they all show up in the same place in the listing anyway?

There should be an easier way to add features. I know they can be added as “features taxonomy’, but then they show up as hyperlinked tags which is confusing for the general viewer. They click on those thinking it’s details about the feature, then get taken to a page of listings with those features. Only someone who setup the site would know why they are there. It’s would be better to just be able to add to the preconfigured features easily, and be able to check them off so they display like the other features.

Why are their separate lists of features when they all show up in the same list anyway? Why not have those columns have titles and display like they do in the backend?

I looked into the premium listings templates available, and none of them seem to address these issues.

Viewing 2 replies - 1 through 2 (of 2 total)

(@justinfm101)

Hi,

I fought with this for a few hours and figured out what was going on, so I figured I’d share.

The filter that allows you to add additional features only takes checkboxes. Additionally, if you ‘replace the list,’ it doesn’t stop those from showing up in the back end.

Below, I’ve displayed the code to a functioning demonstration of adding a custom checkbox that’s then included in the features section.

function my_add_meta_box_epl_listings_advanced_callback($meta_fields) {
	$custom_field = array(
		'id'		=>	'epl_property_listing_custom_data_id',
		'label'		=>	__('Custom Details', 'epl'), // Box header
		'post_type'	=>	array('property', 'rural', 'rental', 'land', 'commercial', 'commercial_land', 'business'), // Which listing types these will be attached to
		'context'	=>	'normal',
		'priority'	=>	'default',
		'groups'	=>	array(
			array(
				'id'		=>	'property_custom_data_section_1',
				'columns'	=>	'2', // One or two columns
				'label'		=>	'custom property data 1',
				'fields'	=>	array(
					array(
						'name'		=>	'property_custom_data_checkbox_single',
						'label'		=>	__('Checkbox Single', 'epl'),
						'type'		=>	'checkbox_single',
						'opts'		=>	array(
							'yes'	=>	__('Yes', 'epl'),
						)
					)

				)
			)
			
		)
	);
	$meta_fields[] = $custom_field;
	return $meta_fields;
}
add_filter( 'epl_listing_meta_boxes' , 'my_add_meta_box_epl_listings_advanced_callback' );

function my_epl_property_additional_features_list( $array ) {
	$array[] = 'property_custom_data_checkbox_single'; //whatever your new field name is
	return $array;
}
add_filter( 'epl_property_additional_features_list' , 'my_epl_property_additional_features_list' );

I’ve also tried the filter for editing the features (http://codex.easypropertylistings.com.au/article/206-editing-meta-field-labels-and-attributes-on-new-edit-listing-page), but those only seem to effect the back end, and if you change the type of the field, it fails.

I’ve come to the conclusion that I’ll need to put all the features that aren’t ‘checkbox,’ including the ones already there like bedrooms, bathrooms etc, into my own custom box, and then display them in the theme myself.

Hopefully, that information helps you.

Thanks,

Justin

Thread Starter

torndownunits

(@torndownunits)

7 years, 5 months ago

Hey, thanks a ton I am going to take a look through this and try it out.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘‘Features’ issues and questions – not in documentation’ is closed to new replies.

Tags