beesmartdesign

I’m not certain a new WordPress version would have been the source of the issue – though it may be worth rolling back to an older version to test this, perhaps Vebra have changed something within their own system?

It may be that users with new API login details – like henryscat – are now unable to get authenticated, whereas as other users – such as myself – who have been running the plugin for a while are picking up the error but it’s still functioning with occasional drops in service.

Unfortunately it’s difficult for me to debug as the only valid API details I have are for a client website and I’m hesitant as they’re a live site and business. My PHP skills are pretty rudimentary so I’m afraid I can’t give any pertinent advice, but you can see where the conditional is occurring if you look at the file:

Line 31: vebra-properties/includes/vebra_feed.php

Henryscat, have you tried contacting Vebra support? (propertysoftwaregroup.com). They may be able to at least confirm the source of the problem is the plugin.

I’m now using a rather inelegant method for the time being, I’m unable to fix the issue at source but believe intercepting it in the template files should be enough as a temporary fix. Using the template files (moved into the theme folder), the two files: vb_list.php AND vb_detail.php

Find:
<div class="property_tagline">
<?php echo $property->web_status; ?>
</div>

Replace with:
<div class="property_tagline">
<?php $prop_type = $property->property_type;
$prop_postfix = $property->price_postfix;

if( ($prop_type == 'Commercial' || $prop_type == 'Office' || $prop_type == 'Retail') && strlen(trim($prop_postfix)) > 0){
echo "To Let";
} else {
echo $property->web_status;
}
?>
</div>

It relies on the ‘PA’ or ‘pcm’ price postfix field as rentals/lettings seem to use the postfix whereas For Sale properties don’t use them. It seems to work ok for me at the moment.