WPSight

Hello Damian,

thanks for writing us.

But as already mentioned you’re using an outdated version of wpCasa which hasn’t much to do with the WPCasa plugin here. Please understand that we’re not able to offer support for that version you’re using since it is already outdated since more than 3 years.

You might want to consider to upgrade to the latest version (the plugin version offered here).

All the best

Hello,

thanks for your report. We’re already aware about the ongoing issues with the Display Widgets plugin. This only affects our premium themes and doesn’t have anything to do with WPCasa itself. However, our premium themes include a clean copy of that plugin which works without any issues. For support with our premium themes please open a ticket on http://wpcasa.com.

And thanks a lot for your suggestion. It might be really useful to those who are looking for a suiteable alternative.

All the best

• This reply was modified 8 years, 4 months ago by WPSight.

Hello,

it sounds like a CSS issue but can’t tell it for sure since we haven’t tested WPCasa with that theme. You might want to send over a link to your site so we can have a quick look by ourselves.

All the best

Hello,

sorry for the late reply.

This is actually not a bug but the actual behaviour. Removing the offer dropdown from the search form means that there is no control about what listings for what offer should get displayed.

To overcome this you’d need to consider customizing the search form properly.

All the best

Hello @eirikv,

It actually depends what you define as “easy”. Basically you can use the below code and it technically does what you need:

<?php

/**
 * Add custom text (from) before price
 */

add_filter( 'wpsight_get_listing_price_before', 'custom_get_listing_price_before' );

function custom_get_listing_price_before( $value ) {

	$custom = get_post_meta( get_the_ID(), '_my_custom_field_name', true );
  
  	if( $custom )
        $value .= '<small>' . $custom . '</small> ';
        
    return $value;
  
}

This code basically checks if there is a custom field with the name _my_custom_field_name and returns the value if available. You can use the default custom fields metabox in your listing editor to add this field/value manually. If you want to have a proper custom field in the listing price metabox you need to add it with some additional custom code.

Note: The code above hasn’t been tested, so please use at your own caution. Also: It is a very basic example, you might need to build on top of that.

All the best

Great, glad that this is solved now.

Hopefully you’ve adjusted the CSS from within your custom child theme and not directly in the CSS from the plugin? Otherwise it would get overwritten during the next update.

All the best

Hello,

this is most probably caused by some CSS from the theme you’re using. There isn’t much we can do on this part – especially if we do not have access to your website’s source code.

There is probably some CSS in your theme which styles buttons differently and which result in this misaligment. You might want to check there first.

All the best