Tim Sutherland

I’ve noticed the following: If I remove &post_type=properties from the search string that the AJAX call creates the page will display correctly. Or if I change it to something else that isn’t properties.

i.e. the query string is ?layout=list&es=1&post_type=properties&location=Coffs+Harbour&page_num=1&paged-1=1

Change it to ?layout=list&es=1&location=Coffs+Harbour&page_num=1&paged-1=1

and the page appears correctly.

Any thoughts on why this would happen? The post type is properties and I’ve resaved permalinks in case there were any issues there but there’s no issues with any other part of the plugin, just appears to be this query that’s created when you filter a search.

Note if you just change the sort order of the results without any filtering (i.e. sort by lowest price) this is the query that’s created and it works fine with back to search results link working AOK

?layout=list&sort=lowest_price&is_address_search_enabled=0&is_collapsed_filter_enabled=0&sort-1=lowest_price&page_num=1&paged-1=1

It appears the issue is clearly the query string that gets created when you add filters to the search using the shortcode instructions?

I see this in the builder but it works AOK for visitors to the site so assumed it never worked. Be great if it also displayed in the builder.

I’m also seeing this issue. I hadn’t used the plugin before until 5.7 and didn’t even realise that there were category select boxes.

For those having the same issue and wondering how to rectify until plugin update follows, I used the below code and it worked in my instance (by simply setting the background of the pop-up to nothing).

#et-boc .area-outer-wrap[data-da-loader=yes] [data-da-area] {
    background: none !important;
}

Hi Phillip

Thanks for your advice.

I can confirm that the loader is not enabled (see screenshot). The CSS change will help but I can’t help but think that there’s something else at play there and you could be on the money with the use of custom post types as when it’s references on an ordinary wordpress page there’s no problems at all.

I use CPT UI for the custom post types as well as ACF for custom fields. If/when you had time it’d be good to see if the custom post types is what causes the problem.

https://www.localelearning.com.au/wp-content/uploads/2021/03/loader-off.png

I found the offending CSS whereby there are two references to background-image. Is it possible that there’s a duplicate and removing one may cause it solve the problem?

I’ll override with CSS for now too and keep an eye out for the next plugin update.

et-boc .area-outer-wrap[data-da-loader=yes] [data-da-area] {
    background-image: url(../images/spin.gif),-o-radial-gradient(center,circle,#fff 65%,hsla(0,0%,100%,0) 66%)!important;
    background-image: url(../images/spin.gif),radial-gradient(circle at center,#fff 65%,hsla(0,0%,100%,0) 66%)!important;
    background-size: 32px 32px,48px 48px;
    background-repeat: no-repeat;
    background-position: 50%;
}

Regards,

Tim

Note, I’ve also turned off ‘show loader’ in settings for the pop up and this didn’t make a difference.

Hi @strackerphil-1
Just sent what you requested finally. Sorry about the delay. Hope that helps in resolving the issue for others.

Regards,

Tim

Great thanks. ??

Cheers and thanks for the prompt response.

Is there an identifier that will allow me to search for all the post meta rows which are table press and/or the settings?

That way I can search all and check to ensure they’re all AOK.