When I try to add a filter for Property Status, I only have “active” as an option. Is it possible to also show “Pending”?
]]>Has anybody encountered issues with duplicate entries or missing listings while using the plugin? If so how do you get this solved?
]]>I’ve noticed that with the latest version of the plugin, version 3.19.0, there is a warning in Firefox Console that says:
Google Maps JavaScript API has been loaded directly without a callback. This is not supported and can lead to race conditions and suboptimal performance. For supported loading patterns please see https://goo.gle/js-api-loading js:229:52The reference links to this page.
Race conditions and suboptimal performance are things I would like to avoid. This sounds like something that will have to be fixed by the developers in an update, correct?
]]>I want to know if I can import the listing from my Stellar MLS with this plugin
]]>In anticipation of MySQL, I have been testing my sites in Local. I received the following warning in Local running WP 6.2.2, PHP 8.0 & MySQL 8.0. However, I got no warning when running WP 6.2.2, PHP 8.0 & MySQL 5.7. Might this be an issue with MySQL 8.0? Or, might this be another matter entirely? Not sure what to make of this.
Warning: Attempt to read property “IsResultsPageModernView” on null in \wp-content\plugins\dsidxpress\globals.php on line 24
]]>Although the plugin still says it has only been tested up to WordPress version 6.0.3, I have been using it with WordPress 6.1.1 for several months without a problem. I know the plugin hasn’t been abandoned since you updated it a couple of months ago, but the WordPress compatibility hasn’t been updated.
Now WordPress 6.2 has been out for a while, and I’d like to upgrade the site. Is dsIDXpress compatible with WordPress 6.2?
]]>I received a notice from Google today saying:
We have detected a publicly accessible Google API key associated with the following Google Cloud Platform project…
It then listed my IDXPress site and the Google Maps API key it found.
When I checked the site, I found that the Google Maps API key was being appended as a query string variable to the following line:
<script src='//maps.googleapis.com/maps/api/js?key=<API Key was here>&libraries=drawing%2Cgeometry&ver=6.1.1' id='dsidxpress_google_maps_geocode_api-js'></script>So it does look like the IDXPress Plugin is including Google Maps API keys in the clear if you add your Google Maps API key in Admin > IDX > More Options > Google Maps API Key. Not good.
My workaround was to delete the Google Maps API key from IDX settings and clear my cache. It looks like Google Maps is still working without the API key.
I also regenerated the API key as Google recommends.
Hopefully, IDXPress can come up with a way to use the Google Maps API without publicly publishing the API key.
It does look like you can restrict a Google Maps API key to specific domain, which is better than nothing, but still not optimal.
]]>The last time we received support, we were told that new properties take a day or so for the images to sync and they’ll show, however it’s been a week and they aren’t showing.
They are showing for some locations but not others.
For example, if you use the menu at the top, go to Listings > Bel Air, those images show.
Going through the same process for the other locations:
Beverly Hills does not show.
Malibu Beach does not show.
Holmby Hills is generating an error (for another time). Right now the images not showing is an issue
]]>We are having some issue with the dsIDXpress plugin. We can see thumbprint photos of the listings but when we click on the listing, no photos are displayed, including the original thumbprint. The photos are supposed to populate from the dsIDXpress plugin. I see that you guys did an update/upgrade for this recently, and it potentially broke some sites such as ours. My questions is there an update or fix to this that you guys will be releasing soon, or what is the work around for the dsIDXpress problem?
Thank you
]]>I need to add a text overlay on the pending listings to show the status of the sale of the homes. As it is now, you can’t tell the difference between the listings. I’m getting the runaround from my rep but the client needs this done asap. Help is appreciated.
]]>I tried to test my new site with dsIDXpress but it disabled my main site’s activation key, and I can’t get it back to work on my main site. Please I need fixes on this ASAP
]]>There doesn’t seem to be a way to change the listings view from Classic to Modern when embedding listings with the shortcode, unless there is a shortcode property not included on this page: https://helpdeskds.wpengine.com/ds-idxpress/using-shortcodes-to-display-mls-content/
Anyone had any luck with this?
]]>It appears your plugin isn’t working very well. Got this…
%%ds_Results|{"SearchSetupID":"67","directive.ResultsPerPage":"3","directive.SortOrders[0].Column":"DateAdded","directive.SortOrders[0].Direction":"DESC"
There is more details, but it appears the message might contain details that should remain private. We might have to generate a new private key.
I googled the first part of that…
ds_Results|{"SearchSetupID" and came up with a large number of other sites that are down.
Not all pages are affected.
]]>Diverse team –
Do you have WP 5.8 compatibility in the works? On 5.8, the widgets do not appear (they output the debug string for an empty response body), and cURL fatal errors occur:
Fatal error: Uncaught Error: Object of class stdClass could not be converted to string in /home/xxxxxx/public_html/wp-includes/Requests/Transport/cURL.php:573 Stack trace: #0 /home/xxxxxx/public_html/wp-includes/Requests/Transport/cURL.php(332): Requests_Transport_cURL->get_expect_header(Object(stdClass)) #1 /home/xxxxxx/public_html/wp-includes/Requests/Transport/cURL.php(287): Requests_Transport_cURL->setup_handle('https://api-idx....', Array, Object(stdClass), Array) #2 /home/xxxxxx/public_html/wp-includes/Requests/Transport/cURL.php(209): Requests_Transport_cURL->get_subrequest_handle('https://api-idx....', Array, Object(stdClass), Array) #3 /home/xxxxxx/public_html/wp-includes/class-requests.php(482): Requests_Transport_cURL->request_multiple(Array, Array) #4 /home/xxxxxx/public_html/assets/plugins/dsidxpress/api-multirequest.php(41): Requests::request_multiple(Array, Array) #5 [internal function]: dsSearchAgent_ApiMultiRequest::GetBufferData('<!DOCTYPE html>...', 9) #6 /home/xxxxxx/public_html/wp-includes/functi in /home/xxxxxx/public_html/wp-includes/Requests/Transport/cURL.php on line 573
The fix seems to be very simple: on line 32 of api-multirequest.php, change json_decode($parameters) to json_decode($parameters, true), which will cause the data key to contain an associative array instead of an object. The updated cURL portion of the Requests library comprehends this just fine.
While you’re performing updates, please consider switching to accessing your API over HTTPS. The comment on line 24 of the above file reads “Since SSL certificate on ENV02 is not valid so curl will throw exception if we use https url so for initial testing we are using http url , it will be replaced later with proper url”. That obviously never happened, even though your SSL cert on api-idx.diversesolutions.com is now valid.
]]>jQuery v3 (added in WP 5.5) has different execution order of jQuery.ready vs DOMContentLoaded compared to jQuery v2 and v1 (used in WP < 5.5)
see https://jquery.com/upgrade-guide/3.0/#breaking-change-document-ready-handlers-are-now-asynchronous
Which breaks dsIDXpress plugin in WP < 5.5 as IDX page content (returned from API) has
window.addEventListener('DOMContentLoaded', function () {
dsidx.activate('details');
// etc
});while using jQuery(function(){...}) in https://api-idx.diversesolutions.com/combo-js?config=dsidxpress-pro&ver=3.14.0 which makes all those dsidx.activate(..) run after the ready function in combo-js, resulting in empty activated modules and broken all IDX pages/search etc.
If we upgrade our WP core past 5.4, while running the RealesWP theme, our content box that contains the list on the right is reduced to 100px tall, and the map is set to 0px tall.
Not sure if an overwrite can be done in the plugin code but I am also reaching out to the theme developer. I was hoping updates might fix this issue, but recent updates both from dsIDXexpress and RealesWP have not fixed the issue. Manually attempting to override with CSS has been unsuccessful.
]]>First time using this plugin in a while. How do I add a title to the IDX pages? I can see in the plugin code where the custom post type only supports ‘editor’. Why is this? Every IDX page I create is titled ‘Auto Draft’.
]]>Hello!
Can you direct me to the documentation for adding a SOLD listings page using your WordPress plugin?
Thanks!
]]>Hi
I can′t activate the plugin after update it to the last version.
It keep saying:
Parse error: syntax error, unexpected ‘}’ in /home/h2wzis5an28z/public_html/wp-content/plugins/dsidxpress/widget-idx-quick-search.php on line 199
]]>Uncaught ReferenceError: dsidx is not defined
** Included page reference.
Is anyone supporting this?
]]>The footer.php in the root directory has a script tag in it. That script tag makes a common issue. They use $ to represent jquery. This is not acceptable (as is) in wordpress, as wordpress doesn’t define this by default. The $ has to change to a ‘jquery’ or you need to pass it as a param in a function.
<script type='text/javascript'>
jquery.ajax({
url: dsidxAjaxHandler.ajaxurl,
type: 'post',
data: {
'action':'dsidx_client_assist',
'dsidx_action': 'LoadDisclaimerAsync',
'params': '{$paramsToJS}'
},
success: function(response){
jquery('#{$disclaimerPlaceholderID}').replaceWith(response);
},
error: function(response){
jquery('#{$disclaimerPlaceholderID}').replaceWith(response);
}
});
</script> I had a client site I wanted to upgrade to WP 5.6, but the plugin documentation still shows it’s only tested to 5.5.3.
I contacted Diverse Solutions Tech Support and spoke to Jordan, who told me they haven’t heard of any issues with WP 5.6, and that it is compatible.
I upgraded, and haven’t had any issues, PHP, or javascript errors.
]]>I think the API server is very slow to respond and it throws lots of loading data errors any chance that you can increase the capacity of your server?
Love the plugin, but it depends on your server and if the server is low in resources and gets back with errors and a very slow respond it becomes useless seo-wise
If you can post any updates here on the forum will be well appreciated by the plugin fans
Well, got a new client. The site started becoming very slow. After cleaning the Database we found it fast. But over time, the database started growing again.
Turns out, this plugin creates tens of thousands of transient records in the options table. Since they load all options on every visit, this causes a performance issue, and makes the site VERY slow. Clearing the transients gets it back, until it fills up again.
Not sure but there appears to be a nulling of the transient, but not a deletion. If it deleted it instead, it would probably avoid these issues.
]]>Hello,
Where can I buy the access to MLS? Then I use the API key from there to activate the plugin, correct?
Anything else I need to know?
Thanks!
Marcus
]]>I spoke to Mason at Diverse Solutions, and he was kind enough to test the plugin with WP 5.5. He had no issues, so I upgraded my site.
I’m using a default theme with WP Super Cache, Autoptimize, and Delete Expired Transients with the IDX Listings and IDX Guided Search widgets. WP 5.5 is working fine with no issues and nothing in the error logs so far.
The new core XML sitemap picks up a link to /idx/listings/for-sale (all properties for sale) out-of-the-box.
So far, so good.
]]>i want to change layout of idx page listing and add extra features in search form shortcode
]]>Hi i am getting the error on every page where the listing is calling
Notice: Undefined offset: 0 in `/home/username/public_html/dev.miamiluxuryresidences.com/wp-content/plugins/dsidxpress/idx-listings-pages.php on line 153
Notice: Trying to get property ‘post_content’ of non-object in /home/username/public_html/dev.miamiluxuryresidences.com/wp-content/plugins/dsidxpress/idx-listings-pages.php on line 153`
I am using the developer key to activate the IDXlisting until we are going to live.
]]>I noticed the following PHP warnings (PHP 7.3) each time I visited the Widgets Page in Admin, even though I’m not using the List Areas Widget:
Use of undefined constant city - assumed 'city' (this will throw an Error in a future version of PHP) in /home/username/public_html/wp-content/plugins/dsidxpress/widget-list-areas.php on line 106
Use of undefined constant community - assumed 'community' (this will throw an Error in a future version of PHP) in /home/username/public_html/wp-content/plugins/dsidxpress/widget-list-areas.php on line 107
Use of undefined constant tract - assumed 'tract' (this will throw an Error in a future version of PHP) in /home/username/public_html/wp-content/plugins/dsidxpress/widget-list-areas.php on line 108
Use of undefined constant zip - assumed 'zip' (this will throw an Error in a future version of PHP) in /home/username/public_html/wp-content/plugins/dsidxpress/widget-list-areas.php on line 109
On lines 106-109, it appears the developers left out the quotes for city, community, tract, and zip that are going to be required in future versions of PHP and trigger the warnings:
<option value="city" {$selectedAreaType[city]}>Cities</option>
<option value="community" {$selectedAreaType[community]}>Communities</option>
<option value="tract" {$selectedAreaType[tract]}>Tracts</option>
<option value="zip" {$selectedAreaType[zip]}>Zip Codes</option>
So to prevent the warning piling up in your error logs, you can just add the quotes:
<option value="city" {$selectedAreaType['city']}>Cities</option>
<option value="community" {$selectedAreaType['community']}>Communities</option>
<option value="tract" {$selectedAreaType['tract']}>Tracts</option>
<option value="zip" {$selectedAreaType['zip']}>Zip Codes</option>
A similar PHP warning occurs in the file locations.php, where searchSetupID and type, the indices for two of the array elements aren’t quoted:
searchSetupID => $options["SearchSetupID"],
type => $_REQUEST["type"]
That PHP warning isn’t triggered unless you use the zip codes option in the List Areas Widget. You can prevent the warning by quoting the indices:
"searchSetupID" => $options["SearchSetupID"],
"type" => $_REQUEST["type"]
I know these won’t interfere with the operation of the plugin, but who wants a bunch of PHP warnings in their error logs?
]]>We noticed that the IDX plugin was breaking our client’s grid view of the media gallery and the dynamic loading of thumbnails spun indefinitely with no thumbs loaded (list view worked). Unfortunately, one of the other required plugins uses only the media gallery grid view in its interface and the list view is not an option.
We verified the grid view remained broken with the latest WordPress core, latest IDX plugin installed, an unaltered base theme, and no other plugins enabled. The only somewhat unique factor is that our media gallery has roughly 2,000 images. As soon as the IDX plugins were disabled on their respective sites, the problem disappeared on both the production site and empty install.
]]>